What Is a CDN? How It Speeds Up Websites

Clients ask me “what is a CDN?” more often than almost any other hosting question, and my answer always starts with the same story. The first time I really understood what a CDN does, I was not reading documentation. I was sitting in a client’s office in Makati, watching their new website load. The site was hosted in a data center in Virginia, and it took close to five seconds to show anything useful. The developer kept saying the server was fast. He was right. The problem was the 14,000 kilometers between that server and the laptop on the desk in front of us.

We put a content delivery network in front of the site that afternoon. Nothing about the code changed. The next morning, the same page loaded in a little over a second.

That gap between “the server is fast” and “the website feels slow” is exactly what a CDN exists to close. In this guide I will explain what a CDN is, how it works under the hood, where it helps, where it does not, and what a business should look at before choosing one. I write technical documentation for a living, so I will try to keep the jargon honest: explained when it appears, and left out when it is not needed.

What Is a CDN, in Plain Terms?

A CDN, or content delivery network, is a group of servers spread across many cities and countries that keep copies of your website’s files close to the people visiting it. Instead of every visitor pulling every file from your one main server, most visitors get those files from a server that is physically near them.

The HTTP Archive, which studies millions of websites every year, describes it this way: a CDN is a geographically distributed network of servers designed to provide high availability, enhanced performance, and improved security for web content and applications, and its primary goal is to minimize latency by serving data from locations closer to the end user.

Three CDN Terms Worth Knowing

Origin server. This is your actual web server, the one your hosting company runs, where the original copy of your site lives.

Edge server. This is a CDN server sitting in a city near your visitors. It holds cached copies of your files.

Point of presence (PoP). This is a physical location, usually a data center, where a CDN keeps a cluster of edge servers. A big provider may have hundreds of these around the world.

If you want a picture, think of a bakery with one kitchen in the city center and small display counters in every neighborhood. The kitchen still bakes everything. But nobody has to drive downtown for a loaf of bread anymore.

Why Websites Need a CDN: Physics, Not Server Power

Many people assume a slow website means an underpowered server. Sometimes that is true. Very often, though, the bottleneck is distance, and no amount of extra RAM fixes distance.

Light inside fiber optic cable travels at roughly two thirds of its speed in a vacuum, which works out to about 200 kilometers every millisecond. A request from Manila to a server on the US East Coast covers well over 14,000 kilometers each way, and real cable routes are never straight lines. So before your server does any work at all, you are already looking at well over 100 milliseconds for a single round trip.

And a webpage is not a single round trip. The browser first has to look up the domain name. Then it opens a connection. Then it negotiates encryption so the page can load over HTTPS. Only after all of that does it ask for the actual page, and then it goes back for the stylesheets, scripts, fonts, and images. Every one of those steps pays the distance tax again.

This is why a CDN matters so much. It does not make light travel faster. It shortens the trip.

How a CDN Works, Step by Step

Here is what actually happens when someone visits a website that sits behind a CDN.

Step 1: The Browser Looks Up Your Domain

When your site uses a CDN, your DNS records point to the CDN rather than straight to your origin. The CDN’s DNS system figures out which edge location is best for that visitor, usually the closest healthy one. CDN DNS infrastructure may use routing strategies such as anycast or unicast to direct users to optimal edge servers. Anycast simply means many locations share the same IP address, and the internet’s own routing delivers each visitor to the nearest one.

Step 2: The Browser Connects to a Nearby CDN Edge Server

That connection, including the encryption handshake, happens over a short distance. This alone saves a surprising amount of time.

Step 3: The CDN Edge Checks Its Cache

If the edge server already has a fresh copy of the requested file, it sends it back immediately. That is called a cache hit.

If the file is not there, the edge fetches it from your origin. That is a cache miss. The edge server requests the file, delivers it to the visitor, and keeps a copy for the next person in that region.

Step 4: The Copy Stays Until It Expires or Is Cleared

Every cached file has a time to live, or TTL, which tells the CDN how long the copy is considered fresh. When you update your site, you can also purge the cache so visitors get the new version right away.

Tiered CDN Caching and Origin Shields

Larger CDNs add a middle layer often called an origin shield or tiered cache. Instead of every edge server in the world hitting your origin on a cache miss, they ask a regional parent server first. This keeps your origin from getting flooded the moment you publish something popular.

What a CDN Actually Caches (and What It Does Not)

This is where I see the most confusion, so it is worth slowing down.

Static Content a CDN Can Cache

