Edge delivery · Intermediate · an hour, mostly measuring
How to connect a CDN — A CDN Pays for Itself in Round Trips, or Not at All
You are about to add a caching layer in front of a caching layer, and you have no figure telling you whether your audience is far enough away for it to matter.
The short answer
Measure the round trip from your audience's region before you buy an edge, because a CDN converts distance into cached bytes and does nothing else. Our origin sits in London: indicative round trips run 5–15 ms from the UK and Ireland, 10–35 ms across western and northern Europe, 130–150 ms from the US west coast and 250–290 ms from Australia and New Zealand. Those figures decide the question for you.
The second half of the decision is what an edge cannot help with. Logged-in traffic, the WordPress dashboard, checkout and account screens, database-backed responses and any SSH or FTP session all speak to the origin at full distance. This runbook covers both halves, plus the SSL mode that quietly leaves the origin leg in plaintext.
By the HostingFast team · Reviewed 24 August 2026
Intermediate
Level assumed
5
Stages start to finish
Free
What support costs
Proven
Measured on our own stack
This is a measurement exercise with a purchase at the end, not the other way round. Everything here assumes you can run a timing test from outside your own country and read a response header, both of which are free.
Keep one figure and one list. The figure is time to first byte from your largest audience region. The list is the set of URLs on your site that can never be cached at an edge. If the figure is small and the list is long, the honest answer is that a CDN is not your bottleneck.
Put a number on the distance before buying anything
Time to first byte from a location near your audience is the whole case for an edge. A UK audience on a London origin is already at 5–15 ms; there is no edge node closer than that and no CDN will improve it. From South Asia the same origin sits at 120–200 ms — measured from Pakistan, roughly 200 ms of TCP connect time — and from Australia or New Zealand it is 250–290 ms, which is exactly the shape of problem an edge exists to solve.
Use a synthetic test that lets you choose the origin city, and take three runs from each region rather than one. Then compare a cached HTML response against an uncached one, because the difference between those two on your own site is the ceiling on what any CDN can hand you.
The requests an edge will never help
Images, CSS, JavaScript and fonts come off the nearest node, and so does cached HTML for logged-out visitors, which covers most of a brochure site. That is the win. Traffic spikes flatten too, because a cached response never reaches the origin at all.
What stays at full distance: the WordPress dashboard, because logged-in traffic is never cached; checkout and account screens, uncacheable for the same reason; database queries and any dynamic request that misses; and file-manager, SSH or FTP sessions, which always talk straight to London. If your slow experience is admin work, an edge will not touch it.
Choose the integration style, then refuse flexible SSL
A proxy CDN takes over your DNS and filters every request, bringing a firewall and rate limiting with it. A pull-zone CDN only rewrites asset URLs to a CDN hostname, which your cache plugin can do in one field. The first is more capability and more moving parts; the second is fewer of both.
On a proxy, flexible SSL encrypts only the visitor-to-edge leg and sends the edge-to-origin leg in plaintext. The padlock appears and the guarantee does not exist. Full or strict is the only production setting, and strict is the one that actually validates the origin certificate — which our free, self-renewing SSL supports out of the box.
Two cache layers now, so verify both
After a publish there are two things to purge, in order: the origin cache, then the edge. Get that order wrong and the edge re-fetches the stale page you just purged. Response headers are how you confirm anything happened — the LiteSpeed cache header on the origin, the CDN's own hit/miss header at the edge.
Then re-run the regional timing test you started with. A new moving part has to pay rent in milliseconds; if the numbers from your audience's region have not moved, remove the edge again rather than keeping it because it feels modern.
Where the origin actually is
The platform runs from London, and we publish indicative round trips by region rather than claiming to be fast everywhere — 5–15 ms from the UK and Ireland, 250–290 ms from Australia and New Zealand. Knowing the number is what makes the CDN decision an arithmetic problem instead of an argument.
Free SSL on every plan, reissued automatically before it can expire, which is what strict origin validation needs.
- A published latency figure per region, not a claim about speed
- LiteSpeed cache at the origin, in front of any edge you add
- Free auto-renewing SSL, so strict mode works day one
- DDoS filtering absorbed at the network edge already
Why HostingFast
Standard on every plan
The decision is arithmetic
Published round trips by region from a London origin, so you can settle the question with a number instead of a hunch.
What an edge cannot fix, stated plainly
Dashboard, checkout, account screens and every database query still run the full distance. Better to know before the invoice.
SSL modes without the fudge
Flexible mode is named as the trap it is, and the origin certificate you need for strict mode is already installed and renewing.
Two layers, one purge order
Origin first, edge second, verified by response header — which is the difference between a stale page and a fixed one.
Origin caching already in place
LiteSpeed is compiled into the server, so the edge sits in front of a fast origin rather than papering over a slow one.
Reversible in one field
The pull-zone route is a hostname in the cache plugin. If the measurement disagrees, taking it out is as quick as putting it in.
Quick Start
From order to online
- 1
Time it from your audience's region
Three synthetic runs from the country that sends you the most traffic, cached and uncached. Against a London origin, anything under about 35 ms leaves an edge almost nothing to win.
- 2
List what can never be cached
Dashboard, cart, checkout, account, search, and any endpoint behind a login. If that list is where your slowness lives, stop here and tune the origin instead.
- 3
Pick proxy or pull zone deliberately
Proxy takes DNS and brings a firewall; pull zone rewrites asset URLs from one plugin field. Choose on how much you want in the request path.
- 4
Set full or strict SSL, never flexible
Flexible leaves the origin leg unencrypted behind a padlock. Strict validates our certificate properly, and that certificate is free and self-renewing.
- 5
Verify headers, then re-run the timings
Confirm an edge hit and an origin cache hit in the response headers, then repeat the opening measurement. No movement in the regional figure means no reason to keep the layer.
Built In
Loaded onto every plan
- LiteSpeed caching compiled into the server, not bolted on by plugin
- Free SSL on every plan, reissued automatically before it can expire
- DDoS filtering absorbed out at the network edge
- NVMe SSD storage on every tier, including the entry plan
- cPanel — the control panel most of the industry already runs
- Staging environments for rehearsing a change before it ships
- Per-site PHP version switching from the control panel
- Daily backups on every plan, with restores you run yourself from the panel
- 99.9% uptime as the target, monitored around the clock
- Human support on duty every hour of every day
Frequently Asked
What people ask us most often
How do I measure time to first byte from a country I am not in?
Use a synthetic test that lets you pick the test location, and take at least three runs because single samples are noisy. Compare a cached HTML response with an uncached one from the same location: the gap between those two is the most a CDN can possibly give you, and it is often smaller than expected.
Which response header proves a request was served from the edge?
Every CDN sets its own cache-status header on the response — read it in the DevTools Network panel or with a curl -I. Check the origin's LiteSpeed cache header in the same response too, because a hit at the edge and a miss at the origin tell you very different things about where your next purge belongs.
Will a CDN speed up the WordPress dashboard?
No. Logged-in traffic is never cached, so wp-admin, checkout and account pages travel the full distance to the origin every time. Long editing sessions from far away feel slow for that reason, and the fix is a faster origin, a lighter admin, or accepting the round trip — not an edge.
What is the practical difference between full and strict SSL?
Full encrypts the edge-to-origin leg but accepts any certificate, including a self-signed one. Strict encrypts it and validates the certificate properly, which is what you want in production. Our free SSL renews itself before expiry, so strict works from day one without a manual step in your calendar.
Keep reading
How to Secure Your Hosting Account
Harden the one account that holds every site you run — keys, two-factor, and the sessions worth revoking — beginner, roughly 30 minutes.
How to Set Up an Email Autoresponder
Automatic replies that answer once, quote sensibly and never loop with another autoresponder — beginner, roughly 10 minutes.
CDN (Content Delivery Network) (Glossary)
The mechanism behind edge delivery, with the request types it can never help.
VPS Hosting
KVM virtual servers with root access, DDoS filtering and one flat monthly price.
WordPress Hosting
WordPress on LiteSpeed and NVMe, with staging clones and daily backups included.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Start with an origin worth caching.
LiteSpeed compiled into the server, NVMe underneath, free auto-renewing SSL and a published latency figure for every region.
View VPS Hosting plans