How to choose a hosting region (and why latency is mostly distance)

Before you tune a database or optimise an image, the biggest performance lever you have is where your server sits. Physics sets the floor: data travels at a fixed speed, so distance to your users dominates round-trip time.

**Measure, do not guess.** Run a speed test from the networks your real users are on — mobile carriers matter as much as office fibre — to each candidate region. Look at round-trip time and jitter, not just headline bandwidth.

**Match region to audience, not to your office.** The right question is "where are my users?", not "where am I?". A server in your city is a poor choice if 90% of your visitors are on another continent.

**Use a few common patterns:**

- **Single audience, single region:** put the server as close to them as you can. - **Coast-to-coast users:** pick a geographically central region to minimise the worst case for everyone. - **Global audience:** consider a CDN for static assets and keep the origin near your primary market.

**Do not over-rotate on region at the expense of everything else.** A well-tuned server a little further away usually beats a badly-tuned one nearby. Region sets your floor; caching, compression and query efficiency determine where you land above it.

If you are unsure, start in the region closest to most of your users and keep the option to replicate to a second region later — a private network between regions makes that a configuration change rather than a rewrite.