A slow website makes simple tasks harder. A customer waits for a product photo, taps a menu that has not responded, or loses their place when a banner moves the page. Even when they stay, those delays interrupt the enquiry or buying process.
Speed also matters to organic search. Google uses Core Web Vitals in its ranking systems, but a fast page still needs relevant, useful content. Passing a performance test does not guarantee a particular position. Google’s Core Web Vitals guidance makes that distinction clear.
The useful question is not “How do we get a perfect score?” It is “What is slowing down our customers, and which improvements will make the biggest difference?”
What Core Web Vitals measure
Core Web Vitals describe three parts of the experience: seeing the main content, getting a response to an interaction, and keeping the layout steady.
| Measure | What it tells you | Good threshold | A business website example |
|---|---|---|---|
| Largest Contentful Paint (LCP) | How quickly the largest visible content element appears. | 2.5 seconds or less | The main service image or large opening text takes too long to appear. |
| Interaction to Next Paint (INP) | How promptly the page responds visually to interactions. | 200 milliseconds or less | Tapping a menu or choosing a product option feels unresponsive. |
| Cumulative Layout Shift (CLS) | How much visible content unexpectedly moves. | 0.1 or less | A late-loading image pushes the enquiry button away as someone taps. |
These thresholds are assessed at the 75th percentile of visits, with mobile and desktop considered separately. That means looking beyond one fast test on an office connection. See the Core Web Vitals overview for the measurement definitions.
Use field data and laboratory tests together
PageSpeed Insights combines real-user field data, where available, with a simulated Lighthouse test. They answer different questions.
Field data: what visitors experienced
Field data reflects a range of devices, connections and visits. It is useful for deciding whether a problem affects real customers and for checking longer-term improvement. A low-traffic page may have insufficient page-level data; the report may show origin-level information instead. Check which level you are reading before drawing conclusions about one URL.
Laboratory data: what to investigate
A controlled test helps identify heavy images, blocking resources and slow server responses. It is a diagnosis aid, not a promise that every visitor has the same experience. Run comparable tests more than once and record the conditions. A single score can move without the website changing.
Test the homepage, a main service page, an article and, for a store, a product and category page. Different templates often have different problems. A quick homepage does not prove that checkout works well on a phone.
Four common sources of delay
1. Images that are larger than the job requires
A full-resolution photograph should not be sent unchanged to every screen. Resize and compress images, use an appropriate modern format, and provide responsive sizes so a phone can download a smaller version. Keep enough quality for customers to judge the work or product.
Give images dimensions so the browser can reserve space. Load off-screen images later where appropriate, but avoid delaying the main image customers need to see immediately. Check the result visually: aggressive compression, awkward crops and missing product detail are poor trade-offs.
2. Scripts competing for the browser’s attention
Chat tools, sliders, maps, review widgets and tracking scripts all add work. Inventory what loads on each template and ask whether it needs to load there, at that point in the journey. An interactive map in the footer rarely needs the same priority as the opening content.
Remove unused tools and test delayed loading carefully. Do not break enquiry forms, payment steps or conversion measurement while chasing a higher score. Long-running browser tasks are particularly relevant when a page looks ready but its controls respond slowly.
3. Caching that is missing or incorrectly configured
Caching can avoid rebuilding or downloading the same resources repeatedly. The right setup depends on the site and hosting. Public brochure pages are different from a customer’s cart or account area.
Confirm that private and transactional pages remain correct, and that changes can be purged reliably. A fast cached page displaying yesterday’s price or somebody else’s information is not a successful optimisation.
4. Hosting and server work
A slow initial response can point to resource limits, database work, an expensive plugin or an external service. Measure before moving hosts. A hosting upgrade may help a genuinely constrained server, but it will not remove a huge image or an unnecessary third-party script.
A practical diagnosis: a slow trade-business website
Consider an illustrative local electrician’s site. The owner says the homepage is slow on mobile. The enquiry form itself works, but the opening photo appears late and the menu sometimes hesitates.
- Reproduce the journey. Open the homepage on a phone, navigate to a service, and start an enquiry. Note what feels slow rather than relying only on a score.
- Check the evidence. Review mobile field data where available, then inspect a laboratory test and its loading sequence. Establish whether the main delay is the server response, the image download or work in the browser.
- Make a focused first change. If the opening image is oversized, prepare suitable responsive versions and make sure it is discovered promptly. Retest before adding another change.
- Investigate interaction separately. If the menu still hesitates, inspect scripts and long tasks. Image compression alone may not address that problem.
- Verify the business tasks. Check the menu, phone link, form, images and tracking after the change. Then monitor real-user measurements as fresh visits accumulate.
This is a diagnosis method, not a reported A1 client result. The actual fix depends on what the evidence shows.
Prioritise improvements and keep them working
Start with important pages and problems that affect many visitors. A broken interaction or a very late main image usually deserves attention before a small saving on an obscure page. Record a baseline, change one coherent group of issues, and compare the same URLs and tasks afterwards.
Add a short performance check whenever you install a plugin, replace a hero image or add a marketing tool. Keep backups and a way to reverse changes. Our website maintenance service can help make those checks part of normal site care.
If organic enquiries are the wider concern, combine performance work with relevant content, clear page structure and a usable enquiry journey. A1’s SEO services can help identify where speed fits among the changes your website needs.