What is a CDN? Caching and CDNs explained in plain language

Caching and a CDN make your site faster by reusing work instead of redoing it for every visitor, and by keeping your files physically closer to that visitor. Caching means storing a ready-made copy so the next request gets it immediately. A CDN (Content Delivery Network) is a worldwide network of servers that distributes those copies, so that someone in Antwerp does not have to wait for a server in the United States. In this article you will read, in plain language, what both are, which caching layers exist, how they work together on load time and uptime, and when they genuinely pay off for a B2B company.

What is caching in plain language?

Caching means keeping a copy of something you have just created, so you do not have to create it again next time. Imagine your website having to build a full page on every visit: fetching data, assembling the layout, preparing images. That costs time and computing power. With caching, you do that work once, store the result, and serve that copy at high speed to everyone who comes along afterwards.

You can 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, but after that things go much faster. The core idea is simple: avoid repeated work. The more often something is requested and the less often it changes, the more you gain from caching.

Which caching layers does a website have?

A typical site caches at several levels at once, each one closer to or further from the visitor. Those layers work together, not instead of one another.

• Browser cache. Your visitor’s browser stores files such as your logo, fonts and scripts locally. On a second visit it does not have to download them again, which makes repeat visits noticeably faster.
• CDN or edge cache. The CDN keeps copies of your files on servers spread around the world, close to the visitor. More on that further down.
• Server or page cache. On your own server you store complete, fully built pages. Instead of assembling a page from scratch every time, you deliver a stored version.
• Application and object cache. An intermediate layer that stores the outcome of heavy operations, for example the result of a database query, so the site does not have to recalculate it on every request.

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, and a page your server has to rebuild costs the most time.

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. Without a CDN, your site sits on a server in one fixed location. Someone far away then has to wait while the data physically covers that distance, and the internet is fast but not infinitely fast. A CDN solves that by copying your static files, think of images, fonts, scripts and stylesheets, to nodes (often called “edge” servers) that sit closer to the visitor.

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. A CDN often does more than just speed things up: it can compress files, secure connections and slow down malicious traffic before it reaches your own server.

Important to understand: a CDN is essentially a form of caching itself, only geographically distributed. It does not cache your files on your server or in the browser, but 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?

Together they tackle the two biggest causes of slowness: too much repeated work and too much distance. Caching removes the repeated work, a CDN shortens the distance. The combination means most requests are handled without your own server having to do any heavy lifting.

That also has consequences for your uptime, in other words the time your site is reachable. When a CDN handles the bulk of the traffic from its cache, your own server gets far fewer requests to process. During a sudden peak, for example after a campaign or a mention in the press, the CDN absorbs that wave instead of letting your server buckle. And if your origin server goes down for a moment, a CDN can in many cases still show a cached version, so visitors do not run into an error message.

The effect is measurable in the numbers that Google and your visitors look at. Fast, stable pages score better on Core Web Vitals, the signals that measure the loading experience. If you want to know where your site stands today, a free test as described in our explanation of Google Lighthouse helps you see where you are losing time.

Why does this matter for a B2B website?

For a B2B site, speed is not a technical detail but a conversion factor. Your visitors are often decision-makers with little patience, and every second of waiting increases the chance they drop off before your form or your offer is on screen. A site that loads slowly undermines trust before anyone has read a single word. We deliberately steer our clients on leads and revenue, and load time is one of the simplest levers for gaining ground there without changing anything about your message.

On top of that, a lot of B2B visits today happen on mobile and on the move, where connections are more erratic. That is exactly where caching and a CDN make the biggest difference, because they depend less on a perfect connection to a distant server. Loading faster means more people actually seeing the page, more people clicking through, and ultimately more completed forms.

Do you always need a CDN, and do you have to set it up yourself?

For most business sites the answer to the first question is yes, and to the second usually no. Many modern website platforms and hosting providers ship caching and a CDN by default, without you having to configure anything by hand. If you build on a managed platform, the basics are often simply included. If you work with a self-hosted setup, for example your own server configuration or a headless architecture, a CDN is generally a deliberate choice you add.

The honest nuance: caching is powerful, but it is not free in terms of complexity. The classic pitfall is that a visitor sees an old, cached version of a page after you have changed something. Good systems solve this with “cache invalidation”, the targeted refreshing of the copy as soon as the content changes. That is exactly the kind of technical foundation you are better off having set up properly than repairing afterwards. Building a fast site is not about a trick, but about a well-considered setup of those layers together, something that belongs to solid web design and that we also cover in our guide to having a B2B website built.

The short summary

Caching lets your site reuse work instead of redoing it for every visitor, and 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 is making the most of this foundation?

Schedule your free intake