Static content is anything that is the same for every visitor: images, CSS files, JavaScript files, fonts, PDFs, and video segments. These are perfect for caching because they rarely change. This kind of content doesn’t change frequently, making it a good candidate for caching on CDN proxy servers.

Dynamic Content

Dynamic content is anything built fresh for each visitor: a logged in dashboard, a shopping cart, a search results page, account details, live pricing. You generally do not want an edge server handing one customer’s cart to another customer, so this content is usually passed through to the origin.

The HTTP Archive’s 2025 data shows this pattern clearly. Third party resources lead CDN adoption at 71%, subdomain requests sit at 52%, and HTML content has the lowest CDN usage at 35%, since it is more commonly served directly from origin servers.

Why Uncacheable Pages Still Get Faster on a CDN

Here is the part many explainers skip: even when content cannot be cached, a CDN can still make it faster. For content with limited cacheability, CDNs still deliver performance improvements through connection optimization, intelligent routing, and edge processing, reducing latency even when content cannot be cached. The visitor only has to set up a quick connection to a nearby edge, and the edge keeps a warm, persistent connection back to your origin over a well tuned network path.

How a CDN Speeds Up Websites Beyond Caching

Caching gets the headlines, but modern CDNs do a lot of quieter work that adds up. A few of the improvements I explain most often to clients:

Faster Encryption Handshakes

Every HTTPS connection begins with a TLS handshake. When that handshake happens with a server down the street instead of one across an ocean, it finishes much sooner. The HTTP Archive measured this directly. On desktop, the median TLS negotiation time for CDNs was 57 milliseconds versus 177 milliseconds for origins, more than three times faster. On mobile, the median for CDN was 183 milliseconds, while for origin servers it was 302 milliseconds.

CDNs also tend to run the newest protocol versions. Nearly all CDN traffic now uses TLS 1.3, with 99% of requests using the latest protocol version.

Quicker CDN DNS Responses

Before a page can even start loading, the browser has to resolve your domain name. CDNs run large, globally distributed DNS systems, and it shows. The 2025 data showed CDNs delivering DNS responses 19% faster on mobile and 60% faster on desktop compared with origin servers.

Newer Web Protocols Without Touching Your Server

HTTP/3 is the newest version of the protocol browsers use to talk to servers. It runs on a transport called QUIC, which handles packet loss better and needs fewer round trips to start a connection. HTTP/3 reduces connection setup from the three round trips of HTTP/2 to one, through QUIC’s integrated cryptographic handshake.

Most businesses would struggle to roll that out on their own servers. A CDN does it for you. In the HTTP Archive dataset, CDNs saw 29% of HTML traffic over HTTP/3, compared with effectively 0% for origin traffic.

Smarter Compression

Text files like HTML, CSS, and JavaScript compress very well, and smaller files arrive faster. Many CDNs compress files at the edge using modern algorithms. Brotli offers 20 to 26% better compression than Gzip, and CDNs served 46% of mobile requests with Brotli, while origins still served 61% with Gzip.

CDN Image Optimization on the Fly

Images are usually the heaviest part of a page. Many CDNs can now detect what a visitor’s browser supports and convert images automatically. Most CDNs now detect browser capabilities and serve the most optimized format available, such as AVIF or WebP, with JPEG as a fallback for older browsers. For a content heavy site, this single feature can cut page weight dramatically without anyone resizing a single file by hand.

Reliability and Security: The CDN Benefits People Forget

Speed is the reason most teams sign up for a CDN. Reliability and security are usually the reasons they stay.

Handling Traffic Spikes With a CDN

When a press mention or a campaign sends a sudden wave of visitors, a CDN absorbs most of the load at the edge. Your origin only sees the cache misses. Without a content delivery network, all of that traffic must be absorbed by a content provider’s own infrastructure.

Built In Failover

Because a CDN has many servers in many places, the loss of one location does not take your site down. Traffic simply shifts to the next best one. That redundancy makes a CDN a practical piece of any disaster recovery plan for your web presence.

CDN Attack Protection

Because a CDN sits between the public internet and your server, it is a natural place to filter bad traffic. The most advanced content delivery networks provide cloud based security solutions and DDoS protection. Many also include a web application firewall and bot management. Google’s own developer guidance notes that CDNs typically provide security features such as DDoS protection, WAF services, and SSL termination.

Security Headers at the Edge

Because CDNs sit between users and origin servers, they can insert or modify security headers regardless of what the origin provides, which makes good security practice easier to roll out across an entire site.

