Someone is standing on a footpath in Marrickville with a coffee in one hand and a phone in the other. They have heard about your business, they type your name into Google, and they tap the first result. The screen stays white. A logo appears, then jumps sideways as a banner loads above it. Four seconds in, they go back and tap your competitor instead.

Nothing was broken. Your website works perfectly on the desktop in your office, with everything already loaded once before. On a phone, on mobile data, it behaves like a different website. That gap is where many Australian small businesses quietly lose enquiries.

What “slow” actually means to Google

Google measures page experience with three numbers called Core Web Vitals. Each one describes a normal human frustration.

• Largest Contentful Paint (LCP) — how long until the biggest thing on the screen, usually your main image or headline, appears. Good is under 2.5 seconds. The “am I looking at a blank page?” measure.
• Interaction to Next Paint (INP) — how long the page takes to respond after someone taps something. Good is under 200 milliseconds. The “I tapped the menu and nothing happened” measure. It replaced First Input Delay in March 2024.
• Cumulative Layout Shift (CLS) — how much the page jumps around while loading. Good is under 0.1. The “I went to tap Book Now and a banner slid into the spot” measure.

Google judges these on field data — real visitors on real phones, collected in the Chrome User Experience Report — not a test in perfect conditions. To pass, at least 75% of visits to a page must be good. A site that is fine on your office wi-fi can still be failing most customers on a train.

Check any page yourself, free, with Google PageSpeed Insights. Use the mobile tab, and test more than the homepage.

Cause one: images that are far too big

The most common culprit, and the easiest to fix. A photo straight off a phone can be several thousand pixels wide. On a phone screen it might display at 400. The visitor still downloads the whole file, then their phone shrinks it. You have made them pay for detail they will never see.

Three habits solve almost all of it:

• Resize before uploading. If an image never displays wider than 1200 pixels, do not upload one that is 5000 pixels wide.
• Use modern formats. WebP and AVIF are image formats that look the same as a JPEG at a fraction of the file size. Most tools now export them.
• Load offscreen images later. Called lazy loading — images further down the page only download when the visitor scrolls towards them.
• Skip video backgrounds. A looping hero video is one of the fastest ways to punish a customer on mobile data.

Cause two: plugins and scripts you forgot about

Every plugin, chat widget, booking embed, review carousel and tracking pixel adds code the visitor must download and run before the page settles. Each seemed reasonable at the time. Twenty together are not. The usual suspects: a lapsed booking tool, two analytics tags added by two different marketers, a social feed nobody looks at, a pop-up plugin, and a homepage slider — often the heaviest thing on the site.

Tracking scripts are worse than they look, because they load from someone else’s server. The phone makes a fresh connection there, waits, then runs whatever comes back. Ten of those and your page is stuck waiting on other people’s infrastructure.

Go through your plugin list and ask of each: what would break if this were gone? If the answer is “nothing I can name”, remove it.

Speed is rarely a mysterious technical problem. It is usually a slow accumulation of small decisions nobody ever reversed.

Cause three: where your website physically lives

This one surprises people. It is not really about your website; it is geography.

Data travels fast, but not instantly. A request from a phone in Sydney to a server in Virginia or Frankfurt goes a very long way, and every request makes the round trip. Loading a page is dozens of requests — styles, fonts, each image, each script. Add delay to each and it compounds into something a customer can feel.

What helps:

• Host closer to your customers. For Australian customers, a server in a Sydney data centre removes that distance from every request. It is why we run hosting in Australia, and why a busier site often moves to dedicated cloud resources rather than a crowded shared plan.
• Use a CDN. A content delivery network keeps copies of your files on servers around the world, including locally, so heavy items come from nearby.

Cheap shared hosting also means sharing a machine with hundreds of other sites. When one has a busy day, yours slows down and you never learn why.

What to do next

The first three cost nothing but an afternoon.

1. Measure honestly. Run your homepage, contact page and best-selling product page through PageSpeed Insights on mobile. Note the LCP, INP and CLS figures as your starting point.
2. Fix the images. Find the biggest files on your slowest page, resize them to the size they actually display at, and re-export as WebP.
3. Cull the extras. Remove every plugin, widget and tag you cannot justify out loud, then test again.
4. Ask where your site is hosted. A server overseas serving only Australian customers is a fixable handicap.
5. Check the foundations. If it is still slow, the theme or build is the problem and tuning will not save it. A leaner rebuild often costs less than years of patching.

Speed is not a vanity metric. It is the difference between a customer waiting and a customer leaving. If you would like someone to look at your numbers and say plainly what is causing them, get in touch.