What Is a CDN? Why Websites Load Fast Everywhere

Short answer

A CDN (Content Delivery Network) is a worldwide network of servers that caches copies of your website close to users. Instead of every visitor connecting to your origin server (wherever that is), they download assets from the nearest CDN edge — often a few milliseconds away. Result: dramatically faster page loads, lower bandwidth bills, and resilience against traffic spikes.

What the CDN actually caches

• Static assets — JS, CSS, images, fonts, videos. These never change per user, so they cache perfectly.
• HTML (optionally) — fully-static sites (like Utilko) cache entire HTML pages. Dynamic sites cache short-TTL responses.
• API responses (optionally) — GET responses with correct Cache-Control headers can cache at the edge.

How edge caching works — the life of a request

1. User in Tokyo requests yoursite.com/app.js.
2. DNS sends them to the nearest CDN pop (e.g., Tokyo).
3. Tokyo edge has a cached copy → returns in ~5 ms.
4. Different user in São Paulo requests the same file → São Paulo edge has no copy yet → fetches from origin → caches locally → serves.
5. Next São Paulo user gets it from the São Paulo edge directly.

Why it's faster

A typical trans-Pacific round trip is 150+ ms. A trans-Atlantic one is ~80 ms. If every image/CSS/JS on your page has to make that round trip, you're looking at multiple seconds of page load. A CDN reduces the round trip to single-digit ms for cacheable content. For a typical page with 30 assets, that's the difference between "loads instantly" and "visibly slow."

Other CDN benefits beyond speed

• DDoS protection — CDNs absorb attack traffic across their global edge, preventing it from ever reaching your origin.
• TLS termination — edge handles HTTPS handshake; your origin doesn't even need TLS.
• Compression & image optimization — most CDNs auto-compress (gzip/brotli) and optionally convert images on the fly.
• Geographic routing — route users to the closest origin server if you have multiple regions.
• Bandwidth savings — each asset is fetched from your origin ~1 time per pop instead of once per user.

Major CDN providers (2026)

CDN	Pop count	Best for
Cloudflare	330+	Generalist; free tier is extremely capable
AWS CloudFront	600+	AWS integration, huge global coverage
Fastly	100+	High-performance, edge compute via VCL
Akamai	4000+	Enterprise, massive scale
Google Cloud CDN	200+	GCP integration
Bunny.net	100+	Low-cost, simple

Cache headers that control CDN behavior

• Cache-Control: public, max-age=31536000, immutable — cache for a year, never revalidate (perfect for fingerprinted assets)
• Cache-Control: public, max-age=300, s-maxage=3600 — browser caches 5 min, CDN caches 1 hr
• Cache-Control: no-store — don't cache anywhere (for sensitive/user-specific content)
• Vary: Accept-Encoding — separate cache per encoding (gzip vs brotli vs none)

Related tools

To see which CDN serves a given URL, look up its IP with IP address lookup — the AS name usually reveals the CDN provider. Response codes like 304 Not Modified or 200 (from service worker) come from cache layers; look them up with HTTP status codes.