Geography, Measured
UK vs US hosting — latency follows your audience, not your flag
Light in fibre crosses the Atlantic in about 35 milliseconds, and no engineering budget changes that. The decision is about whose requests pay the toll — and a first-visit handshake pays it several times over.
The short answer
Host where your audience is: a UK-audience site belongs on UK servers, a US-audience site on US servers, and the marketing address of the company matters not at all. The physics is fixed — roughly 70 ms round trip London to New York, 130 ms or more to the US west coast — and a new visitor's connection spends multiple round trips on TCP and TLS handshakes before the first byte of HTML moves. Cross-ocean hosting quietly adds a couple of hundred milliseconds to every first impression.
A CDN narrows the gap for static assets by serving them from edge nodes near the visitor, but the HTML itself — the document everything else waits for — still comes from your origin unless you deliberately cache it at the edge. For a split audience, host with the majority, let the CDN carry the assets, and check the field data by country before believing anyone's averages, ours included.
By the HostingFast team · Reviewed 25 August 2026
~70 ms
London–New York round trip, before any work happens
×3
Round trips a first visit can spend before the first byte
5–15 ms
A UK visitor's round trip to our London platform
CDN
Equalises static assets — not uncached HTML
Server location is the rare performance factor no code can compensate for. Every optimisation on this site — caching, storage, transport — works to shave milliseconds off processing time; distance adds its milliseconds before processing begins, on every uncached request, for as long as you host there.
The numbers are stable and public: fibre carries signals at about two-thirds the speed of light, London to New York and back costs roughly 70 ms, and reaching the US west coast roughly doubles it. What turns those figures into a decision is multiplication — handshakes, redirects and API calls each pay the toll again. This page does the arithmetic for a typical first visit and shows where a CDN does and does not rescue a bad placement.
Latency compounds before your server does any work
A first-time visitor's browser must complete a TCP handshake and a TLS negotiation before requesting the page — call it two to three round trips on a typical HTTPS setup, fewer with TLS 1.3 and HTTP/3, more with a redirect in the chain. At 12 ms per round trip from London to London, the overhead is imperceptible. At 140 ms from London to California, the page has lost nearly half a second before the server has read the request.
This is why time to first byte cannot outrun geography: TTFB includes the network journey, and the journey is priced per round trip. The same platform, byte-for-byte, measures dramatically differently depending on which side of an ocean the measurement stands.
Host near the audience, not the head office
The only coordinates that matter are your visitors'. A UK e-commerce site hosted in a US data centre taxes every customer a couple of hundred first-visit milliseconds for no compensating benefit; the reverse arrangement taxes Americans identically. Where the company is registered, where the founders live, where the brand feels at home — none of it moves a packet.
Audience location is in your analytics, settled in one look. For sites serving one country predominantly — the common case for local businesses, national retailers and regional services — this is the easiest correctly-sized decision in hosting.
What a CDN equalises, and what it cannot
A CDN copies your static assets — images, CSS, scripts, fonts — to edge nodes worldwide, so those files serve from near the visitor wherever the origin sits. Since assets are most of a page's bytes, this is a genuine equaliser, and it is why 'we have a CDN' is the standard answer to the location question.
The unequalised remainder is the HTML document: generated per request, served from the origin, and — critically — the first resource in the waterfall, the one whose arrival unblocks everything else. Edge-caching HTML is possible with deliberate configuration and careful bypasses for logged-in and cart traffic, but as a default it is not what a CDN does. The origin's location keeps setting the floor under first contentful paint.
Split audiences, and reading the field data
Serving the UK and the US together, the measured playbook is: origin with the larger or more valuable audience, CDN for assets everywhere, and — if the minority's numbers genuinely hurt — edge-cached HTML for anonymous traffic as the targeted fix. Moving the origin mid-Atlantic helps neither side; hosting decisions are majoritarian.
Verify with field data rather than a test run from your own desk: Core Web Vitals broken down by country show what each audience actually experiences. Our platform serves from London — 5 to 15 ms from most of the UK, 10 to 35 ms from western Europe — which is the right answer for UK-audience sites and the wrong one for a site selling only to Texas. We would rather you place the workload correctly than buy the flag.
London hosting, for audiences the round trip favours
Our platform serves from London, which puts most of the UK within 15 ms and western Europe within 35. Stacked with LiteSpeed's cache answering HTML from memory, a UK visitor's first byte arrives with almost nothing left to optimise.
The location claim is one you can test from where you sit: ping the platform, curl a hosted site, read the TTFB. Geography is the most verifiable promise in hosting — no benchmark methodology arguments, just the speed of light and a traceroute.
- London platform — single-digit round trips for much of the UK
- LiteSpeed cache on top, so short trips carry fast responses
- HTTP/3 native, trimming handshake round trips where they cost most
- Verifiable from your own terminal before you spend anything
Why HostingFast
Standard on every plan
The TTFB floor, lowered
Network distance is the part of TTFB no server tuning reaches. Hosting beside your audience removes it at the source.
First visits that feel it most
Handshakes multiply the round trip, so new visitors — the ones forming an impression — gain the most from proximity.
Honest about the map
London is the right origin for UK and European audiences. If yours is elsewhere, we will say so rather than sell against physics.
Quick Start
From order to online
- 1
Locate your audience in analytics
One report settles it: sessions by country. The origin belongs with the majority, and the decision is usually not close.
- 2
Measure the current toll
TTFB from your audience's region against TTFB from beside your server — the difference is what distance is costing every uncached request.
- 3
Place the origin, then let the CDN mop up
Host with the majority, serve assets from the edge, and re-check country-level field data a month later to confirm the floor moved.
Built In
Loaded onto every plan
- Audience geography confirmed from analytics, not assumed from the brand
- TTFB measured from the audience's region — your own desk is not a data point
- Origin placed with the majority audience; ties broken by revenue, not sentiment
- CDN serving static assets, with cf-cache-status or equivalent verified as HIT
- HTML strategy explicit: origin-served by default, edge-cached only with careful bypasses
- Field data by country reviewed after any move — the only scoreboard that counts
Frequently Asked
What people ask us most often
How much does hosting across the Atlantic actually cost in speed?
Around 70 ms per round trip to the US east coast, 130 ms or more to the west — and a first HTTPS visit spends two to three round trips on handshakes before the page is even requested. In practice, transatlantic hosting adds roughly 150 to 400 ms to a new visitor's first byte, on every uncached page, forever.
Doesn't a CDN make server location irrelevant?
For static assets, largely yes — they serve from edge nodes near the visitor. For the HTML document, no: it comes from your origin unless you have deliberately configured edge caching with bypasses for logged-in and cart traffic. HTML arrives first in the waterfall and unblocks everything else, so the origin's location still sets the floor.
Does server location affect SEO?
Indirectly but genuinely: Core Web Vitals are assessed from field data — real visitors' experiences — and distance raises TTFB, which feeds LCP. Google geotargets by TLD and Search Console settings rather than server IP, so the ranking pathway is the speed your distant audience actually experiences, not the address itself.
Where should I host if my audience is genuinely split?
With the larger or higher-value share, plus a CDN for assets everywhere. If the minority market's numbers measurably suffer, edge-cache HTML for anonymous traffic as the targeted fix — it is far cheaper than multi-region origins and solves most of the pain. What helps nobody is a mid-point origin equidistant from everyone.
How do I test a host's real-world latency before signing up?
Ping their platform and traceroute to it from your own connection — or better, from a testing service in your audience's region. Then curl a site they already host and read time_starttransfer, three runs, middle value. Distance shows up in the first hop-count and milliseconds; no marketing page is required.
Keep reading
UK web hosting
The London platform this page measures — single-digit UK round trips, cache on top.
Domains
Names, DNS and the other half of what a visitor resolves before connecting.
HTTP/2 vs HTTP/3
The handshake round trips this page counts — and how QUIC removes one.
Measured buying guides
More decisions settled with numbers you can re-run yourself.
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.
Put the ocean on someone else's waterfall
London origin, LiteSpeed cache, HTTP/3 — measure the round trip from your own terminal, then migrate free and watch the TTFB floor drop.
View Measured buying guides plans