Ordering from abroad?

Location gets asked about because of latency, and latency is the part of the answer that matters least. Browser to server and back across Western Europe costs tens of milliseconds. That is real and measurable, and it is dwarfed by one oversized hero image or a theme that pulls in four font files. Moving a server five hundred miles closer usually buys back less time than deleting one plugin.

Distance does bite in two places. Uncached requests — a dashboard login, a checkout step, a search query reaching the database — make the full return journey every time, so an editor working all day feels a gap a reader never notices. And the further out you go, the steeper the gradient: the difference between Dublin and Warsaw is small, the difference between Dublin and Karachi is not.

The practical rule: choose your origin for the audience you actually have, then let caching flatten the rest. A cached page can be served from an edge node near the reader wherever the origin sits, which is why one well-run facility beats a scattered fleet of slow ones.

The address of a machine settles which courts, regulators and disclosure regimes can reach whatever it holds. That question is not the speed question, and it does not share the speed answer. The machines are in London and the company on your invoice is a British one, which puts the processing under UK law and the ICO in charge of holding us to it.

On most sites it amounts to a paragraph in a privacy notice, not a choice anybody agonises over. It becomes a decision when somebody else sets your rules: a public-sector tender, a client's security questionnaire, an insurer, or a data protection impact assessment naming permitted countries. Where that is the brief, read the requirement first. Discovering it after the invoice has cleared helps nobody.

Residency is the tighter form of the same question — not which law reaches the data, but which country the bytes actually occupy. Ours is one answer — London — and it does not change by plan, by region or by how much you spend. There is no menu of locations here and we would rather say so on the hub than let you find out at checkout.

For the overwhelming majority of sites that is fine, including every business whose customers only want the page to open. It does not suit a project under a rule requiring storage inside a named country. Where that applies, caching cannot rescue it, and a provider running a single facility is simply the wrong shape for the brief.

Country-code endings carry eligibility rules that have nothing to do with hosting, and they are the most genuinely local part of this whole decision. Some registries want a registrant established in the region — .fr expects an EU or EEA presence — while others, .es and .nl among them, hand the ending to anybody who asks. Brexit closed .eu to UK residents and left it wide open to anybody ordering from Dublin, Berlin or Lisbon.

We register a specific list rather than everything, and each country guide names the endings we can genuinely get you along with the year-one price from the live list. Where we cannot supply the national ending, the guide says so in the same sentence rather than steering you toward a .com and hoping you do not notice.

The gap that catches people out is rarely technical. Countries keep their own payment habits: iDEAL in the Netherlands, BLIK in Poland, Bizum in Spain, Multibanco in Portugal. Our checkout takes cards and nothing else. Where the rail you normally reach for is one we cannot process, that belongs on the first page you read — so each country guide names it plainly.

The desk is open at every hour and answers in English, aiming at 2 hours for a first reply and 1 hour once a site is down. The cover never changes by country; the overlap does. Lisbon shares our working day almost exactly. Karachi sends its afternoon into our night shift. Both are answered. Only one is answered while you are still sitting at the keyboard.