CDN stands for content delivery network — a globally distributed system of edge servers that cache and deliver web content from the geographic location closest to the requesting user. CDNs reduce latency, absorb traffic spikes, and improve Core Web Vitals. Every large-scale site (Amazon, Netflix, Meta) runs behind one.
The acronym trips people up more than the concept. CDN = content delivery network = a fleet of servers around the world holding cached copies of your site, so users get bytes from a nearby data center instead of your origin.
What is a CDN?
A CDN (content delivery network) is a network of edge servers positioned in data centers across geographic regions. Each edge caches a copy of your site's static assets — images, CSS, JavaScript, fonts, and increasingly HTML. When a user requests your site, DNS routes the request to the nearest edge; that edge returns the cached response in milliseconds.
Without a CDN, every request travels from user to origin server — sometimes thousands of miles, adding hundreds of milliseconds. With a CDN, most requests are served from an edge within a few hundred miles.
"CDN" is used far more often than the full "content delivery network" — in engineering docs, RFC standards, and every performance dashboard. This page exists both spelled-out and acronym-first because that's how people search.
Why CDNs matter for SEO and revenue
Speed is a ranking signal. It's also a revenue signal. Five reasons CDNs sit near the top of the technical-SEO stack:
- Core Web Vitals compliance. Google uses LCP, INP, and CLS as ranking signals. CDNs improve LCP dramatically — often the difference between "poor" and "good" scores.
- TTFB reduction. Time to First Byte drops 30-70% with a well-configured CDN — a metric Google explicitly tracks.
- Compounding conversion lift. Portent research shows conversion rates drop by 4.42% for every second of load-time delay in the first 5 seconds.
- DDoS + WAF protection. CDNs absorb attack traffic before it reaches origin — most bundle a Web Application Firewall.
- Cost efficiency. Edge-cached bandwidth is often cheaper than origin bandwidth. Traffic spikes hit CDN, not your hosting bill.
How a CDN works — the request flow
Every request follows the same four steps.
GET /hero.webp
# 2. DNS routes to nearest edge (Mumbai PoP)
Anycast: mumbai-edge-04
# 3. Edge checks cache
X-Cache: HIT → return 200 in ~30ms
X-Cache: MISS → fetch origin → store → return
# 4. Every subsequent Mumbai user hits the cache
Anycast routing
Modern CDNs use Anycast — the same IP address is announced from every edge location. Networks automatically send traffic to the nearest edge.
Cache TTL
Each cached asset has a time-to-live: how long the edge keeps it before checking origin for updates. Long TTLs on versioned assets (hashed filenames) can be a year; short TTLs on HTML might be minutes.
Purge and revalidation
When origin changes, you either purge specific URLs (recommended) or wait for TTL to expire (safer at scale).
Major CDN providers compared
| Provider | Free tier | Strengths | Best for |
|---|---|---|---|
| Cloudflare | Yes (unlimited bandwidth) | Full-stack: CDN + DNS + WAF + Workers | Most sites, small to enterprise |
| Amazon CloudFront | 1TB/mo, 12 months | AWS integration, deep customization | AWS-hosted apps |
| Fastly | $50 credit | Instant purge, real-time logs, VCL | Publishers, high-frequency deploys |
| Akamai | No | Largest global network, enterprise features | Fortune 500 workloads |
| Bunny.net | Pay-as-you-go, low cost | Predictable pricing, image optimizer | Media-heavy sites on a budget |
| Google Cloud CDN | Depends on GCP tier | GCP integration, load-balancer-native | GCP-hosted apps |
Real CDN implementation examples
1. Dental practice — one 30-minute change
A dental clinic added Cloudflare to their WordPress site (DNS repoint + auto-caching). Mobile LCP fell from 4.1s to 1.9s in one week. Rankings for "dentist near me" queries climbed from page 3 to the top 5 within 8 weeks — no content changes, no link-building.
2. E-commerce store — crawl budget recovery
An online store had 10,000 product pages and Googlebot was crawling 200/day. After moving static assets to CloudFront + configuring proper Cache-Control on HTML, crawl rate jumped to 2,400/day. New products indexed within hours instead of weeks.
3. Content publisher — competitor gap closed
Two content sites competing for the same keywords. One added Fastly + HTTP/3 + Brotli compression; the other did not. Six months later the CDN-optimised site had accumulated a 2.1x organic traffic lead — small technical differences compounded page-by-page over 6 months.
CDN vs. traditional web hosting — different jobs
Web hosting
- Stores original site files + database
- One physical location (or a few)
- Runs application logic
- Handles authenticated / dynamic requests
- The origin CDN pulls from
CDN
- Caches copies globally
- 200+ edge locations worldwide
- Serves static assets fast
- Optionally caches HTML and API responses
- Sits in front of hosting
Best practice: fast origin hosting + a CDN in front. Neither replaces the other.
6 CDN best practices
- Use hash-versioned filenames for assets.
bundle.a3f92c.jscan cache for a year — hash changes when content changes. - Set Cache-Control headers explicitly. Do not rely on CDN defaults.
public, max-age=31536000, immutablefor versioned files. - Enable Brotli + HTTP/3. Most CDNs support both; enabling shaves 10-20% off transfer bytes and 20-40% off handshake latency.
- Turn on image optimization. Cloudflare Polish, CloudFront + Lambda@Edge, Fastly Image Optimizer — automatic WebP + resizing at the edge.
- Purge surgically on deploy. Only invalidate URLs that changed. Global purges reset cache for every region.
- Monitor cache hit ratio. Target 90%+ on static content. Under 70% signals a misconfiguration draining performance.
Turning on Cloudflare's free tier without setting Cache-Control headers or purge rules can hurt performance — you get cached versions of authenticated content served across users. Read the setup guide before flipping it on for a production site.
Common CDN mistakes to avoid
- Caching cookies or logged-in state. User A ends up seeing user B's dashboard.
- No deploy invalidation strategy. Users see broken JS/CSS combinations for hours after ship.
- Skipping origin-shield configuration. Cache misses stampede origin during traffic peaks.
- Not testing from real geographies. WebPageTest and Chrome DevTools throttling from your city hides the CDN's actual value.
- Assuming the CDN is a security cure. WAF rules still need tuning — defaults let a lot through.
Frequently asked questions
CDN stands for content delivery network — a globally distributed system of edge servers that cache and deliver web content from the location closest to each user.
Cloudflare, Amazon CloudFront, Fastly, Akamai, Bunny.net, and Google Cloud CDN. Cloudflare and Bunny offer generous free / low-cost tiers; Akamai and Fastly serve most Fortune 500 traffic.
Web hosting stores original files and databases on one origin server. A CDN sits in front and distributes cached copies globally. Hosting is where the site lives; CDN is how it reaches users fast.
Cloudflare basic setup — pointing DNS at Cloudflare — takes 15-30 minutes. Advanced configuration (cache rules, page rules, image optimization) usually takes 2-4 hours to tune well.
Yes, often more than desktop. Mobile networks have higher latency, so proximity gains amplify. Mobile TTFB improvements of 40-60% are common.
How theStacc validates your CDN configuration
Our SEO audit runs edge tests from 6 continents, checks cache hit ratios, and verifies your Cache-Control headers against Google's page-experience thresholds. When misconfigurations surface, we send back the exact settings to change — with expected LCP delta so you can prioritise engineering time.