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

The single fastest win for most Australian small-business sites is image weight: compress your homepage photos to WebP and you can roughly halve load time without touching the design, the copy, or the build. Everything else on this page matters, but if you do one thing today, do that. The rest of this guide is the full sequence — Core Web Vitals, Lighthouse, fonts, scripts and caching — in the order that actually moves the number.

You don't need a developer with a PhD to do most of it. You need to know where the weight is, what to measure, and which changes matter. The technical bar sounds high. It isn't.

Why speed is a money problem, not a vanity one

The biggest companies on earth have measured this to the millisecond. Greg Linden, an ex-Amazon engineer, found that every 100ms of extra latency cost Amazon roughly 1% in sales. Google's Marissa Mayer reported that a half-second delay caused a 20% drop in traffic. Walmart found that every one second of load-time improvement lifted conversions by up to 2%. The BBC lost 10% of its users for every extra second a page took to load.

Your business isn't Amazon, but the curve is the same shape: slower equals fewer customers. The only difference is you won't see it in a dashboard — you'll see it as enquiries that never came.

The three metrics that actually rank you

Google's Core Web Vitals became an official ranking factor in June 2021. They 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.

A site that fails them loses positions to competitors who pass — even when your content is better. Picture a Brisbane accounting practice slipping a few spots on "tax advice Ipswich" because one unoptimised homepage image pushed Largest Contentful Paint past four seconds. That is how quietly a single heavy file can cost you rankings, and you'd never know why.

Run your site through Google Lighthouse (free at web.dev/measure). It gives you a score from 0 to 100 and tells you exactly which elements are slow. Don't obsess over the exact number — treat anything in the red as money on the table and use the "Opportunities" list as your to-do.

Images are almost always the biggest single offender

A typical small-business homepage has four or five high-res photographs, each one straight off a phone or a stock site at two or three megabytes. On a phone on regional 4G, your visitor sits there watching nothing happen while those files crawl down the wire. By the time the page is usable, a chunk of them have already hit the back button.

The fix is one of two things: convert to WebP format (visually identical, dramatically smaller), or lazy-load images so they don't download until the user scrolls near them. WebP is the sharper move because every modern browser supports it. Here's the concrete sequence:

1. Export your image at the size it will actually display. If it shows at 600px wide on mobile, export it 600px wide — not 2400px. Nobody ever needs a 4000px hero on a phone.
2. Run it through Squoosh (squoosh.app) to convert to WebP and compress. Aim for under 150 KB per image — you'll be surprised how good it still looks.
3. Serve WebP to modern browsers and a JPG fallback to old ones using the <picture> tag. (Every image on this very page does exactly that.)

No developer handy? TinyPNG (tinypng.com) compresses JPGs and PNGs to roughly half their size in seconds. It's not as good as WebP, but it's far better than the raw files most sites ship.

Picture a gym in Paddington running six untouched hero images. Convert them to WebP, drop each to a couple of hundred kilobytes, and Largest Contentful Paint can fall from "painfully slow" to "snappy" in an afternoon — no redesign, no new content, just lighter files.

Amazon found every 100ms of delay cost about 1% of sales. Your homepage images are where most of that delay lives.

Fonts are a sneaky second culprit

Web fonts look beautiful. They also block the page from rendering until they download. Most Australian small businesses load a pile of Google Fonts (free, easy) without realising they're strangling their own speed — and worse, a slow font swap is a classic cause of layout shift, the "jostling" metric Google penalises.

The rule is simple: limit fonts to two or three, and load only the weights you actually use. If your design uses regular and bold, don't download seven weights. One sans-serif for body, one serif for headings, and you're done.

Better still: use system fonts (the ones already built into Windows, Mac, and iOS) for body text. They load instantly because they're already on the device. Reserve a Google Font for your logo or headings only — one weight. That single change trims real time off a slow connection and removes a layout-shift risk for free.

CSS and JavaScript: the weight you can't see

Every script and stylesheet that loads before the page renders slows you down. A lot of WordPress sites ship with a dozen plugins, each adding its own scripts and CSS — and most of them load on every page even though they're only used in one place. A booking widget you use on a single contact form has no business loading on your homepage.

Check what's actually running. In Chrome DevTools (right-click > Inspect > Network tab), reload your page and watch the files download. If a plugin loads on the homepage but is only used elsewhere, that's dead weight. Ask your developer (or the plugin's own settings) to disable it where it isn't needed.

Then defer non-critical scripts so they load after the page is usable instead of blocking it. For most sites that's a small change with an outsized payoff — the page becomes interactive sooner, which is exactly what Interaction to Next Paint measures.

Caching and CDN: the easy wins most people skip

Your web server is probably sitting in America or Europe. Every time someone in Sydney visits, the data has to travel that whole way and back. A Content Delivery Network (CDN) copies your files to servers closer to your visitors — so a Sydney customer gets your files from a nearby edge server, not from California.

Cloudflare offers a free CDN tier that works with almost any website, and it caches your pages so repeat visitors load them near-instantly. Setup takes about 20 minutes if your domain is with a normal registrar. (It's the same network this site runs on.)

Browser caching tells a visitor's device to remember your logo, CSS and other files for weeks instead of re-downloading them every visit. That's a five-minute setting in most hosting panels and it makes your most loyal, repeat visitors — your actual customers — the ones who get the fastest experience.

When faster is the wrong goal

Here's the honest bit most speed guides won't tell you: there's a point of diminishing returns. Once your site is comfortably in Lighthouse's green, squeezing out the last few points rarely changes how anyone behaves. Your time is then better spent on conversion — shortening the enquiry form, lifting the phone number higher, making the call-to-action obvious — because a fast site that nobody acts on still earns you nothing.

And some businesses genuinely need rich media. An architect's portfolio or a jeweller's gallery should show detailed, high-res work even if it costs a second of load. In those cases you lazy-load below the fold and accept the trade — but you do it deliberately, not by accident.

One place speed is never negotiable: paid traffic. If you're running Google Ads or Meta Ads, a slow landing page drags down your Quality Score and inflates your cost per lead — you're literally paying more for every click to land somewhere worse. An organic visitor is more forgiving; a paid one you've bought is not.

The sequence to follow right now

1. Run Google Lighthouse on your homepage (web.dev/measure). Write down the mobile score so you have a before-and-after.
2. Read the "Opportunities" section. Largest Contentful Paint and Cumulative Layout Shift are almost always your top two targets.
3. Images first: compress to WebP with Squoosh, or TinyPNG if you're in a hurry.
4. Fonts next: load only the weights you use; switch body text to system fonts.
5. Scripts: defer non-critical JavaScript and disable plugins that load where they aren't used.
6. Put Cloudflare's free tier in front of your domain.
7. Turn on browser caching in your hosting panel.
8. Re-run Lighthouse after each change and watch the number climb.

Most sites make a serious jump within a couple of weeks on this sequence alone, and the first three steps — images, fonts, script deferral — do the bulk of the work. No coding required for any of it.

If you're trying to decide right now

Fast websites convert better, rank better, and bleed less money to impatient visitors — the data from Amazon, Google, Walmart and the BBC all points the same way. The work itself isn't clever; it's boring, repetitive, and it works. If your site is in the red on mobile, the first three fixes will move you a long way in two weeks.

If you'd like a straight answer on which levers matter most for your specific site, the web.dev/measure report is the best free starting point — and if you'd rather hand it off, that's exactly the kind of work we do. We'll tell you what we'd fix and what it costs up front; our pricing is published, and you own everything we build.