Websites & Visibility

The Eight-Second Website: How Slow Load Times Quietly Cost You the Job

A slow site doesn't announce itself — it just quietly loses jobs to whoever loaded first.


Most lost jobs don’t look like a rejection. They look like nothing at all — a phone that doesn’t ring, an enquiry that never arrives, a customer who found someone else and never told you why. One of the most common, least visible reasons: your website took eight seconds to load on their phone, and theirs took two.

This matters more in Tasmania than the national averages suggest. A lot of searches — someone standing in a driveway, in a paddock, in a spot with patchy 4G — happen on a mobile connection that isn’t fast to begin with. A website that’s slow even on good reception becomes borderline unusable on a bad one. And a customer standing there with a problem to solve doesn’t wait around to find out if your site is just being slow today.

Why it happens

It’s almost never one big thing. It’s usually a stack of small ones: a page-builder plugin doing more work than the page needs, image files uploaded straight from a phone camera at ten times the size they need to be, a theme built to handle every possible layout instead of the one the site actually uses. None of it is visible to the business owner — the site looks finished in the browser at the office, on the office wifi, and that’s the only place it usually gets checked.

What it actually costs

Google notices load speed too — it’s part of what Core Web Vitals measures, and it factors into how a page ranks locally. So a slow site doesn’t just lose the customer who already found you; over time, it can mean fewer customers find you in the first place. It’s a cost that compounds quietly in both directions.

What actually fixes it

Not a “we’ll optimise your images” add-on tacked onto an existing slow build — the fix that holds up is building the site without the bloat in the first place. Hand-built templates instead of a stacked page-builder plugin. Compressed imagery from day one. A structure that only carries the weight the page actually needs. That’s the difference between a site that’s fast because someone tuned it once, and a site that’s fast because it was never built to be slow.

If you’re not sure where your own site lands, load it on your phone with wifi off and time it — genuinely, with a stopwatch. If it’s not comfortably under three seconds, that’s very likely costing you jobs you never see. Have a look at how CrunchPixels builds sites for speed from the ground up, or see the Launceston-specific hub if you’re based in the north.

Nobody tells you your site was slow. They just ring the next one.