What is a CDN and when it really speeds up a web page
Published on 2026-10-20 by frfrand
Una CDN acerca imágenes, CSS y otros recursos a tus visitantes. Cómo funciona la caché, cuándo ayuda, cuándo no y errores que conviene evitar.
A CDN (content delivery network) is a set of servers distributed across different regions that can deliver copies of website files from locations close to the visitor. This usually reduces the distance traveled by images, stylesheets, and scripts, and can also reduce the load on the main server.
Imagine a photography website hosted in Portugal that receives visits from Mexico. Without a CDN, images are usually requested from the original server. With a well-configured CDN, some files can be served from a network node located closer to the person requesting them.
How it works?
The server that hosts the original files is known as the origin. The distributed nodes are called points of presence or edge servers. When someone requests an image, the node checks if it has a current copy. If it does, it responds; if not, it consults the origin and decides whether to keep the file.
This mechanism is called caching. A cache hit avoids requesting the file again from the origin; a cache miss requires retrieving it. That is why the first request may behave differently from subsequent ones.
What resources can be stored?
The most common candidates are images, CSS files, JavaScript, and web fonts. In certain architectures, public HTML and API responses can also be stored, provided the rules are appropriate.
A cover photo can remain identical for weeks, while the result of a booking changes continuously. It is advisable to establish different policies for each case.
HTTP headers, especially Cache-Control, allow indicating how copies should be treated. Provider rules and the type of request also influence.
Example: an international booking website
Suppose an agency publishes twenty tourist tours, each with large photographs. It receives visits from Portugal, Mexico, and the United States.
A CDN can deliver photographs and style files from locations close to each visitor. But when someone checks if there are places available for tomorrow, that operation normally needs current data at the origin or in a system specifically designed to provide correct responses.
The ideal result is a combination: repeatable resources close to the user and dynamic operations where appropriate.
Does a CDN improve SEO?
Speed and user experience matter, but activating a CDN does not guarantee better positions on Google. If images weigh too much, JavaScript blocks the page, or the server takes too long to generate HTML, those problems can persist.
To evaluate the change, I measured before and after. Check the response time, real user experience metrics, and cache hit rate. A misconfigured CDN can add complexity without perceptibly improving a website whose audience is already close to the origin.
What invalidating the cache means
You published a new image with the same name, but some visitors are still seeing the previous one. It's a classic case: the old copy is still considered valid.
You can wait for it to expire, purge it using the provider's tools, or publish a different URL, such as foto-v2.webp or a hashed name. This last option allows you to keep long caches without showing outdated content.
It is not advisable to purge the entire site every time an image changes: you lose the cache benefits and the origin receives more requests.
Are CDN, hosting, and reverse proxy the same thing?
No. Hosting runs or stores your site. A CDN distributes content through a network. A reverse proxy receives requests and forwards them to internal servers or the origin; many CDNs work as a reverse proxy, but the concepts are not identical.
What a CDN does not solve
A CDN can improve file delivery, but it does not automatically turn a slow application into a fast one. If the server takes time to generate a page or a database query takes a long time, you need to work on that origin.
A CDN does not replace website maintenance either. It is an additional component worth measuring before and after installing it.
What does a CDN mean for privacy?
There is an important detail when a page uses personal accounts: the cache should never deliver one person's private data to another. It is not just about gaining speed. Responses with session information, payment data, or private reservations need clear storage and access rules. A misconfigured cache can cause leaks even if the backend is properly authenticated.
In a store, the logo and product photos can be shared among visitors. Each shopper's cart contents cannot. That is why you need to consider both HTTP headers and the specific behavior of the provider.
When is it worth installing a CDN?
A CDN usually adds more value if you have visitors spread across different regions, heavy images, lots of static resource downloads, or traffic spikes. If the audience is local and your site already responds quickly from the origin server, it may be better to first optimize images, queries, and JavaScript.
Do not trust an isolated test: compare measurements from representative locations, check cache hits, and monitor server times. The first visit and subsequent ones may behave differently.
And how is this applied in ArduMaker?
A website deployed on an ArduMaker VPS can be hosted on a specific server. If it serves visitors from different regions, you can place a compatible CDN in front and define which resources can be stored temporarily. The decision to configure caches, private content, and expiration policies remains part of your application design.
In one sentence: a CDN helps bring content closer and reduce origin workload, but it only accelerates usefully when you choose well what to distribute and what you should never store as a shared copy.
Sources to learn more: web.dev CDN Guide · Cache-Control on MDN.