Hostinger has cut server response times by up to 35 percent after reworking its in-house content delivery network. The CDN now needs far less computing power, so the company has switched it on across all web hosting plans, including Premium and Single, at no extra charge. Saulius Lazaravičius, the company’s chief product officer, said a more efficient CDN lets every customer get a faster, more resilient site without paying for extra infrastructure.
Existing customers moved over automatically if they met three conditions: they used Hostinger DNS, ran no other CDN and had not opted out. New customers get the CDN enabled by default. Early infrastructure-wide data shows average response times falling 26 percent, from 965 ms to 714 ms. SSD-based servers improved the most, by 35 percent. Those machines had less headroom than newer NVMe hardware, so lowering the backend load made a bigger difference, even though SSD servers now form a minority of the fleet.
Load balancing shifted too. Lower-tier servers once ran 20 to 30 percent above the average load of the Business and Cloud infrastructure. Afterward, Premium and Single servers sat 15 to 20 percent below that average. Even sites without the CDN enabled responded faster, since overall server pressure dropped.
Instead of buying new hardware, Hostinger reduced the computing resources its CDN needs by 45 to 50 percent. Encryption played a big part. The company moved SSL certificates from RSA to ECDSA, which cut CPU use for SSL operations to roughly a third of the old level. It also adopted kernel TLS and improved session resumption, so returning visitors cost less to serve.
The in-house traffic engine added further gains. Previously, several regions fetched and processed the same content independently. Now, requests travel through the edge closest to the website’s origin over warm, pooled connections. Connection setup fell from tens of milliseconds to about 3 ms, and global CPU use dropped around 20 percent. Tasks such as image optimization can also be reused across the network instead of repeated.
Smaller fixes covered the remainder, including removing internal lock contention, moving bot fingerprinting into native code, and streamlining storage, logging, request handling and edge process recovery.

