Your site does not need a redesign. It needs to load
Google publishes exactly what it measures and exactly where the line is. The part almost everyone misses is that it is measured on your real visitors, at the 75th percentile — not on your laptop.
The three metrics and the actual thresholds
Core Web Vitals are three measurements of real user experience, and Google publishes the thresholds:
- LCP — Largest Contentful Paint. How long until the main content appears. Good is 2.5 seconds or less.
- INP — Interaction to Next Paint. How quickly the page responds when someone taps. Good is 200 milliseconds or less. INP replaced First Input Delay.
- CLS — Cumulative Layout Shift. How much the layout jumps while loading. Good is 0.1 or less.
The detail that changes everything: the 75th percentile
Google evaluates these at the 75th percentile of real visitor data. Three out of four visits must be in the "good" band for the page to pass.
Two consequences that people miss.
Your laptop test is meaningless. You are on fibre with a fast machine. The 75th percentile of your traffic is a mid-range phone on a mediocre mobile connection, possibly in a basement with one bar. That is the visitor being measured.
The average is the wrong statistic. A page can have a lovely average and fail, because the failure lives in the slow quarter. Optimising for the average optimises for the visitors who were already fine.
Where contractor sites actually lose the time
In roughly the order we find them:
- Hero images shipped at full camera resolution. A 4MB photo scaled down in the browser still downloads 4MB. Resize before upload and use a modern format.
- Images without width and height attributes. The single most common cause of layout shift — the page reflows when each image arrives.
- Third-party scripts. Chat widget, three analytics tools, a review carousel, a heatmap recorder. Each one is someone else's server deciding your load time. Count them; most sites have more than the owner thinks.
- Web fonts loaded from a third party. Two extra DNS lookups and TLS handshakes before any text renders.
- Page builder bloat. Shipping 400KB of CSS to render a page that uses 30KB of it.
What to do this week
- Run PageSpeed Insights on your two most important pages and read the field data section — that is real visitors, not a lab simulation.
- Fix images first. Resize, convert, add width and height. This alone resolves most LCP and CLS failures on contractor sites.
- Audit third-party scripts and delete what nobody reads. The chat widget nobody staffs is costing you speed and giving you nothing.
- Test on a real phone on cellular, away from your office wifi. It is a different site than the one you think you have.
Then, if you still want a redesign, at least you will not be making a slow site prettier.