Who Actually Uses a CDN?

Short answer: most of the web you visit every day, and more of it each year.

The top 1,000 websites have the highest CDN usage at 71%, followed by the top 10,000 at 70%, and the top 100,000 at 62%. Adoption is climbing among smaller sites too, and the reason is cost. The HTTP Archive attributes this rise to free, flat tier, or affordable CDN options, and notes that many hosting solutions now bundle CDNs with their services.

The market itself is concentrated among a handful of providers. The leading vendors for serving base HTML requests are Cloudflare with a 58% share, followed by Google at 21%, Amazon CloudFront at 7%, Fastly at 5%, and Akamai and Vercel at 2% each.

Why a CDN Matters for Professional Services Firms

If you run a consulting firm, an agency, an accounting practice, or an IT services company, you might think a CDN is something only streaming platforms and big online stores need. I disagree, for three practical reasons.

Your website is your first meeting. A prospective client often forms an opinion of your firm before they ever call you. A slow site quietly signals a firm that does not sweat the details.

Your clients are probably not all in one city. Professional services firms increasingly work across regions. If your site is hosted in Singapore and your newest client is in Toronto, that client is getting the slow version of your brand.

Page speed feeds into search visibility. Google’s Core Web Vitals measure real visitor experience, including how quickly the main content appears. A CDN is one of the most direct ways to improve the time to first byte that every other metric depends on.

There is also a less glamorous benefit. Your proposal PDFs, case study downloads, and recorded webinars are large files. Serving them from the edge reduces bandwidth charges at your host and keeps your server free to do real work. If you rely on an outside provider for IT support for small business, ask them to include CDN setup and monitoring in their scope.

CDN vs Web Hosting vs Edge Computing

These three get blurred together constantly, so here is how I separate them for clients.

Web hosting is where your website lives. It runs your application, your database, and your content management system. You always need hosting.

A CDN sits in front of your hosting and delivers copies of your content from locations near your visitors. It does not replace your host. It reduces how often visitors need to reach it.

Edge computing goes one step further and runs actual code on the CDN’s servers. Unlike traditional CDN caching, edge computing executes arbitrary code at edge locations, enabling dynamic responses, personalized content, A/B testing, authentication, and real time data manipulation without contacting origin servers. Most major CDN providers now offer both, and a typical pattern serves static assets through CDN caching while routing dynamic requests to edge functions for processing.

For most small and midsized business websites, a well configured CDN is the right place to start. Edge computing becomes worth exploring once you have a specific problem it solves, such as localized pricing or redirect logic you want to run before a request ever reaches your server.

How to Choose a CDN: A Practical Checklist

When I help teams evaluate providers, I steer the conversation away from marketing claims and toward these questions.

Where Are Your Visitors?

Look at your analytics first. A provider with excellent coverage in North America but thin coverage in Southeast Asia is the wrong fit if half your traffic comes from the Philippines and Indonesia. Ask for a PoP map and check the cities that matter to you.

How Does CDN Pricing Work?

Some providers charge per gigabyte delivered, some per request, some offer flat monthly plans, and some have generous free tiers. Many CDN providers offer pricing plans based on usage, so estimate your monthly bandwidth before comparing quotes. If a managed provider runs your CDN for you, factor that line item into your overall managed IT services cost.

How Fast Can You Purge the CDN Cache?

When you fix a typo on your homepage, you want the change live in seconds, not hours. Check how quickly the provider can invalidate cached content and whether you can purge a single file or only everything.

What Security Is Included?

Find out whether DDoS protection, a web application firewall, and free SSL certificates come standard or cost extra.

Does the CDN Fit Your Stack?

If your site runs on WordPress, check for a maintained plugin. If you live inside AWS or Google Cloud, their native CDNs may be simpler to manage. Google’s guidance is sensible here: select a CDN provider that aligns with your application’s requirements, geographic reach, and performance needs, then configure DNS records, set up your origin server, and specify your caching preferences.

What Reporting Do You Get?

You will want to see your cache hit ratio, bandwidth, top requested files, and blocked threats. Without data, you are guessing.

Common CDN Mistakes I Keep Running Into

Turning a CDN on is easy. Getting the full value out of it takes a little more care. These are the problems I see most often when I audit setups.

Caching Nothing Useful

Some sites put a CDN in front and leave the default settings, which may only cache a narrow set of file types. The CDN is running, but the hit ratio is poor and the origin is still doing most of the work.

