What is content delivery network (CDN)?
A content delivery network (CDN) is a group of servers spread across many cities that keep copies of your site’s files and serve them from the location nearest each visitor.
Want to know where your site stands on CDN?
I’ll test your site on a real mid-range phone profile and send you the two or three fixes that matter most, free.
In plain English
Without a CDN, every visitor fetches your site from one server, wherever it happens to be. With one, images, scripts and often whole pages are cached at “edge” locations around the world. Someone in Montréal gets files from a nearby edge rather than a data centre in Oregon.
CDNs also absorb traffic spikes and many block common attacks before they reach your origin server. Most modern hosts for static sites include one by default.
Why it matters for a small business
Distance adds delay. For a business serving clients across Canada, a CDN keeps the site quick in Halifax and Vancouver alike. It also means a mention on the local news or a busy promo day doesn’t take the site down.
An example
A Winnipeg tour operator’s site is hosted on a single server in Europe because that’s where the original developer lived. Visitors in Canada wait noticeably for every image. Putting the site behind a CDN cuts TTFB and image load times across the country with no change to the design.
Common mistakes
Where I see CDN go wrong most often.
Caching pages that contain personal or logged-in content, so one visitor sees another’s data.
Forgetting to clear the CDN cache after an update, then wondering why changes aren’t showing.
Assuming a CDN fixes a slow site when the real problem is oversized pages.
CDN, answered
It still helps. Even local visitors benefit from fast edge servers, and many good hosts include a CDN at no extra effort.
No. Hosting is where the original files live. A CDN sits in front and distributes copies. Some platforms bundle both.
Keep reading
- nick@tavro.ca
- 587-439-9994
- Calgary, Alberta