Quick answer: Google measures how fast your site feels to real visitors using three Core Web Vitals. Your pages should show the main content within 2.5 seconds (Largest Contentful Paint), respond to taps and clicks within 200 milliseconds (Interaction to Next Paint) and not jump around while loading (Cumulative Layout Shift below 0.1). Google judges each one on the 75th percentile of real visits, so most visitors need a good experience, not just you on office Wi-Fi.
Speed is not a technical vanity metric. A slow site loses visitors before they see your offer, it wastes ad spend because you pay for clicks that never load, and it is one of the signals Google uses in its page experience assessment.
The three numbers that matter
| Metric | What it measures | Good | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | How long until the main content, usually the hero image or headline, appears | 2.5 seconds or less | Over 4 seconds |
| INP (Interaction to Next Paint) | How quickly the page reacts when someone taps a button or opens a menu | 200 ms or less | Over 500 ms |
| CLS (Cumulative Layout Shift) | How much the layout jumps as things load | 0.1 or less | Over 0.25 |
INP replaced the older First Input Delay metric in March 2024, so older articles you find may mention FID. It measures responsiveness across the whole visit, not just the first tap, which is why heavy pop-ups, chat widgets and tracking scripts now matter more.
How to test your site in two minutes
- Go to Google’s free PageSpeed Insights and enter your homepage address.
- Look first at the top section, which shows real-user data from Chrome if your site has enough traffic. This is what Google actually uses.
- Check the Mobile tab, not just Desktop. Mobile is where most sites fail.
- Repeat for your most important service page and your contact or quote page.
If you have Google Search Console set up, the Core Web Vitals report shows which groups of pages pass or fail across your whole site.
The usual causes of a slow small business site
- Huge images. A 5 MB photo straight from a phone or camera on the homepage. Images should be resized, compressed and served in modern formats like WebP or AVIF.
- Heavy page builders and themes. Some all-in-one themes load large amounts of code on every page whether it is needed or not.
- Too many plugins. Each one can add scripts and database work. Many sites carry plugins nobody uses any more.
- Third-party scripts. Chat widgets, review widgets, heatmaps, multiple tracking pixels and embedded social feeds all compete for the phone’s processor.
- Cheap hosting. Overloaded shared servers respond slowly before the page even starts loading.
- No caching. Pages are rebuilt from scratch for every visitor instead of being served ready-made.
- Fonts and sliders. Several font families and auto-playing image sliders slow down the first view and often cause layout shift.
Quick wins
- Compress and resize images, and lazy-load anything below the first screen.
- Remove unused plugins and replace heavy sliders with a single strong image.
- Delay chat and non-essential scripts until after the page has loaded.
- Set width and height on images and embeds to stop layout jumps.
- Turn on page caching and use a content delivery network.
- Move to quality hosting with servers in or near Australia if your customers are here.
Speed is designed in, not bolted on
The cheapest time to make a site fast is before it is built. Choosing a lightweight theme, planning images and limiting scripts from day one avoids the expensive cleanup later. Every site we build is tested against Core Web Vitals on mobile before launch, and speed is checked monthly on our Growth Care plan.
Planning a new website?
Next step: fill in the website brief. It takes about 10 minutes, and you get a fixed quote within one business day, then 2 or 3 design concepts to compare before anything is built. See website packages and care plans.

