SEO

CDN

Also called content delivery network, edge network

Edge servers that hold copies of your files so each request is answered close to the visitor, not at your host.

Quick facts: CDN

Category
SEO
Also called
content delivery network, edge network
Level
Intermediate
Affects
Page speed, server load, Core Web Vitals, international reach
Where to see it
PageSpeed Insights, Chrome DevTools Network panel, your CDN provider's dashboard
In this article4
  1. How a CDN works
  2. Why a CDN matters
  3. Common mistakes with a CDN
  4. How to act on it

How a CDN works

Your website lives on one server, in one place. Without a CDN, a request from Sydney or London travels to that server and back for every file the page needs — the HTML, the stylesheet, the fonts, every image. Distance costs time, and the longer the round trip, the longer the visitor stares at a blank screen.

A content delivery network keeps copies of those files on machines in many countries. When someone opens the page, the network routes the request to the nearest of those machines, which already holds a copy and answers immediately. Only when the copy is missing or expired does the request travel back to your own server, which the network calls the origin.

Most networks also do work your host will not: compressing files, serving them over a newer protocol, converting images to smaller formats as they are requested, and absorbing traffic spikes before they reach the origin at all.

Why a CDN matters

Speed is the obvious reason, and it shows up first in time to first byte — the wait before anything at all arrives. Shortening the journey shortens that wait for every visitor who is not sitting beside your server.

It matters more the further your audience sits from your host. A Nepali business selling to Australia, the UK or the Gulf from locally hosted infrastructure is asking every overseas visitor to wait for a long round trip on every file. The reverse is just as true: a site hosted in Europe or the United States serving customers in Kathmandu, most of them on mobile data, gains real time by holding the files closer.

Common mistakes with a CDN

The commonest is treating it as a cure for a slow site. A CDN shortens the journey; it does not make a bloated page lighter or a slow database query quicker. If the origin needs seconds to build the HTML, and the network has to ask the origin for every page, the visitor waits exactly as long as before.

Caching the wrong things comes next. Carts, logged-in dashboards and forms carrying a security token must never be cached, or one visitor is handed another visitor’s response. At the other extreme, caching only images leaves the files that actually block rendering — the CSS and JavaScript — still coming from the origin.

Stale content is the third. Prices, opening hours and corrected articles can sit at the edge long after you changed them, and the person who notices is usually a customer.

How to act on it

Decide what is genuinely static and cache that hard, then name the exceptions explicitly rather than trusting the defaults to guess your checkout correctly. Put a purge step into your publishing routine so an edit reaches visitors the same day it is made. Test from the countries you actually sell to rather than from your own laptop, because a network that performs well in Europe may have nothing near your buyers.

Then check that the network is solving your real problem. If the delay sits in building the page rather than delivering it, the work belongs in hosting, caching and code — which is where a proper page speed review starts, before any network is bolted on.

Do and do not

Do

  • Cache stylesheets and scripts at the edge, not just images
  • Check the network serves the countries you actually sell to
  • Purge the cache whenever prices or content change

Do not

  • Expect a CDN to fix slow server-side code
  • Cache carts, logins or checkout pages without testing
  • Leave stale cached pages live after publishing an update

Questions people ask about this

Does a CDN improve SEO rankings?

Not directly. Google gives you nothing for using one. What a CDN can improve is the thing Google does measure: how quickly the page starts to appear for real visitors. If your pages are already quick for the people who actually visit, the gain is small. If your audience sits far from your server, it can be substantial.

Do I need a CDN if all my customers are in Nepal?

Less than an international site does, but it can still help. If your hosting sits in Singapore, Europe or the United States, every local visitor makes a long round trip for every file. A network with a nearby presence shortens that. If your host is genuinely close and responsive, spend the effort on page weight and images instead.

Will a CDN break my forms or checkout?

Only if it is set to cache pages it should not. Anything personal — a cart, a logged-in area, a form carrying a security token — has to be excluded so each visitor gets a fresh response. Most providers exclude these by default, but the safe move is to submit a real form and complete a real order after switching the network on.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.