Caching Too Much

The opposite mistake is worse. If you cache pages that contain logged in information, one visitor can end up seeing content meant for another. Always exclude account pages, carts, checkout, and admin areas.

Using One CDN TTL for Everything

Your logo might not change for a year. Your homepage might change every week. Giving both the same expiry time means either stale content or needless trips to your origin. Set longer TTLs for versioned assets and shorter ones for HTML.

Forgetting to Purge After Updates

Teams publish a change, refresh the page, see the old version, and assume the update failed. Build cache purging into your publishing routine.

Leaving the Origin Exposed Behind the CDN

If attackers can find your origin’s real IP address, they can go around the CDN entirely. Lock your origin down so it only accepts traffic from your CDN provider’s network.

Never Measuring

I have met teams who turned on a CDN years ago and never checked whether it helped. Test before and after, from more than one location.

How to Measure Whether Your CDN Is Working

You do not need an expensive monitoring platform to get a useful answer.

Check Your CDN Cache Hit Ratio

Start with your provider’s dashboard. For a typical marketing or content site, most static file requests should be hits. If the ratio is low, your caching rules need attention.

Read the Response Headers

Open your browser’s developer tools, load your site, and look at the response headers on your images and scripts. Most CDNs add a cache status header that tells you whether a file was a hit or a miss.

Test From Several Regions

Run your homepage through a public speed testing tool from several regions, ideally one close to your origin and a couple far away. The difference between those results is roughly what your CDN is buying you. Then keep an eye on your Core Web Vitals report in Google Search Console over the following weeks, since that reflects real visitors rather than lab tests.

A Final Word on What a CDN Can Do

A CDN is one of the rare infrastructure changes that delivers a visible result without a rebuild. It shortens the distance between your content and your visitors, takes load off your server, adds a layer of protection, and quietly brings modern protocols to a site that might otherwise never get them.

It is not magic, and it does not fix a bloated page or slow database queries. But if your audience is spread across more than one city, and for most businesses today it is, a properly configured CDN is no longer an optional upgrade. It is part of running a professional website.

That afternoon in Makati, the client asked me why nobody had suggested a CDN sooner. I did not have a good answer then, and honestly, I still do not.

Frequently Asked Questions About CDN

What is a CDN in simple words?

A CDN is a network of servers in many locations that keeps copies of your website’s files near your visitors, so pages load from a nearby server instead of one far away. The MDN Web Docs glossary entry on CDNs gives a short, reliable definition.

Does a CDN replace my web hosting?

No. Your host still runs your website and stores the original files. The CDN sits in front of it and delivers cached copies. You need both. Cloudflare’s explainer on what a CDN is walks through how the two work together.

Will a CDN make every page faster?

Mostly, yes, but by different amounts. Static files see the biggest gains from caching. Dynamic pages that cannot be cached still benefit from faster connections and better routing, as the 2025 Web Almanac CDN chapter explains in detail.

Is a CDN worth it for a small business website?

Usually, yes, especially if your visitors are spread across regions. Many providers offer free or low cost plans, and many hosts bundle a CDN with their packages. Google’s guide to CDNs for content driven web apps covers how to evaluate fit.

Does a CDN help with SEO?

Indirectly, yes. Search engines factor in page experience, and a CDN improves load times and server response, which feed into Core Web Vitals. Faster pages also tend to keep visitors around longer. See web.dev’s article on content delivery networks for the performance side.

Is a CDN secure?

A reputable CDN generally improves security by filtering malicious traffic, absorbing DDoS attacks, and handling encryption at the edge. Akamai’s overview of what a CDN is describes the security role in more depth.

What is the difference between a CDN cache hit and a cache miss?

A cache hit means the edge server already had a fresh copy of the file and served it instantly. A cache miss means it had to fetch the file from your origin first. A higher hit ratio means a faster site and a lighter load on your server. AWS’s explanation of CDNs covers caching behavior clearly.

References

Sarah Whitmore

Administrator

Technology writer for Foretec.com, covering IT infrastructure, networking, cybersecurity, and practical technology solutions for modern businesses.

View All Posts

Related News

SD-WAN vs MPLS: How to Choose the Right WAN for Your Business

IT Asset Management: How to Track Hardware and Software From Request to Retirement

How to Build a Disaster Recovery Plan That Actually Works Under Pressure

You may have missed

What Is a CDN? How Content Delivery Networks Make Websites Faster