Most Australian small businesses spend their marketing effort on getting people to the website — an ad, a Google ranking, a social post, a referral. Almost none of that effort goes into what happens in the three seconds after someone actually lands on it. If the site is slow, a chunk of that hard-won traffic leaves before it ever reads a word, and the channel that sent them gets blamed for a problem the website caused. Speed is one of the least glamorous parts of a website, and one of the most expensive to ignore.
Why speed is a ranking factor, not just a nice-to-have
Google has built page experience — how quickly a page loads and how stable it feels while loading — into how it evaluates sites, alongside content and links. It isn't the only signal, and a fast, thin page won't outrank a slower, genuinely useful one. But between two pages of similar quality, the faster, more stable one has an edge. In Australia, where a large share of local search happens on a phone, often on a mobile connection rather than office wifi, that gap shows up more, not less. A site that loads sluggishly on desktop can be markedly worse on a tradie's phone standing on a job site with patchy reception.
This matters more now, not less, because of where search itself is heading. AI-generated answers and overviews increasingly summarise and cite pages directly on the results page, and a page has to be crawlable and quick to load to be a candidate for that in the first place. We go into that shift in more detail in how to get your business cited in AI Overviews — speed is one of the quieter prerequisites underneath it.
What a slow site actually costs you
The cost shows up in three places, and all three are invisible unless you go looking for them.
- Lost visitors before they see anything. People are impatient on mobile, and a page that takes several seconds to become usable loses a meaningful share of visitors before the headline even renders. They don't complain — they just go to the next result.
- Wasted spend on everything upstream. If you're running paid ads, doing outbound, or investing in SEO or social content, every one of those channels is paying to send someone to a page that then quietly drops them. A slow site taxes every acquisition channel equally, which is why fixing it tends to lift results across the board rather than in just one place.
- A ceiling on your organic growth. Good content and backlinks can be undone, in part, by a technical foundation that makes Google reluctant to reward the page as strongly as it otherwise would.
The usual causes on small business sites
Almost none of this comes down to bad luck. In our experience it's nearly always one of a small, repeatable set of causes:
- Heavy website builders and page-builder plugins. Drag-and-drop platforms and plugin-stacked WordPress sites are quick to launch but ship a lot of code the visitor never benefits from, on every single page.
- Unoptimised images. A photo straight off a phone or a stock library, dropped into the page at full resolution, is often the single biggest thing slowing a page down — and the easiest to fix.
- Third-party scripts piling up. Chat widgets, booking widgets, review badges, marketing pixels and analytics tags each add their own request and their own delay. Individually small, collectively significant.
- Cheap or mismatched hosting. A shared hosting plan built for a low-traffic brochure site struggles once a site gets real visitors, particularly around a campaign or a seasonal spike.
What actually moves the needle
The fixes aren't exotic, and you don't need to touch everything at once. In rough order of effort versus payoff: compress and correctly size every image before it goes on the page; remove any third-party script that isn't earning its keep, and load the rest only when needed rather than on every page; keep the code the page ships down to what that page actually uses, rather than one heavy template loaded everywhere; and host on infrastructure built for the traffic you actually get, not the cheapest available plan.
This is also the argument for building lean in the first place rather than patching later. A performance-first build — one that ships only the code and assets a page needs, without a general-purpose builder underneath it — sidesteps most of this by design, which is the approach behind our own web development work.
Speed alone won't save an unclear website
It's worth being honest about the limit here too. A fast page with a confusing offer, no clear reason to act, or a call to action nobody can find will still convert poorly — it will just lose people quickly instead of slowly. Speed removes friction; it doesn't supply a reason to buy. The businesses that get the most out of fixing site speed are usually ones where the message and offer are already reasonably clear, and the technical drag was the thing actually holding results back. If you're not sure which of those two problems you have, that's a reasonable thing to check before spending on either.
Patch it, or rebuild it?
Not every slow site needs a rebuild. If the platform underneath is fundamentally capable and the problems are images, scripts and hosting, a focused clean-up can produce a real, measurable improvement without touching the design. A rebuild earns its cost when the platform itself is the ceiling — a heavy builder that can't be trimmed further, a site that's already due for a redesign, or one that's grown into a tangle of plugins nobody wants to keep maintaining. In that case, fixing speed and improving the site tend to be the same project rather than two separate ones.
Where this fits with the rest of your marketing
None of this replaces the rest of the work — getting found, getting cited, and getting replied to still matters, and that's the territory our SEO agent and outreach agents work in. But a slow site is a tax on all of it at once, which makes it one of the higher-leverage things to fix rather than one more channel to add. If you're not sure whether speed, message or traffic is the actual constraint on your site right now, that's exactly what our free AI readiness audit on the pricing page is for — a straight look at where the leak actually is before you spend on the wrong fix.