A CDN, explained for owners: what it fixes and what it does not

A delivery network fixes distance, not slowness: a heavy page is slow from the server next door too.

Your site lives on one machine, probably far from some of the people trying to reach it. A visitor in another country asks for your homepage and the bytes crawl across the world to reach them, one ocean at a time. The content delivery network is the market's answer to that distance, and it is sold, as usual, as if it answered everything.

The mechanism is not complicated. Copies of the site's static pieces, the images, the scripts, the heavy files, sit on servers in many places, so each visitor downloads from somewhere near them instead of from one distant machine. What this fixes is distance, the plain physics of waiting for bytes to cross the world. It also fixes resilience: the origin machine is not alone under load, because the copies carry part of the traffic.

What it does not fix is a slow site. A page that is heavy or badly built is slow from nearby too: the visitor waited for the server and now waits for the page itself. Buying a delivery network as a product and keeping the same slow page is the commonest version of this mistake, and the disappointment that follows is deserved, because the slowness was never only distance.

The other failure versions live in configuration. The setup where the cached copies held old files for days because nobody set the refresh rule: updates stay invisible while support insists the site is fixed. And the forgotten subdomain, the one address that kept serving through the old path because it sat outside the review, noticed by nobody until a customer asked why that one page alone was slow.

The practice starts with geography. If your visitors and your server sit far apart, distance is a real cost and the delivery layer earns its place. If they sit in the same city, the win is small and other work comes first. Then set the caching rules deliberately, so updates propagate when you publish instead of whenever the caches feel like it. Keep the same security review over the delivery layer that the main site gets. And measure from where your visitors actually are, not from the office.

Guidance, not guarantees: we place the delivery layer as infrastructure serving a fast page, never as a purchase standing in for one. Whether your traffic is spread thin across countries or gathered in one region, what your caching rules say today, and what a review of the setup would find are things we can work through with you. The physics, at least, makes no promises it cannot keep.