CDNs explained: do you actually need one?
A CDN can be the single biggest performance win for a global site — or pure complexity overhead for a local one. Here's how to tell which side you're on.
What a CDN does
A content delivery network caches copies of your static assets — images, CSS, JS — across hundreds of locations worldwide. When a visitor loads your site, those assets come from the nearest edge instead of your origin server.
For global sites this can cut total page-load time by half. For an audience that's geographically close to your server already, the win is much smaller.
When you definitely need one
International audience, image-heavy site, or any site that's seen a viral traffic spike. CDNs absorb traffic the origin can't.
Ecommerce — even small. A CDN smooths checkout performance and protects against bot traffic and DDoS, both of which can take your store offline at the worst moment.
When you can skip it
Local-only business sites with low traffic and a host in the same region. Adding a CDN here is more complexity than it's worth — though Cloudflare's free tier is so cheap and easy that it's still hard to argue against.
Truly internal apps where every user is on the same network as the server.
Questions readers ask about this topic
Is Cloudflare's free plan really free?
Does a CDN replace my host?
Will a CDN break my site?
Where to go next on Hostilo
One email a month. Hosting deals, new reviews, no fluff.
What uptime numbers really mean
99.9% sounds reassuring. Here's what it translates to in downtime per year, and which providers consistently exceed it.
TTFB: what time-to-first-byte tells you about your host
TTFB is the cleanest single metric for comparing hosts. Here's what it measures, what's good, and what to do when yours is bad.