How much a London data centre is really worth in milliseconds, when a CDN makes it irrelevant, and the non-speed reason that matters more than either.
"UK hosting for UK customers" is repeated so often that it has stopped being examined. It is broadly right, for reasons that are not quite the ones usually given.
The physics
Light in fibre travels at roughly two-thirds of c, and routes are never straight. Typical round-trip times from a UK domestic connection:
| Server location | Round trip from UK |
|---|---|
| London | 5–15 ms |
| Amsterdam / Frankfurt | 15–25 ms |
| Falkenstein or Helsinki (Hetzner) | 25–40 ms |
| US east coast (Virginia) | 75–95 ms |
| US west coast (Utah, Arizona) | 130–160 ms |
A single 140ms round trip is imperceptible. The problem is that page loads are not one round trip. TLS negotiation alone is two or three, then the HTML request, then each uncached asset that could not be discovered until the HTML arrived. Thirty sequential round trips at 140ms is 4.2 seconds of pure waiting versus 0.3 seconds from London — before the server has done a single millisecond of actual work.
Where the CDN argument breaks down
The usual counter is "put Cloudflare in front and location stops mattering". Half true. A CDN caches static assets at the edge, so your images, CSS and JavaScript come from a UK PoP regardless of where the origin sits.
But the HTML document itself is generated by PHP hitting a database, and on a default configuration that is not cached at the edge at all. Every visitor waits the full transatlantic round trip for the first byte — and TTFB is precisely what Core Web Vitals measures and what the visitor experiences as "the site is slow to start".
You can cache HTML at the edge — Cloudflare APO, full page rules, or a host like Rocket.net that does it by default. But it needs deliberate configuration, and it breaks for anything logged-in: WooCommerce carts, checkouts, member areas and admin all bypass the cache and pay the full latency every time.
What this means in practice
- Brochure site, mostly anonymous traffic, CDN configured properly: a US host is survivable. You will lose a few hundred milliseconds and probably not lose customers over it.
- WooCommerce or any logged-in experience: host near your customers. Checkout cannot be cached and every step of it pays the round trip. This is the case where it genuinely costs money.
- WordPress admin: nothing about wp-admin is cacheable. If your team edits the site daily from Manchester and the server is in Arizona, they will feel it every single day.
The reason that matters more than speed
Data residency. If you handle personal data and sell to UK organisations, "where is the data stored?" appears on procurement forms, insurance questionnaires and DPAs. UK GDPR permits international transfers with appropriate safeguards, so a US host is lawful — it is just a longer conversation, and some buyers will simply prefer the supplier who answers "London".
For public sector work, charities, healthcare-adjacent services and anything regulated, UK or EU hosting removes a question you would otherwise have to answer repeatedly.
The practical shortcut
Several non-UK companies will serve your site from Britain if you pick the region at signup — and most people do not notice the option. Hostinger (London), Namecheap (Nottingham), SiteGround (London, on Google Cloud), DigitalOcean (LON1) and OVHcloud (London/Erith) all offer it. You usually cannot change it later without a migration, so choose carefully at checkout.
Short version: a London data centre is worth having, costs nothing extra with most providers, and matters most for shops, logged-in users and anyone who has to answer a compliance questionnaire. It matters least for a cached brochure site behind a well-configured CDN.
Published 20 August 2026. Prices and ownership change — check the comparison table for current figures, and the provider's own site before buying. No affiliate links anywhere on this site.