A CDN (content delivery network) is a globally distributed network of servers that delivers static and dynamic web content such as images, JavaScript, stylesheets, videos, fonts and entire HTML pages – as close to the end user as possible. Instead of passing every request through to the central origin server, the CDN node (“edge server”) that is geographically and network-wise closest to the visitor answers. That lowers load times, relieves your own infrastructure and makes a website more robust against load spikes and DDoS attacks.
How does a content delivery network work?
A CDN consists of a global federation of so-called points of presence (PoPs), data centres housing edge servers. Each PoP holds a cached copy of the selected content. If someone in Stuttgart opens a website whose origin server sits in Frankfurt, it’s not the origin itself but the nearest edge node (e.g. the Frankfurt PoP) that delivers. A visitor in Tokyo gets the same files from the Tokyo PoP. The intelligent routing is handled by the CDN via anycast routing or DNS-based geo-routing.
Caching and cache invalidation
Edge servers only query the origin when the requested resource is either not yet cached or has expired. Cache headers (Cache-Control, ETag, Expires) control, per file, how long a piece of content stays cached. If a file changes early, the cache can be emptied in a targeted way via a “purge”.
Origin shield and multi-tier caching
Larger CDN providers place an additional caching layer (“origin shield”) between edge nodes and origin. That reduces the number of requests actually arriving at the origin server yet again – important during viral traffic spikes.
Benefits of a CDN at a glance
Faster load times
The physical proximity between server and device shortens latency. For images, fonts and libraries from the cache, the answer often arrives in under 50 ms. Faster pages directly improve the Core Web Vitals (LCP, FCP) and thus the Google ranking.
Higher scalability
Sudden traffic from a campaign, a newsletter blast or a PR event pushes many web servers to their limits without a CDN. With distributed caching, the load spreads across hundreds of PoPs instead of overloading a single server.
Better availability
If an edge node fails, the next best takes over automatically. Even a complete origin server outage can be bridged, since delivered cache remains reachable until the backend responds again.
Protection against DDoS and bots
Modern CDN providers block volumetric DDoS attacks right at the edge, long before they reach the origin server. Web application firewalls (WAF), rate limiting and bot management are standard with most providers.
Reduced bandwidth costs
Instead of answering every request from your own server, the CDN handles delivery. That saves traffic volume with the hosting provider, a tangible cost factor especially for media-heavy sites.
SEO benefits
Since Google uses the Core Web Vitals as a ranking signal, load times are a direct SEO factor. A well-configured CDN pushes LCP, FCP and TTFB into the green zone, supporting not only the user experience but also findability via search engines.
Which content benefits the most?
Classically, static assets are offloaded: images, CSS, JavaScript, fonts. These files rarely change and are perfect for aggressive caching. Beyond that, many CDNs today also handle:
- Streaming content (video and audio on demand, live streams)
- Software downloads and installation files
- API responses via edge computing functions (Cloudflare Workers, Lambda@Edge, Fastly Compute)
- Dynamic HTML for websites whose content rarely changes
- WebSocket connections and real-time data with special caching strategies
When is a CDN worth it?
- The website addresses an international audience, or at least has visitors outside its own region.
- Many or large media files are delivered (online shops with high-resolution product photos, video platforms, magazines).
- The web shop or platform must withstand load spikes: sales, launches, seasonal campaigns.
- The site is conversion- or SEO-critical and every extra hundredth of a second of load time counts.
- There is an elevated security risk (politically exposed sites, big brands, login areas).
For a purely locally accessed brochure website with little traffic, on the other hand, a CDN is usually not strictly necessary, though many providers now have entry tiers so cheap that the effort can pay off there too.
Well-known CDN providers
| Provider | Strengths |
|---|---|
| Cloudflare | Large free tier, integrated DDoS protection, Workers (edge computing) |
| Akamai | Enterprise standard, very large global network |
| Amazon CloudFront | Tight integration with AWS, Lambda@Edge |
| Fastly | Fast cache purges, strong API control |
| Google Cloud CDN | Integrated into GCP, good synergies with GKE & Cloud Run |
| Bunny.net | Inexpensive entry, simple operation |
| KeyCDN | Pay as you go, good value for money |
CDN integration in CMS and frameworks
In WordPress, a CDN can be connected via plugins such as W3 Total Cache, WP Rocket or the official Cloudflare integration. TYPO3 offers extensions that automatically route asset handling through a CDN. With headless setups or static site generators (Hugo, Next.js, Astro), delivery via a CDN is the default anyway – the build artefact lands directly on a globally distributed storage bucket.
If you take your website’s performance seriously, you typically combine a CDN with:
- HTTP/3 and TLS 1.3 for lower connection latency
- Brotli or gzip compression at the edge
- Image optimisation (WebP/AVIF, automatic resizing) directly in the CDN
- HTTP/2 server push or early hints for critical resources
Frequently asked questions about content delivery networks
What does a CDN cost? Cloudflare and Bunny.net offer free or very cheap entry tiers for small sites. For large enterprise setups with Akamai or Fastly, on the other hand, costs scale with the traffic delivered and can be correspondingly higher at very large volumes.
Does a CDN replace web hosting? No. A CDN delivers a cached copy; the actual content is still generated by the origin server. Without working hosting in the background, there’s nothing to cache.
Does a CDN hurt SEO? Quite the opposite: faster delivery improves the Core Web Vitals, which have fed into the Google ranking since 2021. What matters is only that the cache headers are set correctly and the CDN provider allows crawlers like Googlebot unhindered access.
What’s the difference between a CDN and cloud hosting? Cloud hosting (AWS, Azure, GCP) provides server resources on which applications run. A CDN only distributes the result of these applications closer to the user. Many setups combine both: cloud hosting in the backend, CDN as the global delivery layer in front.
Conclusion
A well-configured content delivery network is today practically mandatory equipment for any website with supra-regional ambitions, whether for performance, security or SEO reasons. Which provider fits best depends on traffic volume, the geo-distribution of the audience and the desired edge features. We’re happy to support you with selecting, setting up and optimising a CDN – get in touch for a no-obligation consultation.