CDNs Explained: When Your Website Actually Needs One

Your website loads instantly for you in New York, but a customer in Singapore waits five seconds for the same page. That gap is where a CDN earns its keep — or doesn't, depending on who you serve and how your site is built.

Let's get specific about what a CDN actually does, when it's worth setting up, and when you're better off spending that money elsewhere.

What a CDN Actually Is

A CDN (Content Delivery Network) is a global network of servers that store copies of your website's static files — images, CSS, JavaScript, fonts, sometimes full HTML pages — and serve them to visitors from the location closest to them.

Instead of every visitor pulling files from your single origin server (let's say it's in Virginia), a visitor in Tokyo gets those files from a Tokyo edge server. The result: faster page loads, less strain on your hosting, and protection against traffic spikes.

What gets cached on a CDN

• Static assets: images, video, PDFs, fonts
• Stylesheets and scripts: CSS and JavaScript files
• Cached HTML: entire pages, when configured (great for blogs and marketing sites)
• API responses: some CDNs cache GET requests with proper headers

What doesn't get cached

• Logged-in user dashboards
• Shopping cart and checkout pages
• Real-time data (live chat, stock prices)
• Personalized content based on cookies or sessions

The Real Performance Difference

Numbers matter here. Without a CDN, a 200KB hero image hosted in Virginia might take:

• New York visitor: 80ms
• London visitor: 320ms
• Sydney visitor: 850ms
• Mumbai visitor: 920ms

With a CDN, those numbers drop to roughly 40-80ms across the board. Multiply that across 30+ assets on a typical page, and you're looking at a 2-4 second difference for international visitors.

Google's Core Web Vitals — which influence search rankings — measure things like Largest Contentful Paint (LCP). A CDN directly improves LCP for image-heavy pages.

When Your Website Needs a CDN

You should set up a CDN if any of these apply:

1. You have international visitors. Check your analytics. If more than 15-20% of traffic comes from outside your hosting region, a CDN pays for itself in conversions.
2. Your site is media-heavy. Photography portfolios, e-commerce with product galleries, real estate listings, video content — all benefit massively.
3. You run paid ads. Every second of load time costs you conversions. If you're spending $500+/month on ads, slow loads waste budget.
4. You've had traffic spikes. A press mention, viral post, or seasonal rush can crash an unprotected origin server. CDNs absorb most of that traffic.
5. You need DDoS protection. Modern CDNs like Cloudflare include attack mitigation by default.
6. Your hosting is in one region but customers aren't. Common for businesses using cheap shared hosting.

When You Probably Don't Need One

Don't add complexity you don't need:

• Local service businesses serving one city or region, with hosting in the same country
• Brochure sites under 5 pages with minimal images and low traffic
• Sites already on platforms with built-in CDNs (Shopify, Webflow, Squarespace, Vercel, Netlify all include CDN delivery)
• Internal tools and dashboards used by a small team in one location

Popular CDN Options and Real Costs

Cloudflare

The most common choice for small businesses. Free tier covers most needs: global CDN, basic DDoS protection, SSL, and analytics. Paid plans start at $20/month for image optimization and advanced caching rules.

Bunny.net

Pay-as-you-go pricing starting around $0.01 per GB. Excellent for media-heavy sites where you want predictable costs without a free tier's limitations. A typical small business site costs $1-5/month.

AWS CloudFront

Powerful but complex. Best if you're already on AWS. Pricing is around $0.085 per GB for the first 10TB. Overkill for most small businesses.

Fastly

Developer-focused with edge computing features. Pricing starts at $50/month minimum. Good for SaaS and apps, less suited to simple websites.

Setting Up a CDN: What's Involved

For most small business websites, the process looks like this:

1. Sign up for a CDN provider (Cloudflare is the easiest starting point)
2. Change your domain nameservers to point to the CDN — typically two DNS records to update at your registrar
3. Configure caching rules — what to cache, for how long, what to bypass
4. Enable performance features — Brotli compression, image optimization, HTTP/3
5. Test thoroughly — check that forms still submit, logged-in areas work, and analytics still fire correctly

For a WordPress site, you'll typically also install a plugin like WP Rocket or W3 Total Cache that integrates with your CDN. For custom-built sites, the configuration lives in your build pipeline or hosting platform.

Common setup mistakes to avoid

• Caching pages that contain user-specific content (you'll show one user's data to another)
• Setting cache TTLs too long — updates won't reflect for days
• Forgetting to purge the cache after deploying changes
• Not configuring an origin shield, causing repeated misses to slam your server
• Leaving development URLs cached publicly

Measuring Whether It Worked

Before flipping the switch, record baseline numbers:

• Run PageSpeed Insights on your top 3 pages and save the scores
• Test from multiple locations using WebPageTest
• Note your Time to First Byte (TTFB) and LCP

After setup, run the same tests. You should see TTFB drop significantly for distant locations, LCP improve on image-heavy pages, and total page weight stay similar (a CDN doesn't reduce file size unless you also enable optimization features).

If you're not seeing improvement, the bottleneck is somewhere else — usually unoptimized images, heavy JavaScript, or render-blocking resources. A CDN can't fix bad code; it just delivers it faster.

Get Help Setting It Up Right

A CDN is one of the highest-impact performance wins for the right kind of site — but configured badly, it can break checkout flows, leak stale content, or do nothing measurable at all. At Axoxweb, we build sites with performance baked in from the start, including proper CDN integration tuned to how your business actually operates.

If you want a fast, modern website that works as hard as you do, visit axoxweb.com to talk through your project.