The short version
What is a CDN? A content delivery network is a network of servers spread across the world that keeps copies of your website’s static files, images, stylesheets, scripts, and sometimes full pages, and hands them to each visitor from whichever server is geographically closest. Without a CDN, a visitor in Sydney loads every file from your single server wherever it sits, maybe in Germany, and every kilometre adds latency. With a CDN, that visitor gets the files from a server in Sydney instead. The result is faster page loads for distant visitors, less strain on your origin server during traffic spikes, and better resilience if one location has problems. CDNs power a huge share of the modern web, from social networks to streaming services, and the same technology is now bundled with many hosting plans. The concept is simple; the details below explain what actually happens and what a CDN cannot do (checked 14 Oct 2026).
How a CDN works, step by step
When you enable a CDN, your domain’s DNS points visitors to the CDN’s edge network instead of directly to your hosting server. A visitor requests your homepage; the CDN routes that request to the nearest point of presence, a PoP. If the PoP already has a cached copy of the needed files, a cache hit, it serves them immediately without ever contacting your server. If not, a cache miss, it fetches the files from your origin server once, serves them to the visitor, and stores a copy for the next person. Static assets like images, CSS, and JavaScript cache beautifully because they rarely change. Dynamic, personalised content like a logged-in dashboard or a cart is trickier; modern CDNs can accelerate it with smart routing but must never cache one user’s private data for another. Cache lifetimes are controlled by headers and CDN rules: set them too long and visitors see stale content, too short and you lose the benefit. Good CDN setups also handle TLS at the edge and can absorb distributed denial-of-service floods before they reach your server.
What a CDN does for your site
The headline benefit is speed for distant visitors: cutting the physical distance files travel is the single biggest latency win available, often shaving a second or more off load times for international audiences. That speed translates into better user experience, lower bounce rates, and a modest SEO benefit, since page speed is a ranking factor. The second benefit is origin offload: during a traffic spike, the CDN serves most requests from cache, so your hosting plan’s CPU and bandwidth limits stretch much further. The third is reliability: with content replicated across many PoPs, a single server or network failure does not take your site down everywhere. The fourth is security: most CDNs include DDoS mitigation and a web application firewall layer, filtering junk traffic before it touches your server. For image-heavy sites, blogs with global readers, and stores selling internationally, a CDN is one of the highest-value upgrades you can make. Our Hostinger web hosting overview notes which plans bundle one.
What is a CDN unable to fix?
A CDN is not magic, and sellers oversell it. It does almost nothing for visitors already near your origin server; if your audience and your server are in the same city, the gains are small. It cannot fix a slow origin: if your server takes three seconds to generate a page, the CDN still waits those three seconds on a cache miss. Misconfigured caching causes real pain, stale prices in a store, or logged-in users seeing each other’s content, which is why dynamic sites need careful cache rules. A CDN adds a third-party dependency: if the CDN has an outage or is blocked in some region, your site feels it. And the free or bundled CDN tiers have limits on bandwidth, features, and support compared with paid plans from specialists like Cloudflare or Bunny. Think of a CDN as a multiplier on a decent setup, not a rescue for a bad one. Fix hosting and page weight first, then add the CDN. For speed-focused hosting comparisons, see best low latency hosting.
What a CDN does not do for Hostinger users
Here is an honest framing of what is a cdn in the context of Hostinger specifically. Hostinger bundles a CDN with its Unlimited and Cloud plans, which is genuinely useful and saves you configuring a third party. But the cheapest Premium plan does not include it, so budget-plan buyers either go without or set up Cloudflare's free tier themselves, which is a fine option. The bundled CDN will not rescue an overloaded shared account: if your plan's CPU limits are the bottleneck, cached assets help but dynamic pages still crawl. It also does not replace backups, security hardening, or image optimisation; a CDN delivers your bloated 5 MB hero image faster, but compressing it to 200 KB helps more. Use the bundled CDN as one layer among several: decent hosting, cached pages, optimised images, then the CDN on top. That stack beats any single trick. For plan details, compare Hostinger cloud hosting against the shared tiers.
When a specialist CDN beats the bundled one
Hostinger's bundled CDN is convenient, but it is not the last word. If you run a high-traffic store, a media-heavy site, or anything where seconds of latency cost money, a dedicated CDN like Cloudflare or Bunny gives you finer cache control, better analytics, stronger DDoS protection, and more points of presence. Developers who need edge functions, advanced page rules, or detailed cache purging will outgrow a bundled toggle quickly. And if you ever leave Hostinger, a third-party CDN moves with you, while the bundled one does not. The practical advice: start with the bundled CDN, since it is free with your plan and takes minutes to enable, and graduate to a specialist when your traffic or your needs justify it. Either way, measure before and after with a speed test; a CDN should show clear gains for distant visitors, and if it does not, something else is the bottleneck (checked 14 Oct 2026).
| Situation | CDN helps a lot | CDN helps little |
|---|---|---|
| Global audience, one origin server | Yes, big latency win | - |
| Local audience near your server | - | Yes, distance is already short |
| Traffic spikes | Yes, absorbs the surge | - |
| Image-heavy pages | Yes, static assets cache well | - |
| Logged-in dashboards | - | Yes, personal data cannot cache |
| Slow origin server | - | Yes, fix the server first |
Cloud Startup
48-month plan, paid upfront
Renews at $25.99/mo
- Unlimited websites
- 100 GB NVMe storage
- 4 CPU cores + 4 GB RAM
- Daily and on-demand backups
- Free domain for 1 year
FAQ
A CDN is a network of servers around the world that stores copies of your website's files and serves them from the location nearest each visitor. This cuts loading time for distant visitors, reduces strain on your hosting server, and adds resilience against traffic spikes and outages.
When a visitor requests your site, the CDN routes them to the closest edge server. If that server has a cached copy, it serves it instantly; if not, it fetches the file from your origin server once and caches it for the next visitor. Static files like images and scripts cache best.
Yes, for most sites with any international audience. The speed gain for distant visitors is significant, and the protection against traffic spikes alone is worth it. If your audience is entirely local to your server, the benefit is smaller but the security and reliability gains still apply.
Hostinger includes CDN on its Unlimited and Cloud hosting plans, which covers most growing sites. The cheapest Premium plan does not include it. If you are on Premium and need a CDN, a free Cloudflare plan in front of your site is a legitimate alternative.
A CDN cannot fix a slow origin server, since it still waits for the server on a cache miss. It does little for visitors already near your server, and misconfigured caching can serve stale content or leak personalised data. It is a multiplier on a good setup, not a rescue.
A CDN speeds up delivery of your content from distributed edge servers. Web hosting is the origin server where your site actually lives. You need hosting first; a CDN is an optional layer on top that makes the hosted site faster and more resilient.