Infrastructure
Your files sit in London
Most hosts label their infrastructure 'global' and leave you guessing. Ours is a single datacentre. Here is what that honestly means, wherever your visitors happen to sit.
London
The city holding your files
NVMe
Storage fitted to every plan
1
Origin, and we name it
Free
CDN, enabled whenever you ask
The Trade-Off
One origin, no hedging
A straight answer helps you decide. A vague one only ever helps the host.
One location, stated plainly
Your files sit in a London datacentre on the 20i platform. Not 'global locations' in the plural — one, and you should know which.
Distance is physics, not marketing
Light covers about 200 km a millisecond in fibre, and real routes wander. No host alive can shorten the run from London to Sydney.
The levers we can actually pull
NVMe storage, LiteSpeed caching and a CDN sitting in front of the origin. For most visitors those count for far more than raw distance.
Decide with the facts first
If almost all your visitors are in Australia or East Asia, a host with a nearby origin probably suits you better. We would sooner say so than take the order.
Real Distances
Round-trip times from your side of the world
Indicative figures on a well-connected consumer line — an honest expectation, not a promise to hide behind.
| Where you are | Round trip | How that feels |
|---|---|---|
| United Kingdom & Ireland | 5–15 ms | Instant. For a British or Irish audience, nothing beats it. |
| Western & Northern Europe | 10–35 ms | Full speed. A server inside your own borders would not improve on it. |
| Eastern Europe & Turkey | 30–60 ms | Quick for visitors, and admin work keeps its rhythm. |
| US East Coast & Eastern Canada | 70–90 ms | Developers may notice the hop. Cached pages land before anyone counts. |
| West & North Africa | 90–160 ms | Your local carrier decides this figure far more than the distance does. |
| US West Coast | 130–150 ms | Front it with a CDN and visitors stay quick. Uncached admin work drags. |
| Middle East | 110–140 ms | Content arrives at a good clip. Long stretches in the control panel lose it. |
| South Asia | 120–200 ms | Measured from Pakistan: roughly 200 ms of TCP connect time. Cached pages keep their speed; the control panel feels every mile. |
| Southeast & East Asia | 160–230 ms | Audience here? Lead with a CDN — the origin alone will not keep up. |
| Australia & New Zealand | 250–290 ms | Almost the opposite side of the planet from London. Decide with that in mind. |
| South America | 180–210 ms | Cache keeps the pages brisk. Anything that must reach London arrives slowly. |
Latency measures one request's round trip. A page fires dozens of them, which is precisely why caching and a CDN matter more than the raw figure.
About the CDN
What it speeds up, and what it can't
A CDN is genuinely useful and routinely oversold. Both columns below hold true.
It does fix
- Images, CSS, JavaScript and fonts, handed to your visitor by the nearest edge node
- Cached HTML, covering almost every page a logged-out visitor opens
- Traffic spikes, because a cached response never touches the origin
It doesn't fix
- The WordPress dashboard — logged-in traffic, so it is never cached
- Checkout and account screens, uncacheable for the same logged-in reason
- Database queries and any dynamic request the cache misses — those run the full distance to London
- File-manager, SSH and FTP sessions, which always speak straight to the origin
By Country
What this looks like from your country
Latency out of London, the domain endings we register locally, the currency prices appear in, and the tax position — one territory at a time.
Common Questions
Questions about our location
Where does my site actually live?
In a London datacentre, on the 20i platform we build on. Shared, WordPress, WooCommerce and email plans all run from there. We say so because 'global infrastructure' nearly always means one location the host would rather not name — and that is something you should know before you pay, not afterwards.
Does server location move the needle on SEO?
Far less than it once did, and far less than most people assume. Google crawls from many points and scores the speed your real visitors get, not the straight-line distance to your machine. Genuine page speed and Core Web Vitals are what count — and caching plus a CDN go at both directly. Location does not decide which country you rank in either; content, domain and inbound links do. A .de domain written in German ranks in Germany whether the files sit in Frankfurt or London.
My audience is far from London. Will things crawl?
For most of them, no — though the honest answer splits in two. Anonymous visitors reading cached pages are served from an edge node near them, so London barely enters into it. Logged-in work is another matter: the WordPress admin, checkout and anything dynamic that cannot be cached takes the round trip to London every time. Edit posts from Sydney and you will feel roughly a quarter of a second per action. Your visitors ride the fast lane; you, at the admin screen, absorb the distance.
What does a CDN actually speed up?
Static files and cached HTML — images, stylesheets, scripts, fonts, and every page an anonymous visitor opens. Those ship from an edge close by, which covers the bulk of most traffic. What it cannot touch is anything uncacheable: the WordPress admin, checkout, account pages, database queries, SSH and FTP sessions. Those reach the London origin every single time. Any host claiming a CDN makes location irrelevant has run past the facts.
Can I choose a different location?
Not today. We run one London origin, and we would rather say that flatly than dangle a choice that does not exist. If your project genuinely needs a nearby origin, we will tell you straight rather than sell you a poor fit. For most sites, a CDN in front of London is the smarter spend.
How can I test the speed myself first?
Point any independent speed test at one of our live pages from where you are, then run it again from your audience's region — plenty of free tools let you choose where the test fires from. That gives you a measurement instead of our word for it. Hosting plans also carry a 30-day money-back guarantee, so you can put the real site on and measure properly. If the numbers do not work for your audience, take the refund.
Put our speed on the clock yourself.
Thirty days to measure real speed for your real audience. If the numbers fall short, take the refund — we will not argue the point.
Browse Hosting Plans