Website & Development
What is a CDN? Caching and CDNs explained in plain language
Copy for AI
A CDN is a network of servers that delivers your files from close by.
So what is a CDN in practice?
CDN stands for Content Delivery Network: a worldwide network that keeps copies of your files near the visitor.
Someone in Antwerp then doesn’t wait for a server in the United States.
Caching is the idea underneath.
It means storing a ready-made copy, so the next request gets it immediately.
The verdict: caching removes repeated work, a CDN removes distance. Together they make your site faster and steadier, and most business sites should use both.
What is caching in plain language?
Caching means keeping a copy of something you’ve just created, so you don’t have to create it again.
Why it saves time
Imagine your website building a full page on every visit. It fetches data, assembles the layout and prepares images.
That costs time and computing power.
With caching, you do that work once and store the result.
Everyone who comes along afterwards gets that copy at high speed.
The baker analogy
Compare caching to a baker who bakes popular loaves in advance, instead of starting the moment a customer walks in.
The first customer might wait a little. After that, things go much faster.
The core idea: avoid repeated work. The more often something is requested and the less often it changes, the more you gain.
For example, your logo is requested on every page and changes maybe once a year.
That’s a perfect file to cache for a long time.
Which caching layers does a website have?
A typical site caches at several levels at once, each closer to or further from the visitor.
Those layers work together, not instead of one another. MDN’s guide to HTTP caching splits them into private caches (the browser) and shared caches (proxies and CDNs).
The four layers
From the visitor outward:
- Browser cache. The visitor’s browser stores your logo, fonts and scripts locally, so repeat visits are noticeably faster.
- CDN or edge cache. The CDN keeps copies of your files on servers spread around the world, close to the visitor.
- Server or page cache. Your own server stores complete, fully built pages and delivers a stored version.
- Application and object cache. An intermediate layer stores the outcome of heavy operations, such as a database query result.
Closer is faster
The closer the cache sits to the visitor, the faster the answer arrives:
- a file from the browser cache is there instantly
- a file from a nearby CDN server is almost instant
- a page your server has to rebuild costs the most time
How the layers know what to keep
Every file tells caches how long they may keep it, through the Cache-Control header. MDN’s Cache-Control reference lists the main instructions:
| Instruction | What it means |
|---|---|
max-age=31536000, immutable | Fresh for a year and never changes: ideal for versioned images and scripts |
s-maxage | How long a shared cache, such as a CDN, may keep it |
no-cache | May be stored, but must be checked with the server before each reuse |
no-store | Must not be stored by any cache |
stale-while-revalidate | May serve an old copy while fetching a fresh one in the background |
MDN’s own stale-while-revalidate example keeps a response fresh for 7 days. After that, caches may reuse it for 1 more day while they fetch a new copy in the background.
Visitors never wait for the refresh.
Watch out: no-cache doesn’t mean “don’t cache”. MDN stresses it allows storing but requires a check first.
Use no-store when nothing may be kept.
What exactly is a CDN?
A CDN is a network of servers, spread around the world, that keeps copies of your website files close to your visitors.
MDN defines it as servers in many locations that answer each request from the copy closest to the user.
The problem it solves
Without a CDN, your site sits on a server in one fixed location.
Someone far away then waits while the data physically covers that distance.
The internet is fast, but not infinitely fast.
How it works
A CDN copies your static files to nodes, often called “edge” servers, that sit closer to the visitor.
Think of images, fonts, scripts and stylesheets.
If a visitor comes from Brussels, a nearby node delivers the files. If someone comes from Sydney, a node there does the same.
The content travels a much shorter distance, so the page loads faster.
More than speed
A CDN often does more than speed things up. It can:
- compress files
- secure connections
- slow down malicious traffic before it reaches your server
A CDN is caching too
Here’s the key point: a CDN is essentially a form of caching itself, only geographically distributed.
It doesn’t cache your files on your server or in the browser. It caches them in dozens of places at once, as close as possible to whoever requests them.
How do caching and a CDN improve your load time and uptime together?
They tackle the two biggest causes of slowness: repeated work and distance.
Caching removes the repeated work. A CDN shortens the distance.
The combination means most requests are handled without your own server doing any heavy lifting.
Uptime and traffic peaks
That also affects your uptime, the time your site is reachable.
When a CDN handles most traffic from its cache, your own server gets far fewer requests.
During a sudden peak, for example after a campaign or a press mention, the CDN absorbs that wave.
Your server doesn’t buckle.
When the origin goes down
If your origin server goes down for a moment, a CDN can often still show a cached version of static pages.
Cloudflare’s Always Online feature, for example, serves a stale copy from its cache. Old, but online.
Cloudflare refreshes that copy every 30 days on its Free plan, every 15 days on Pro and every 5 days on Business and Enterprise.
Dynamic content, like a form submission, can’t be served while the origin is offline, though.
Cloudflare also notes it doesn’t keep a copy of every page.
So it isn’t automatic: it depends on your CDN configuration. The standard mechanism is the stale-if-error directive from RFC 5861, which lets a cache serve an expired copy on a 500, 502, 503 or 504 error for a period you set.
So a CDN softens an outage; it doesn’t replace website uptime monitoring.
The effect on Core Web Vitals
The effect is measurable in the numbers Google and your visitors look at.
Fast, stable pages score better on Core Web Vitals, the signals that measure the loading experience.
The first one, largest contentful paint, is where a CDN usually helps most.
Here’s what that field data looks like for our own site in PageSpeed Insights:
PageSpeed Insights field data for customerimpact.be on mobile, October 2026. LCP passes at 1.9 s; CLS at 0.13 still needs work.
Notice the split. It matters. LCP passes, but CLS doesn’t, and no CDN fixes layout shift.
The same story shows in our Search Console:
Our own Search Console, Core Web Vitals on mobile, October 2026. Layout shift, not load speed, keeps 349 mobile URLs out of the green.
For that, read our guide to cumulative layout shift.
The business case
The business case is documented. Google’s web.dev case collection lists several results:
Vodafone saw 8% more sales after a 31% LCP improvement.
The BBC lost an additional 10% of users for each extra second of load time.
And Rakuten 24 saw revenue per visitor rise 53.37% after investing in Core Web Vitals.
Want to know where your site stands today?
A free test, as in our explanation of Google Lighthouse, shows where you lose time.
Why does this matter for a B2B website?
For a B2B site, speed isn’t a technical detail. It’s a conversion factor.
Decision-makers don’t wait
Your visitors are often decision-makers with little patience.
Every second of waiting increases the chance they drop off before your form or offer is on screen.
A slow site undermines trust before anyone has read a word.
We steer our clients on leads and revenue.
Load time is one of the simplest levers there, without changing anything about your message.
Our piece on page speed, SEO and conversion goes deeper into that link.
Mobile makes it matter more
A lot of B2B visits happen on mobile and on the move, where connections are more erratic.
That’s exactly where caching and a CDN make the biggest difference.
They depend less on a perfect connection to a distant server.
For example, say a buyer opens your pricing page on a train between Ghent and Brussels.
With a nearby edge server and cached assets, the page shows up before the signal drops.
Loading faster means more people seeing the page, more clicking through, and more completed forms.
Do you always need a CDN, and do you have to set it up yourself?
For most business sites: yes to the first, usually no to the second.
Often it’s already included
Many modern website platforms and hosting providers ship caching and a CDN by default.
You don’t have to configure anything by hand.
If you build on a managed platform, the basics are often simply included.
Compare the options in managed hosting vs self-hosting and our guide to choosing web hosting.
With a self-hosted setup, such as your own server configuration or a headless architecture, a CDN is a deliberate choice you add.
Which setup needs what
| Your setup | CDN and caching | What to check |
|---|---|---|
| Managed platform | Usually built in | That it’s switched on for images |
| Shared or self-hosted server | Add a CDN yourself | Cache headers and purge options |
| Headless front end | A deliberate choice | Which pages may be cached at the edge |
The classic pitfall: stale pages
Caching is powerful, but it isn’t free in terms of complexity.
The classic pitfall: a visitor sees an old, cached version of a page after you’ve changed something.
Good systems solve this with “cache invalidation”: refreshing the copy as soon as the content changes.
Standard HTTP has no delete command for copies already stored elsewhere, MDN notes. So CDNs offer a purge via dashboard or API.
That’s exactly the foundation you’re better off setting up properly than repairing afterwards.
Get the layers right together
Building a fast site isn’t about a trick. It’s about a well-considered setup of those layers together.
That belongs to solid web design, and we also cover it in our guide to having a B2B website built. Images usually come next: see how to optimize images on your website.
Frequently asked questions
What is the difference between caching and a CDN?
Caching is the principle: keep a copy so you don’t redo the work.
A CDN is one place that applies it, on servers spread around the world.
So every CDN caches, but not every cache is a CDN.
Does a CDN help SEO?
Indirectly, yes. Through speed.
A CDN mostly speeds up loading, which shows in Core Web Vitals such as LCP.
It doesn’t fix layout shift or slow scripts on its own.
Is a CDN worth it for a site that only targets Belgium?
Usually, yes.
Even with nearby visitors, a CDN offloads your server and absorbs peaks.
Check what your host already includes first; our overview of web hosting in Belgium helps.
The short summary
Caching lets your site reuse work instead of redoing it for every visitor.
That happens across several layers: in the browser, on a CDN, on your server and in the application.
A CDN is a worldwide network that keeps copies of your files close to the visitor.
Together they cut your load time, absorb peaks and keep your site more stable.
For a B2B site, that translates directly into more visitors who stay and convert.
Want to know whether your site makes the most of this foundation?
Send us your URL and we’ll check the caching layers with you.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.