A visitor 6,000 km from your server waits on roughly 60 milliseconds of travel time per round trip before your page can even start loading, and opening a new secure connection takes about 3 round trips. Google's web.dev guidance says most sites should aim for a time to first byte (TTFB) of 0.8 seconds or less, so a far-away server spends a noticeable slice of that budget on distance alone (web.dev, Time to First Byte, checked October 19, 2026). For SEO, Google lists server location as one signal of a site's intended audience but calls it "not a definitive signal" (Google Search Central, Managing multi-regional sites). Server location matters for speed far more than for rankings, and a CDN changes the math for both.
Disclosure: HostingDive earns a commission when you buy through links on this page, at no extra cost to you. Commissions do not change which hosts are covered or how plans are compared.
The Short Answer
Pick the data center closest to the majority of your visitors, not closest to you. If most traffic comes from one country or region, that single choice cuts latency on every uncached request. If your audience is spread across continents, put a CDN in front of the site and pick the origin location by where your uncached traffic (checkout, logged-in pages, admin) comes from. Do not move hosts for SEO reasons alone; Google weighs your domain, hreflang, and on-page signals ahead of server IP.
Why Distance Shows Up in Load Time
Data travels through fiber at roughly two thirds of the speed of light, about 200,000 km per second. That works out to roughly 1 millisecond of round-trip time for every 100 km of cable, before routing detours, congestion, and equipment add more. Cable routes are rarely straight lines, so measured latency is usually higher than the physics floor.
Round trips multiply the distance
A browser does not make one trip to load a page. web.dev breaks TTFB into DNS lookup, connection and TLS negotiation, and the request itself. On a fresh HTTPS connection that is typically:
- 1 round trip for the TCP connection.
- 1 round trip for the TLS 1.3 handshake (older TLS versions need 2).
- 1 round trip for the HTML request and the first byte back.
Three round trips at 60 milliseconds each is about 180 milliseconds of pure travel before the server does any work. At 10 milliseconds each, for a visitor in the same region, it is about 30 milliseconds. The server's own processing time, covered in the guide to PHP workers, comes on top of either figure.
Approximate travel cost by distance
The table below uses the physics floor of roughly 1 millisecond per 100 km of round trip. Treat the figures as approximate minimums, not measured results; live networks add overhead.
| Visitor to server distance | Approx. round trip | 3 round trips (new HTTPS connection) | Verdict |
|---|---|---|---|
| Same metro, under 100 km | 1 to 5 ms | Under 15 ms | Distance is not your problem |
| Same region, about 1,000 km | 10 ms or more | 30 ms or more | Fine for nearly every site |
| Cross-continent, about 4,000 km | 40 ms or more | 120 ms or more | Noticeable on uncached pages |
| Intercontinental, about 6,000 km | 60 ms or more | 180 ms or more | Use a CDN or move the origin |
| Opposite side of the world, about 15,000 km | 150 ms or more | 450 ms or more | Origin location matters a lot |
What a CDN Changes
A CDN stores copies of cacheable files, such as images, CSS, JavaScript, and fully cached pages, on servers near the visitor. For those files the trip ends at the nearby edge, so the origin's location stops mattering. The connection and TLS handshake also terminate at the edge, which removes most of the distance penalty on the first two round trips.
What a CDN does not fix is the uncached request. A WooCommerce cart, a membership dashboard, a search results page, or the WordPress admin still has to reach the origin server, and every one of those requests pays the distance cost. That split is the same one covered in the guide to what an included CDN speeds up.
Choose the origin data center by where your uncached traffic comes from. Let the CDN handle everyone else.
How to Measure It on Your Own Site
You do not need to guess. Three free checks show how much distance is costing you:
- Browser developer tools: open the Network tab, reload a page that is not cached, and read the timing breakdown for the main document. The connection, TLS, and waiting phases map directly to the round trips above.
- A command-line timing check: curl's write-out option can print the time_connect, time_appconnect, and time_starttransfer values for a URL, which are connection time, TLS completion, and time to first byte in seconds.
- Multi-region testing: free speed-test tools that run from several cities show the same page's TTFB from near and far locations. A large gap between nearby and distant test points is the distance penalty.
Run each check on a cached page and an uncached one, such as the cart or a logged-in page. If the uncached page is slow only from far away, location is the cause. If it is slow everywhere, the problem is server processing, not distance.
Does Server Location Affect SEO?
Only a little, and only as a tiebreaker for audience. Google's multi-regional guidance lists the signals it uses to work out which country a page targets: country-code domains, hreflang annotations, server location through the server's IP address, and other signals such as local addresses, currency, and language. On server location specifically, Google notes that many sites use CDNs or host in another country with better infrastructure, so it treats location as not definitive.
In practice, that means:
- A US business hosted in the US: no SEO issue.
- A UK business on a .co.uk domain hosted in the US: the ccTLD already tells Google the target country; server IP adds little.
- A .com site targeting Germany: hreflang, German content, euro pricing, and a German address do more than a German server IP.
The indirect effect is speed. A slow TTFB can drag down Largest Contentful Paint, which is a Core Web Vitals metric. That is a page experience issue that happens to involve server location, not a geotargeting penalty.
How Hosts Handle Data Center Choice
Most hosts let you pick a data center at signup on at least some plans, and the number of locations varies widely. SiteGround's managed hosting page describes six global data centers, and Hostinger's web hosting page describes a global data center network (both pages checked October 19, 2026). Cloud platforms built on large providers usually offer more regions.
Three checks before you buy:
- Is the location selectable on your plan? Some hosts reserve the choice for higher tiers or assign a default.
- Can you move later, and what does it cost? A data center move is often a migration with downtime risk. The guide to DNS changes and downtime covers what happens during a move.
- Does the plan include a CDN? An included CDN reduces how much the origin choice matters for cached pages.
When Location Matters Most
- Stores and membership sites with a concentrated audience: most requests are uncached, so pick the region where buyers are.
- Sites with heavy admin or editorial work: editors working on the far side of the world feel every round trip in the dashboard.
- Data residency requirements: some businesses must keep customer data in a specific country. That is a legal question, not a speed question, so confirm it before choosing on performance.
Location matters least for a content blog or brochure site behind a CDN with most pages cached. There, the origin could sit almost anywhere without visitors noticing.
Which Data Center Should You Pick?
Look at your analytics for the country breakdown of visitors, and weight checkout and logged-in traffic more heavily than blog readers. Pick the data center in or nearest that region. If no single region holds most of your traffic, pick the region with the most uncached requests and add a CDN. Re-check once a year, because audiences shift. For a broader framework on choosing a host, see how to choose a web host.
Compare hosting plans, data center options, and renewal pricing in the small business hosting guide on HostingDive.
Frequently Asked Questions
- Does server location matter for website speed?
- Yes, for uncached requests. Each round trip costs roughly 1 millisecond per 100 km at the physics floor, and a new secure connection usually needs about 3 round trips before the first byte arrives. A CDN removes most of that cost for cached files.
- Does server location affect SEO?
- Slightly. Google lists server location as one signal of a site's intended audience but says it is not definitive, because many sites use CDNs or host abroad. Country-code domains, hreflang, and on-page signals carry more weight.
- Should I host my website in my own country?
- Host it near your visitors, not near you. If most customers are in your country, that is the same thing. If they are elsewhere, choose their region.
- Do I need a CDN if my server is close to my visitors?
- Not always. A CDN helps most when visitors are far from the server or spread across regions. For a local audience with a nearby server, it is optional, though it can still offload traffic.