Why Distance Still Slows Your Website Down

1 October 2026/, ,

Hosting · Part 2 of 4

A lot of the cheap hosting sold to Australian businesses is not in Australia. The page does not say so, and for a while you will not notice. Then you will notice, and you will blame the website.

This one is not about security. It is about a constraint that no amount of money spent on server hardware can remove, and that almost nobody explains at the point of sale.

Light is fast. It is not infinite.

In optical fibre light travels at roughly two thirds of its speed in a vacuum, so call it 200,000 kilometres per second. From there the sums are unarguable.

Brisbane to Sydney is about 730 kilometres. There and back is about 7 milliseconds in theory and under 20 in practice, once you allow for the fact that cables do not run in straight lines and every switch along the way takes a moment.

Brisbane to the west coast of the United States is about 11,600 kilometres. There and back is about 115 milliseconds in theory and around 150 in practice.

Nothing you buy changes those numbers. A faster processor does not make the Pacific Ocean narrower.

The first byte is not the first round trip

Here is the part that surprises people. Before your server sends a single byte of your homepage, the visitor has already made several trips across that distance: one to open the connection, another to negotiate the encryption, and then the request itself. Three crossings before anything useful arrives.

At 150 milliseconds each, that is roughly 450 milliseconds spent purely on distance, before your server has thought about anything at all.

Google treats a time to first byte of 0.8 seconds or less as good, and anything over 1.8 seconds as poor. If distance alone has eaten more than half your good budget, the rest of the work has to be flawless just to come out average.

Why it looks fine when you test it

This is where most owners get quietly misled, including technical ones.

A content delivery network keeps copies of your images, stylesheets and scripts at locations near the visitor, so those arrive fast regardless of where your server is. That is genuinely useful and it is why an overseas site can score well on a speed test.

What a cache cannot answer is anything that has to be worked out fresh.

  • The page a logged-in customer sees
  • The cart, and every change to it
  • Checkout
  • A contact form being submitted
  • Search, and booking availability
  • Anything priced, personalised or in stock

So your homepage tests beautifully and your checkout crawls. And you only ever test the homepage, because that is the URL you paste into the tool.

The part that costs you personally

Then there is the admin. Every time you edit a page, save a draft, load a preview or upload an image, you are making the round trip yourself. On a server in Sydney the interface feels immediate. On a server on the other side of the planet it feels like wading.

An owner who maintains their own site pays that distance in their own time, every week, for as long as they own the business. Nobody itemises it, so nobody counts it. It is usually the single biggest cost of a cheap plan and it never appears on an invoice.

When distance genuinely does not matter

An argument with no honest counter is just advertising, so here is the counter.

If your site is a brochure with no logins, no cart and no bookings, if the whole thing can sit in an edge cache, if you get a modest number of visitors and you never touch the admin yourself, then the distance is an academic point and the cheaper plan is a perfectly sound decision.

The catch is the same one as in part one. Sites do not stay brochures. Somebody adds a form, then a booking system, then a login, and nobody goes back and revisits the hosting decision, because nothing announced that the decision had changed.

How to find out where your site actually is

  • Ask your host which city the server is in. Not the region, not the country. The city. If the answer is a marketing phrase, ask again.
  • Ask the same question about your backups, separately. The answers are often different countries.
  • Run your contact page, not your homepage, through Google PageSpeed Insights, and read the server response time rather than the score.
  • Then log into your own admin and notice how long a page save takes. You already know the answer, you have just been putting up with it.

If the answers point offshore and your site does real work, distance is costing you money in ways nobody has ever billed you for. Part four of this series does the arithmetic on what the cheap plan is actually paying for. Our own managed hosting sits in Sydney for exactly the reasons above.

Common questions

Does a CDN not solve this?
It solves half of it. A cache serves your static files from somewhere close to the visitor. It cannot serve a cart, a login, a checkout or a form submission, because those have to be worked out on the origin server. Those are usually the pages where money changes hands.
Does Google penalise slow hosting?
There is no penalty in the sense of a punishment. Speed is one of the signals Google measures, and you can see your own numbers in PageSpeed Insights and Search Console rather than taking anyone’s word for it. The more immediate cost is people leaving before the page arrives.
Is Sydney better than Melbourne for a Brisbane business?
The difference is a handful of milliseconds and it does not matter. The decision that matters is Australia against offshore, not which Australian city.
My host says their servers are fast. Is that not enough?
A fast server on the wrong continent still waits for the light. Hardware fixes processing time. It does nothing about the distance, which on an overseas plan is usually the larger number.
What about email, is that affected too?
Sending and receiving are not noticeably slower, but if your website and your mail sit on the same budget shared account, they share the same fate when something goes wrong. That is the subject of part one.

Next step

If you want to know what distance is costing you, send us your URL and we will measure it properly and tell you whether it is worth moving. If it is not, we will say so.