Short answer
A CDN speeds up cached content for distant visitors. A faster server speeds up everything else — checkout, admin, search, logged-in pages. If your audience is far away, get a CDN. If your uncached pages are slow, no CDN will help.
Key takeaways
- A CDN buys you distance. A faster server buys you everything else.
- A CDN cannot speed up checkout, cart, admin or any logged-in page — those always reach your origin.
- In our dataset SiteGround is 67ms slower at the origin than Cloudways, yet 120ms faster globally.
- If your uncached pages are slow, fix the server first: cache misses still hit it.
This is the most consequential misunderstanding in web performance, and it costs people money in both directions — some buy a CDN that cannot fix their problem, others skip one when it was precisely the answer.
The two things solve different bottlenecks. Once you can name yours, the decision is obvious.
What each one actually does
#A faster server reduces the time your origin takes to build a response: PHP execution, database queries, the work that happens before a single byte goes out. It improves every request, for every visitor, everywhere.
A CDN stores copies of your content in data centres around the world and serves the nearest copy. It removes distance — but only for content that can be cached, and only after that content has been cached.
The catch is in that last sentence, and it is where the confusion lives.
The worked example
#Our ranking table contains a pair that demonstrates this better than any explanation.
| US origin TTFB | Global TTFB | |
|---|---|---|
| Cloudways | 118ms (fastest measured) | 312ms, no CDN |
| SiteGround | 185ms | 192ms, CDN enabled by default |
SiteGround’s server is 67ms slower than Cloudways’. Yet a visitor in Sydney or São Paulo will typically get a faster page from SiteGround — because its stack puts a CDN in front by default and Cloudways does not.
This is why our rankings show two separate TTFB columns instead of blending them into a single score, and why the methodology ranks on origin TTFB — it is the only column that measures the server rather than the delivery network in front of it.
The full trade-off between those two providers is worked through in Cloudways vs SiteGround.
Which bottleneck do you have?
#Answer these honestly.
Where are your visitors? Check your analytics by country. If 80% are in one region and your server is in that region, distance is not your problem and a CDN will do less than you hope. If your traffic is spread across continents, distance is a real cost you are paying on every request.
What are they requesting? A blog, a brochure site, documentation — content that is identical for every visitor — caches beautifully. A logged-in dashboard, a cart, a search results page, a checkout cannot be cached, so every one of those requests goes to your origin regardless of what CDN you run.
Is your uncached response slow? Run the cached-versus-uncached test. If your uncached TTFB is 800ms, a CDN will make your homepage feel quick and leave every important page exactly as slow as it was.
The decision
#| Your situation | What you need |
|---|---|
| International audience, mostly cacheable pages | CDN. Biggest single win available to you. |
| Regional audience, slow uncached pages | Faster server. A CDN barely touches this. |
| International audience, slow uncached pages | Both — and fix the server first, because cache misses still hit it. |
| Regional audience, fast uncached pages | Neither. Your bottleneck is front-end weight: images, scripts, fonts. |
| Store or membership site, any audience | Faster server, then a CDN for static assets. Your revenue pages are the uncacheable ones. |
If you decide you need a CDN
#You have three routes, and the differences matter less than people assume.
Add one yourself. Cloudflare’s free tier is a genuine global network and takes about fifteen minutes to set up by changing your nameservers. For most sites this is the right answer, and the improvement from no CDN to free CDN is far larger than any subsequent upgrade.
Buy your host’s add-on. Convenient, integrated with their caching, and typically $5–15/mo. Worth it if you would rather not manage another service.
Choose a host that bundles one. Premium managed hosts include enterprise CDN access in the plan price. Kinsta posts the fastest global figure in our dataset at 184ms largely for this reason — that is the packaging, not a magically faster server. Its origin TTFB is 132ms, behind Cloudways.
That trade-off — cheaper server plus your own CDN, versus a pricier plan with one included — is the substance of Cloudways vs Kinsta.
What a CDN will not do
#Worth being explicit, because vendors rarely are:
- It will not speed up your admin area. Those pages are never cached.
- It will not speed up checkout, cart or account pages, for the same reason.
- It will not fix a slow database. Cache misses still wait for your origin.
- It will not rescue a heavy front end. Four megabytes of images is four megabytes of images whether it comes from Frankfurt or Virginia.
- It will not make an overloaded server cope. It reduces load, which can buy you headroom, but a server that is already struggling on uncached requests will keep struggling.
The summary
#A CDN buys you distance. A faster server buys you everything else.
Most sites benefit from a CDN and it is cheap enough that the decision is usually easy. But it is a delivery optimisation layered on top of your hosting, not a substitute for hosting that works — and the pages that make you money are usually the ones a CDN cannot touch.
Diagnose first: is it your host or your site? Then, if the server is genuinely the constraint, the speed rankings compare eight managed cloud hosts on origin response time with the CDN variable stripped out.
Common questions
Does a CDN make my website faster?
For visitors far from your server, requesting content that can be cached — yes, dramatically. For anything that has to be generated fresh, such as a cart, a login or an admin page, a CDN adds nothing because those requests still travel to your origin server.
Is the free Cloudflare plan good enough?
For most sites, yes. The free tier gives you a genuine global edge network and covers the main use case. Paid tiers add configurability and better routing, but the jump from no CDN to free CDN is far larger than the jump from free to paid.
If I have a CDN, does my hosting speed still matter?
Yes, for two reasons. Every cache miss goes to your origin, and any page that cannot be cached always does. A CDN raises your floor for cached content; it does not raise your ceiling for everything else.
Why do some hosts include a CDN and others don't?
It's a packaging decision. Premium managed hosts tend to bundle one, which is why their global figures look strong out of the box. Others leave it to you, which is cheaper up front but means their default global performance is worse until you add one.