Placing an order from abroad?

People raise the location question because they are worried about latency. It is usually the answer that matters least. A browser talking to a server elsewhere in Western Europe finishes the round trip in tens of milliseconds: real, measurable, and dwarfed by whatever an unoptimised hero image adds, or a theme that drags in four font files. Shift the box five hundred miles nearer your reader and you claw back less time than deleting a single plugin would give you.

Two things do suffer. Anything that cannot be cached (a dashboard login, a step through checkout, a search query that hits the database) travels the full journey out and back on every single hit, so an editor working at it all day feels a lag their readers never register. Push further from the origin and the curve steepens as you go. Dublin to Warsaw barely shows up in the numbers. Dublin to Karachi shows up plenty.

Here is the working rule. Choose an origin that suits the audience you have today rather than the one you hope for, then let caching iron out everything after that. Once a page is cached, an edge node close to the reader can hand it over whichever city the origin happens to occupy. One properly run facility beats a scattered fleet of sluggish ones.

The location of a server determines which courts, which regulators and which disclosure regimes can reach the data held on it. Speed is a separate question, and it carries a separate answer. Our machines sit in London, and the company that issues your invoice is registered in England and Wales, so UK law governs the processing and the ICO holds jurisdiction over what we do.

On most sites this ends up as a line in the privacy notice rather than a choice anyone agonises over. It turns into a choice the moment somebody else writes your rules: a public-sector tender, a client's security questionnaire, an insurer, or a data protection impact assessment that lists the permitted countries. Where that is the brief, read the requirement before you pay, not once the invoice has cleared.

Residency narrows the jurisdiction question down: not whose law reaches the data, but which country the bytes physically occupy. We have one answer, London, and it stays the same whatever plan you take, whichever region you order from, and however much you spend. No menu of locations exists here. Better you read that on the hub than turn it up at the checkout.

For the vast majority of sites that works, and it certainly works for any business whose customers only want the page to appear. It falls down on a project bound by a rule demanding storage inside a named country. Should yours be one of those, caching will not rescue you, and a provider running a single facility is simply the wrong shape for the work.

Country-code endings come with eligibility rules that owe nothing to hosting, and they are the one genuinely local part of this whole decision. Certain registries insist the registrant be established in the region: .fr wants an EU or EEA presence. Others, .es and .nl among them, will hand the ending to whoever asks. Brexit took .eu away from UK residents, though a buyer sitting in Dublin, Berlin or Lisbon can still register it.

Our registry list is specific rather than exhaustive. Each country guide spells out which endings we can genuinely obtain for you, alongside the year-one price pulled straight from the live list. Where the national ending is one we cannot supply, that guide admits it in the same breath, instead of nudging you across to a .com and trusting you never check.

What trips buyers up is almost never technical. Each country has its own payment habit: iDEAL in the Netherlands, BLIK in Poland, Bizum in Spain, Multibanco in Portugal. Our checkout takes cards. If the rail you reach for by default is one we cannot process, you deserve to learn that on the first page you open, which is why every country guide names it outright.

Support answers in English at any hour, and we aim at a first reply inside 2 hours, or 1 hour where a site has gone down. Country changes the overlap, not the cover. From Lisbon your working day sits neatly on top of ours; from Karachi your afternoon arrives during our overnight shift. Both tickets get a reply. Only one of them gets it while you are still at the keyboard.