Blog

Core Web Vitals are not the whole story. Google's metrics reward fast paint times and stable layout, but visitors reward something simpler: can I read the headline, find a phone number, and tap a button without waiting.

The usual suspects on Australian SMB sites are predictable. Hero images sized for a 4K monitor delivered to a mobile on 4G. Third-party widgets for chat, reviews, and analytics all firing before the page is usable. Autoplay video that pushes everything else down the loading queue. Deferring non-critical scripts, resizing media to actual display dimensions, and lazy-loading anything below the fold is still the highest-ROI fix for most sites we scan.

Speed also feeds into AI visibility in a way most owners underestimate. Generative engines prefer to cite sources that load reliably and render cleanly: slow, layout-shifting pages signal a maintenance problem, and AI assistants quietly favour the competitor whose page they can parse without trouble. Fixing speed is rarely just a UX win.

If you only ship one change after a diagnostic, make it the path from landing on the homepage to making contact. Fewer steps, lighter assets, one obvious next action. A tradie's site where the phone number is visible and tappable within two seconds of landing will out-convert a slick competitor whose page is still loading a carousel. When the same fixes do not move the score after two or three sprints, the bottleneck is usually deeper in the build, and a specialist review will surface what your developer cannot see from inside the code.