What It Actually Means
Distance costs time. A request travelling to another continent and back adds delay that no amount of server performance removes, because the limit is physics rather than processing.
What It Actually Does For You
Speed, mostly for distant visitors. If your server is in London and your customers are in London, the gain is modest. If you have visitors elsewhere, it is significant.
Load taken off your server. Images, stylesheets and scripts are served by the network, so your server handles only the parts that need it. On a media-heavy site this is most of the traffic.
Resilience against spikes. A sudden surge is absorbed by the network rather than by your hosting.
Protection. Most CDNs sit in front of your site and filter malicious traffic, which is a genuine benefit and frequently the main reason smaller businesses end up using one.
Free certificates and modern protocols, usually included and enabled without effort.
The Predictable Problem
Stale content, and it is the same issue as any other caching layer with one extra step: the copies are distributed, so clearing them means clearing everywhere.
The pattern is familiar. An image is replaced, the site still shows the old one, and the person who made the change sees the new version because their browser bypasses the cache. The fix is purging the CDN, which is a button, and knowing it exists is most of the battle.
The version that causes real damage is caching pages that should be personal. A CDN configured to cache whole pages on a site with logged-in users can serve one person’s page to another. That is not a performance bug, it is a data exposure, and it needs the exclusions checked deliberately rather than assumed.
Do You Need One
For a small business site serving one country, on decent hosting, the honest answer is that it is optional. It will help somewhat and it is not the thing holding the site back.
It becomes clearly worthwhile when you have international visitors, a media-heavy site, unpredictable traffic, or you want the security filtering. Since the entry-level offering from the main providers is free, the cost side of the decision is close to zero, which is why most sites end up with one regardless.
What To Ask
- Is it caching anything personalised? The one that matters.
- How do we purge it after a change? Someone should know before it is needed.
- Is it configured, or just switched on? Default settings are safe and conservative; most of the benefit needs a few decisions about what to cache and for how long.
- Where are our visitors? Decides how much benefit there is to have.
- Does it sit in front of everything? If the site is behind it but an application or API is not, the protection is partial.
What It Does Not Fix
A CDN speeds up delivery of files. It does not make a slow application fast.
If pages are slow because the database is doing too much work or the code is inefficient, the CDN serves the static parts quickly and the page still waits for the slow part. That distinction matters when a CDN is proposed as the answer to poor performance scores: it helps with some of the measurements and none of the underlying cause.
More terms are in the glossary.
