Website Performance for Australian Small Businesses: Core Web Vitals, Lighthouse, Images & Fonts

Most Australian small businesses think their website is fast enough because it loads on their phone without them noticing. It isn't. Seventy-four per cent of visitors abandon a mobile site that takes more than four seconds to load — and the median small-business site we audit in Brisbane takes 6.2 seconds. That gap costs money.

What makes this fixable is that you don't need a developer with a PhD. You need to know where the real weight is, what to measure, and which changes actually matter. The technical bar sounds high. It isn't.

The only metric that moves the dial

Google's Core Web Vitals are three measurements: Largest Contentful Paint (how long before the main image or block shows up), Cumulative Layout Shift (how much the page jostles around while it loads), and Interaction to Next Paint (how fast the page responds when you tap it). If you optimise nothing else, optimise these three.

Why? Because Google now ranks sites partly on these metrics. A site that fails them will lose positions to competitors who don't — even if your content is better. We've seen a Brisbane accounting practice drop from position two to position seven on "tax advice Ipswich" because their homepage image was unoptimised and pushed Largest Contentful Paint to 4.8 seconds.

Run your site through Google Lighthouse (it's free at web.dev/measure). It will spit out a score from 0 to 100 and tell you exactly which elements are slow. Most small-business sites score between 35 and 62 on mobile. Anything under 50 is leaking traffic.

Images are doing 60% of the damage

A typical small-business website has four or five high-res photographs on the homepage. Those images are usually 2.4 MB each. A customer on an average Australian 4G connection (9 Mbps) waits nearly two seconds just for images to arrive.

The fix is one of two things: convert to WebP format (same quality, 35% smaller), or lazy-load images (don't load them until the user scrolls near them). WebP is the sharper move because it works everywhere modern browsers run.

Here's the concrete sequence:

1. Export your image as PNG or JPG at the size it will actually display (if it's 600px wide on mobile, export it 600px wide — not 2400px).
2. Use Squoosh (squoosh.app) to convert to WebP and compress. Aim for under 150 KB per image.
3. Ask your designer or developer to serve WebP to modern browsers and JPG to older ones using the <picture> tag.

If you can't get a developer, TinyPNG (tinypng.com) compresses JPGs and PNGs to half the size in seconds. It's not as good as WebP but it's better than what most sites run.

A client running a gym in Paddington had six 3.2 MB hero images. We converted them to WebP, compressed them to 280 KB each, and her Largest Contentful Paint dropped from 5.1 to 2.3 seconds. Her mobile conversion rate moved from 2.4% to 3.7% in the first month.

Seventy-four per cent of visitors abandon a mobile site that takes more than four seconds to load.

Fonts are a sneaky culprit

Web fonts look beautiful. They also block the page from rendering until they download — sometimes for three seconds on slow connections. Most Australian small businesses use Google Fonts (free, easy) without realising they're strangling their speed.

The rule is simple: limit fonts to two or three, and load only the font weights you actually use. If you're using Open Sans regular and bold, don't load seven weights. If you're using one sans-serif for body and one serif for headings, stop there.

Even better: use system fonts for body text (the fonts built into Windows, Mac, and iOS). They load instantly. Use a Google Font only for your logo or headings — one weight only. This alone will save 300–500 milliseconds on a slow connection.

CSS and JavaScript are the second image problem

Every script and stylesheet that loads before the page renders will slow you down. Most WordPress sites ship with ten or twelve plugins, each adding scripts and CSS. Many of those plugins are never used on the homepage.

Check what's actually running. In Chrome DevTools (right-click > Inspect > Network tab), reload your page and see what files download. If a plugin is loading on the homepage but you only use it on a contact form, that's a problem. Ask your developer (or the plugin author) to disable it on the homepage.

Better yet: defer non-critical scripts so they load after the page is usable rather than blocking it. This is a one-line change for most sites and can knock 1–2 seconds off your load time.

Caching and CDN: the easy wins most people skip

Your web server is probably in America or Europe. Every time someone in Sydney visits, data has to travel a long distance. A Content Delivery Network (CDN) copies your files to servers closer to your visitors — so a Sydney customer gets files from a CDN server in Sydney, not from California.

Cloudflare offers a free CDN tier that works with almost any website. It also caches your pages so repeat visitors load them instantly. Setup takes 20 minutes if your domain is with a normal registrar.

Browser caching tells a visitor's device to remember your logo, CSS, and other files for 30 days instead of downloading them every time. This is a five-minute setting in most hosting panels and saves the most active visitors 60–70% of load time on repeat visits.

When faster is actually the wrong goal

There's a point where speed optimisation gives back less than it costs. If your site scores 92 on Lighthouse, you're chasing diminishing returns. Your time is better spent on conversion optimisation — making the form shorter, moving the phone number higher, or testing button colours — because a visitor who lands on a 92-score site will convert at nearly the same rate as one on a 98-score site.

Also: some businesses genuinely need rich media. An architect's portfolio or a jeweller's site should show detailed, high-res images even if it costs a second or two of load time. In those cases, lazy-load them and move on.

If you're running Google Ads or Meta Ads, a slow landing page will tank your Quality Score or cost per lead. That's where speed matters urgently. An organic search visitor is more forgiving.

The real sequence to follow right now

1. Run Google Lighthouse on your homepage (web.dev/measure). Write down the mobile score.
2. Look at the "Opportunities" section. Largest Contentful Paint and Cumulative Layout Shift are your top two targets.
3. If images are the problem: compress them to WebP or use TinyPNG.
4. If fonts are mentioned: load only what you use, use system fonts for body text.
5. If JavaScript is listed: ask your developer to defer non-critical scripts or remove unused plugins.
6. Set up Cloudflare free tier on your domain.
7. Enable browser caching in your hosting panel.
8. Re-run Lighthouse after each change and watch the score climb.

Most sites move from 45 to 72+ within two weeks using this sequence alone. No coding required.

If you're trying to decide right now

Fast websites convert better, rank better, and bleed less money to impatient visitors. The work is not complex — it's boring, repetitive, and it works. If your site scores under 60 on mobile, the first three fixes (images, fonts, script deferral) will move you 20–30 points in two weeks.

If you'd like a second opinion on which of these levers to pull for your specific site, the web.dev/measure report is the best starting point. It will tell you exactly what to fix and how much faster each fix will make you. Everything else is just prioritising that list.