Core Web Vitals, Explained for Contractors

Short answer: three numbers — LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1. Measured on real visitors, and you pass only when at least 75% of them hit the threshold. Most contractor sites fail on the first.

Here is what each one is, in plain terms, and what to do about it.

The three numbers

LCP is the one that matters most for contractors, because it is the one homeowners feel. It is the moment the page stops looking empty.

INP is about responsiveness. A visitor taps “Call Now” and nothing happens for half a second — that is INP.

CLS is the jumping. You go to tap a button, an image finishes loading above it, everything shifts, and you tap the wrong thing. Ours measures 0, which is what happens when every image has its dimensions declared up front.

The two details everyone misses

These are measured on real visitors, not a test. Google uses field data from the Chrome User Experience Report — actual people, on actual phones, on actual networks. A perfect score on your office fibre connection means nothing about a homeowner on LTE in a driveway.

You must pass at the 75th percentile. At least 75% of real page views have to hit the threshold. Being fast for most people is not passing if a quarter of visitors are waiting.

That second point catches contractors out constantly. Your site can feel fine to you and still fail.

Check yours in five minutes

1. Run PageSpeed Insights. Go to pagespeed.web.dev, enter your homepage, and read the mobile tab — not desktop. Your customers are on phones.

2. Ignore the big score at first. Look for the field data section labelled as real user data. That is what Google judges you on. The large number underneath it is a lab simulation and is far less important.

3. If it says insufficient data, your traffic is too low for Google to have field measurements, and it falls back to lab estimates. Treat those as directional.

4. Test a service page too, not just the homepage. Service pages are usually heavier and are what people actually land on from search.

What actually fixes LCP

In rough order of how much they typically buy you:

Images. Almost always the biggest win. A photo straight off a phone is 4–8 MB. Ten on a homepage is 40–80 MB delivered to someone on mobile data. Correctly sized and converted to modern formats, the same images are often under 200 KB in total.

Plugins you are not using. Every active plugin loads code on every page whether that page needs it or not. Over twenty is a warning; over thirty is usually the whole story.

Render-blocking scripts. If content only appears after JavaScript executes, the visitor watches white space. This also costs you with AI crawlers, many of which do a simple fetch without running scripts.

Hosting. A $5/month shared plan puts you on a machine with hundreds of other sites. Response times climb under load — which arrives on the first 100-degree day, exactly when your traffic peaks.

What fixes CLS

Almost always one thing: images and embeds without declared dimensions. The browser does not know how much space to reserve, so content jumps when they load.

Declaring width and height on every image is unglamorous and fixes most of it. That is the entire reason this site measures 0.

What fixes INP

Usually removing JavaScript rather than optimizing it. Chat widgets, tracking scripts, popup builders, and review carousels all compete for the main thread. Each one individually seems harmless.

What passing is actually worth

Two things, and the second is bigger.

Ranking. Core Web Vitals are a ranking signal. A real one, but modest — content and links matter more.

Booked calls. This is the one. A homeowner next to a dead condenser in August is the least patient customer you will ever have. If your site takes six seconds and a competitor’s takes one, you often lose before your page renders. There is no report for that call.

A realistic target

A well-built contractor site should load its main content in under one second on mobile and hold up when traffic spikes.

For reference, this site measures LCP 288ms and CLS 0 in production — roughly nine times inside Google’s LCP threshold. That is not a boast about our cleverness; it is what you get when a site is built static, ships no JavaScript, and declares image dimensions. The techniques are available to anyone.

If yours takes six seconds, that is not a tuning gap. That is the difference between being the first call and not being called.

---

Sources: Google Search Central Core Web Vitals documentation and 2026 thresholds; Chrome User Experience Report methodology; PageSpeed Insights field data guidance; measured production field data from this site.