Content delivery networks explained

A content delivery network, or CDN, keeps copies of a site’s files on a distributed network of servers in many locations around the world, and serves each visitor from whichever copy is nearest to them rather than always from the original server. Akamai and Cloudflare are two of the best-known CDN providers operating this kind of network at global scale, though a small-business site is more often riding on a CDN bundled invisibly into its hosting or platform than dealing with a major provider directly. This page is about it as a purchasing decision — whether it is already part of a hosting arrangement or something that needs to be added — rather than the underlying physics, which is covered fully in Australian hosting and latency.

Why a CDN is a distribution service across the internet, not a hosting replacement

A CDN does not replace the origin server; it sits in front of it, caching copies of content that does not change per visitor — images, stylesheets, scripts, and often entire static pages. Anything genuinely personalised, or generated fresh for each request, still has to reach the actual origin server regardless of how good the CDN in front of it is. This distinction matters enormously for what a CDN can and cannot fix, covered in full where the physics is explained.

Where a CDN is already included, quietly

Every hosted platform covered in platforms — Shopify, Squarespace, Wix, Webflow — bundles CDN distribution into the subscription as standard, invisible infrastructure; a business on any of these is very likely already using one without having made an explicit decision to. Many managed hosting plans for self-hosted software, and an increasing number of ordinary shared hosting plans, now include basic CDN functionality as well, often through a partnership with a major CDN provider offered at no extra cost.

Where it needs to be added separately

A self-hosted site on shared, VPS or unmanaged hosting without an included CDN service needs one configured explicitly, generally through a CDN provider’s own service layered in front of the existing hosting via a DNS change. Several providers offer a genuinely capable free tier suitable for an ordinary small-business site, which is worth checking before assuming a paid service is required — the free tiers cover the great majority of what a small-business brochure or content site actually needs from a CDN.

What to actually ask

Whether the current hosting plan already includes CDN distribution, and if so, which regions it covers — a CDN with no edge location near Australia delivers considerably less benefit to an Australian audience than one that does. If it is not included, whether adding one is a straightforward DNS-level change or requires a more involved technical migration, and whether the specific plan’s caching rules can be configured to actually cover the pages that matter, rather than only the most generic static assets.

What a CDN does not solve, worth restating here

Checkout pages, account areas, live availability lookups and anything else generated per-visitor still travel the full distance to the origin server regardless of the CDN sitting in front of the rest of the site — a CDN improves browsing speed for content it can cache, and does nothing for the specific interactions a business’s commercial success often depends on most. Australian hosting and latency sets out exactly which requests fall into each category.

Purging a stale cache, briefly

After publishing a genuine content change, a CDN occasionally continues serving an older cached version for a short period until it refreshes — most CDN services provide a manual purge option for exactly this situation, worth knowing about before assuming a change has failed to publish when it may simply be a caching delay.

A CDN does not replace a backup

Because a CDN holds copies of content, it can feel like a form of redundancy, but it is not a substitute for an actual backup — a CDN’s cached copies are for delivery speed, not disaster recovery, and expire or update independently of anything resembling a restorable backup, covered properly in backups: who takes them and where they live.

Security benefits, briefly, beyond speed

Many CDN services also absorb large-scale malicious traffic — including a DDoS (distributed denial-of-service) attack, where a flood of traffic from many sources at once is aimed at knocking a site offline — before it reaches the origin server at all, providing a genuine security benefit alongside the speed advantage. This is also, incidentally, how a CDN can serve video streaming and other bandwidth-heavy content at scale for larger sites, absorbing the load rather than passing all of it to a single origin server — worth knowing about as a secondary reason to use one, separate from the performance case that usually drives the decision.

A one-line summary worth keeping

A CDN makes browsing faster by copying content closer to visitors; it does not make the origin server itself faster, and confusing the two is the most common misunderstanding about what a CDN actually does.

Configuring cache rules correctly the first time

A CDN configured to cache too aggressively can serve stale content after a genuine update, while one configured too conservatively delivers little of the actual speed benefit — the correct balance depends on how frequently a specific site’s content actually changes, and is worth setting up deliberately with whoever manages the technical side rather than left on a generic default.

Checking coverage for the actual audience

A CDN with strong coverage in North America and Europe but a thin presence in the Asia-Pacific region delivers a smaller benefit to a predominantly Australian audience than its global marketing might suggest — worth confirming regional edge locations specifically rather than assuming global coverage is uniform.

Where to go from here

The underlying reason distance affects load time at all, and the full breakdown of what a CDN can and cannot shorten, is set out in Australian hosting and latency. Whether a CDN is worth configuring as part of a new build, and what that adds to the project, is a question for web development services.