Infrastructure
Your clients' sites sit in London
Most hosts call their infrastructure 'global' and leave you to guess. Ours is one datacentre. Here is what that honestly means, depending on where your visitors are.
London
Where the files sit
NVMe
Drives on every plan
1
Origin, and we name it
Free
CDN, ask and it's on
The Trade-Off
One origin, said out loud
A real answer helps you decide. A vague claim only helps the host.
One location, and we name it
A London datacentre on the 20i platform is where your files sit. One location, not 'multiple global locations', and you deserve to know which.
Distance is physics, not a feature
Down a fibre, light manages roughly 200 km per millisecond, and real routes bend rather than run straight. Nobody can shorten London to Sydney.
The parts we can actually change
NVMe storage, LiteSpeed caching, and a CDN parked in front of the origin. Those three matter more to most visitors than raw distance does.
Weigh it up before you buy
Should nearly all of your visitors sit in Australia or East Asia, a host with a local origin is probably the better fit. Saying that costs us the order, and we say it anyway.
Real Distances
The round trip from where you sit
Indicative figures for a well-connected consumer network — an expectation worth setting, not a promise to hide behind.
| Where you are | Round trip | How that feels |
|---|---|---|
| United Kingdom & Ireland | 5–15 ms | Set it beside a box on your own street and nothing would feel different. |
| Western & Northern Europe | 10–35 ms | So fast that shifting to a host nearby would gain you nothing. |
| Eastern Europe & Turkey | 30–60 ms | Easy browsing at this level, and admin screens behave themselves. |
| US East Coast & Eastern Canada | 70–90 ms | A developer notices the lag here. Anyone arriving on a cached page never will. |
| West & North Africa | 90–160 ms | How your ISP routes the traffic shifts this number more than the miles between us. |
| US West Coast | 130–150 ms | Stick a CDN out front. Uncached admin screens will still drag. |
| Middle East | 110–140 ms | Content reads fine; dashboard-heavy work slows down. |
| South Asia | 120–200 ms | Out of Pakistan we measured roughly 200 ms just to open a TCP connection. Cached pages hold their own. Admin panels grind. |
| Southeast & East Asia | 160–230 ms | When your audience sits here, running without a CDN stops being a real choice. |
| Australia & New Zealand | 250–290 ms | Short of leaving the planet, nothing sits further from London. Order it knowing that. |
| South America | 180–210 ms | Serving from cache works well enough here. A trip back to the origin does not. |
Latency measures the round trip for a single request. One page fires off plenty of them, which is exactly why caching and a CDN weigh more heavily than the raw figure.
About the CDN
What a CDN fixes, and what it will not
A CDN is genuinely useful and routinely oversold. Both columns below are true.
It does fix
- Images, CSS, JavaScript and font files, all of them handed over by an edge node sitting near your visitor
- HTML held in cache, meaning most of what any logged-out visitor ever sees
- Traffic spikes, because a response served from cache never reaches the origin server
It doesn't fix
- Your WordPress admin area, logged in by definition and therefore never cached
- Checkout and customer account pages, logged in and thus stuck outside the cache
- Database queries and any dynamic request that misses the cache still travel to London
- SSH sessions, FTP transfers and file-manager work, which always talk straight to the origin
By Country
What all this means where you sit
Latency from London, the domain endings we register locally, the currency prices display in, and the tax position — country by country.
Common Questions
Questions about where we host
So where does my site actually run?
In a London datacentre, on the 20i platform underneath everything we sell. Shared, WordPress, WooCommerce and email plans all run out of there. We print the fact because 'global infrastructure' nearly always means a single location the host would sooner not name, and you ought to know that before paying rather than afterwards.
Does where the server sits affect SEO?
Much less than it used to, and far less than most people assume these days. Google crawls from many places and weighs the speed your actual visitors get, not the straight-line distance to the machine. Real page speed and Core Web Vitals are what count, and caching with a CDN in front handles both. Nor does location decide which country you rank in. That falls out of your content, your domain and whoever links to you. A .de domain carrying German writing ranks in Germany whether its files sit in Frankfurt or in London.
My visitors sit nowhere near London. Will the site drag?
For most of them, no. The answer does come in two halves, though, and both halves are true. An anonymous visitor reading a cached page is served from an edge location near them, so London hardly comes into it. Logged-in work is a different story: the WordPress admin, the checkout, and anything dynamic that will not cache has to travel to London and back on every action. Edit posts from Sydney and you will feel roughly a quarter of a second each time you click. Your visitors get the quick version. You, sitting at the admin screen, carry the distance.
What does a CDN really fix?
Static files and cached HTML: images, stylesheets, scripts, fonts, and the pages an anonymous visitor lands on. All of that comes from an edge close by, and it makes up the bulk of most traffic. Uncacheable work is beyond its reach, meaning the WordPress admin, the checkout, account pages, database queries, SSH and FTP sessions. Every one of those reaches the origin in London, every single time. A host telling you a CDN makes location irrelevant is selling past the facts.
Can I pick a different location?
Not today. One London origin is what we run, and saying so plainly beats dangling a choice that does not exist. Where your project genuinely needs a local origin, you will hear that straight from us rather than be sold something that does not fit. For most sites, a CDN sitting in front of London is the better buy anyway.
How do I check the speed for myself first?
Aim any independent speed test at one of our live pages from wherever you are, then run the same test from your audience's region. Several free tools let you pick the test location. That hands you a measurement rather than our word for it. Hosting plans carry a 30-day money-back guarantee as well, so put the real site on one and measure it properly. Should the numbers fail your audience, take the refund.
Put your own site on it and measure.
Thirty days to test real speed from your real audience. If the numbers don't work, take the refund — we won't argue.
Browse Hosting Plans