Infrastructure
Your site runs from London
Most hosts describe their infrastructure as 'global' and leave you guessing. Ours is one datacentre, and here is what that honestly means depending on where your visitors are.
London
Where your files live
NVMe
Storage on every plan
1
Origin region, stated plainly
Free
CDN available on request
The Trade-Off
One origin, stated openly
Knowing the real answer helps you decide. Guessing at a vague claim does not.
One location, named
A London datacentre runs your site, sitting on the 20i platform. Not 'multiple global locations'. One location, and we would sooner name it than dodge the question.
Distance is physics, not marketing
Roughly 200 km per millisecond is what light manages inside fibre, and no real route runs straight. Sydney stays far from London whoever hosts you.
What we can change
NVMe storage, LiteSpeed caching, and a CDN parked in front of the origin. For most visitors that combination counts for more than raw distance.
Decide before you pay
Should your audience live almost wholly in Australia or East Asia, a host with an origin nearer to them is probably the better fit. Saying so beats taking your money.
Real Distances
Round-trip times from your region
Indicative figures for a well-connected consumer network — a realistic expectation to set, not a guarantee we'd hide behind.
| Your region | Round trip | What it feels like |
|---|---|---|
| United Kingdom & Ireland | 5–15 ms | You cannot tell it apart from a server across town. |
| Western & Northern Europe | 10–35 ms | Properly quick. Against a local host you lose nothing in practice. |
| Eastern Europe & Turkey | 30–60 ms | Browsing and admin work both stay comfortably quick here. |
| US East Coast & Eastern Canada | 70–90 ms | A developer will notice it. On cached pages most visitors never will. |
| West & North Africa | 90–160 ms | How your local routing behaves matters more here than distance from us. |
| US West Coast | 130–150 ms | This is where a CDN earns its keep. Uncached admin work drags. |
| Middle East | 110–140 ms | Fine for content, slower for dashboard-heavy work. |
| South Asia | 120–200 ms | From Pakistan we clocked roughly 200 ms of TCP connect time. Cached pages hold up perfectly well. Admin panels drag. |
| Southeast & East Asia | 160–230 ms | With an audience out here, running a CDN stops being optional. |
| Australia & New Zealand | 250–290 ms | No point on earth sits further from London. Choose this deliberately. |
| South America | 180–210 ms | Cached delivery holds up fine. Round trips to the origin do not. |
One request going out and coming back: that is latency. A single page fires off plenty of them, which is precisely why caching and a CDN outweigh the raw figure.
About the CDN
What it repairs, and what it leaves alone
A CDN is genuinely powerful and routinely oversold. Both halves below are true.
A CDN does fix
- Static files (images, CSS, JavaScript, fonts) delivered out of an edge location sitting near your visitor
- Cached HTML pages, and that covers nearly everything an anonymous visitor will ever see
- Traffic spikes, since a cached response never touches the origin in the first place
A CDN does not fix
- The WordPress admin area, logged-in by definition and therefore never cached at all
- Checkout pages and account pages, on exactly the same grounds
- Database queries, plus any uncached dynamic request, all of which still travel to London
- SSH, FTP and file-manager work, every bit of it talking straight to the origin
Common Questions
Questions about server location
Where exactly is my website hosted?
A London datacentre, on the 20i platform everything here is built on. Shared, WordPress, WooCommerce and email plans all run out of that one location. We put it in writing because 'global infrastructure' tends to mean a single site the host would rather not name, and knowing that belongs before the purchase, not after it.
Does server location matter for SEO?
Less than it once did, and a good deal less than people assume. Google crawls from many places, and what it weighs is the speed your visitors actually meet, not the straight-line kilometres to your server. Real page speed and Core Web Vitals are the measures that count, and caching plus a CDN go straight at both. Which country you rank in is not decided by where the box lives. Your content decides it, your domain decides it, and so do the sites linking to you. German content on a .de domain ranks in Germany whether the files sit in Frankfurt or in London.
My readers are nowhere near London. Does that make it slow?
For most visitors, no, though the truthful answer splits in two. Someone browsing anonymously gets cached pages from an edge location near where they are, so the run to London hardly shows up. Logged-in work behaves differently. The WordPress admin, the checkout, and every dynamic request that cannot be cached must go to London and come back, which means editing posts from Sydney costs you about a quarter-second of round trip on each click. Your readers get the quick version of the site. You, the one administering it, wear the distance.
Which problems does a CDN solve, and which does it leave?
Static files and cached HTML: images, stylesheets, scripts, fonts, and whatever an anonymous visitor sees. Those come off an edge location sitting close to that person, and for most sites that is the bulk of the traffic. Anything uncacheable stays untouched by it. The WordPress admin area, the checkout, account pages, database queries, SSH and FTP work all reach the origin in London every time. A host telling you a CDN makes location irrelevant is overselling the thing.
Can I choose a different server location?
Not today. One London origin is what we run, and pretending there is a menu of locations would be dishonest. Where a local origin is genuinely essential to your project, expect us to say so rather than sell you a poor fit. For the majority of sites, putting a CDN in front of London is the trade that gives you more for the money.
How do I measure the speed myself before committing to it?
Point an independent speed test at one of our live pages from wherever you are, then run it again from the region your audience sits in. Plenty of free tools let you choose the testing location for yourself. That hands you a real number instead of a claim from us. Each plan carries a 30-day money-back guarantee too, so put your own site on it and measure the thing in earnest. Numbers no good for your audience? Take the refund.
Measure it against your own site.
Thirty days to measure real speed from your real audience. If the numbers don't work for you, take the refund — no argument.
See Hosting Plans