Skip to main content
Claim your .com from $2.99 — free WHOIS privacy included

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

Your site runs from a London datacentre on the 20i platform. Not 'multiple global locations' — one, and we would rather tell you which.

Distance is physics, not marketing

Light in fibre covers roughly 200 km per millisecond, and real routes are never straight. No host can make Sydney close to London.

What we can change

NVMe storage, LiteSpeed caching and a CDN in front of the origin. Together these matter more than raw distance for most visitors.

Decide before you pay

If your audience is almost entirely in Australia or East Asia, a host with a local origin may suit you better. We would rather say that than take the order.

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.

Indicative round-trip latency from each region to the London origin
Your regionRound tripWhat it feels like
United Kingdom & Ireland5–15 msIndistinguishable from a server in the same city.
Western & Northern Europe10–35 msGenuinely fast. No practical disadvantage against a local host.
Eastern Europe & Turkey30–60 msStill comfortably quick for browsing and admin work.
US East Coast & Eastern Canada70–90 msNoticeable to a developer, invisible to most visitors on cached pages.
West & North Africa90–160 msVaries more with local routing than with distance to us.
US West Coast130–150 msA CDN matters here. Uncached admin work will feel slower.
Middle East110–140 msFine for content, slower for dashboard-heavy work.
South Asia120–200 msWe measured ~200 ms of TCP connect time from Pakistan. Cached pages are fine; admin panels drag.
Southeast & East Asia160–230 msA CDN is not optional if your audience is here.
Australia & New Zealand250–290 msThe furthest you can get from London. Be deliberate about this.
South America180–210 msCached delivery is acceptable; origin round trips are not quick.

Latency is the round trip for one request. A page makes many, which is exactly why caching and a CDN matter more than the raw number.

About the CDN

What it fixes, and what it can't

A CDN is genuinely powerful and routinely oversold. Both halves below are true.

A CDN does fix

  • Static files — images, CSS, JavaScript, fonts — served from an edge location near your visitor
  • Cached HTML pages, which is most of what an anonymous visitor ever sees
  • Traffic spikes, because cached responses never reach the origin at all

A CDN does not fix

  • The WordPress admin area, which is logged-in and therefore never cached
  • Checkout and account pages, for the same reason
  • Database queries and any uncached dynamic request, which still travel to London
  • SSH, FTP and file-manager work, which always talks to the origin directly

Common Questions

Questions about server location

Where exactly is my website hosted?

In a London datacentre, on the 20i platform we build on. Every shared, WordPress, WooCommerce and email plan runs from there. We publish this because 'global infrastructure' is a phrase that usually means one location the host would rather not name, and you deserve to know before you buy rather than after.

Does server location matter for SEO?

Far less than it used to, and far less than people assume. Google's crawlers are distributed and it primarily judges the speed your actual visitors experience, not the straight-line distance to your server. What matters is real-world page speed and Core Web Vitals, which caching and a CDN address directly. Server location does not determine which country you rank in — that comes from your content, your domain, and who links to you. A .de domain with German content ranks in Germany whether the files sit in Frankfurt or London.

My audience is far from London. Will my site be slow?

For most visitors, no — but the honest answer has two halves. Anonymous visitors reading cached pages are served from an edge location near them, so the distance to London barely registers. Logged-in work is different: the WordPress admin, checkout, and any uncached dynamic request has to travel to London and back each time, so if you are in Sydney editing posts you will feel roughly a quarter-second of round trip on every action. Your visitors get the fast experience; you, as the person administering the site, carry the distance.

What does a CDN actually fix, and what doesn't it?

It fixes static files and cached HTML — images, stylesheets, scripts, fonts, and the pages an anonymous visitor sees. Those get served from an edge location close to them, which is the bulk of most traffic. It does not fix anything that cannot be cached: the WordPress admin area, checkout, account pages, database queries, or SSH and FTP work. Those always reach the origin in London. Any host claiming a CDN makes location irrelevant is overselling it.

Can I choose a different server location?

Not at present — we run a single London origin, and we would rather be straightforward about that than imply a choice that does not exist. If a local origin is essential for your project, we will say so honestly rather than sell you something that does not fit. For most sites, a CDN in front of London is the better value trade.

How can I check the speed myself before committing?

Run any independent speed test against one of our existing pages from your own location, and test from your audience's region too — several free tools let you pick a test location. That gives you a real measurement rather than our claim about one. Every plan also carries a 30-day money-back guarantee, so you can put your actual site on it and measure properly. If the numbers do not work for your audience, take the refund.

Test it with 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