What is a CDN, and why does your static site need one?

A CDN, content delivery network, is a network of servers spread across many physical locations that all keep copies of your site's files, so a visitor's request gets served from whichever location is geographically closest to them, rather than from one single origin server that might be sitting on the other side of the planet.

Why distance matters for load time

Every request has to physically travel, and data doesn't move instantly; the further it has to go, the more latency gets added before the page even starts rendering on screen. A visitor in Singapore requesting a page from a server in Virginia will wait longer than one requesting a page from a server nearby, purely due to distance, independent of how fast the server itself actually is. A CDN removes most of that distance by having a copy ready close to wherever the request happens to come from.

Why this matters especially for static sites

Static files, HTML, CSS, JS, images, are exactly the kind of content CDNs are best at serving: identical for every visitor, safe to cache and duplicate across many locations, since there's no per-request computation that needs to happen at a single "true" origin. A dynamic page that depends on a live database lookup is harder to fully distribute this way; a static file is close to the ideal case for it, which is part of why static sites pair so naturally with CDN delivery.

That's part of why static sites can end up faster than more complex dynamic ones even when the dynamic site runs on more powerful infrastructure underneath. The static site's content is duplicated everywhere it's needed, while the dynamic site's database usually lives in one place, no matter how many edge servers sit in front of it.

What this looks like in practice

If a host serves your site "directly at the edge," that's describing a CDN doing its job. Your files are replicated across multiple points of presence, and a visitor's request is automatically routed to a nearby one rather than a single central server:

You don't configure this yourself; it's part of what the hosting layer handles for you behind the scenes.

What to actually check

You generally don't need to think about CDN configuration directly; what matters is whether your host uses one at all. If a host is serving static content from a single origin server with no edge distribution, visitors farther from that server will notice the lag firsthand. A host built for static content should have this handled by default, not as a paid add-on you have to remember to enable separately.

Frequently asked questions

Do I need to configure caching rules for a CDN myself? Usually not for a static host; sensible defaults for static file caching are typically built in, since the content doesn't change per-request the way dynamic pages do.

Does a CDN affect SEO? Indirectly, yes, since faster load times are a ranking factor and improve user experience, which search engines account for in various ways.

Can a small personal site benefit from a CDN, or is it only for high-traffic sites? Any site benefits from faster loading for visitors, regardless of traffic volume; a CDN isn't a scaling feature reserved for large sites, it's a baseline performance improvement for everyone.