What Are Core Web Vitals? A Guide for Contractor Websites

The Three Core Web Vitals Metrics

Google measures three things, and each one answers a different question about how a page behaves for a real visitor.

Largest Contentful Paint (LCP)

LCP measures how long it takes for the largest visible piece of content, usually a hero image or headline, to fully load. Google considers 2.5 seconds or faster good. A homeowner searching “emergency plumber near me” on a phone with a weak signal will not wait much longer than that before tapping back to the search results.

Interaction to Next Paint (INP)

INP measures how long the page takes to visibly respond after someone taps a button, link, or form field. It replaced an older metric called First Input Delay in March 2024 because INP measures responsiveness across the whole visit, not just the first click. Google considers 200 milliseconds or faster good. A slow INP feels like the page is ignoring a tap on the phone number.

Cumulative Layout Shift (CLS)

CLS measures how much visible content jumps around as a page finishes loading, usually because an image or ad loads late and pushes everything below it down. Google considers a score under 0.1 good. A common example on contractor sites: a visitor lines up a tap on “Call Now,” and the button shifts down as a slow-loading image loads above it, so the tap lands on the wrong thing.

Is a good score the same for every business?

Yes. Google’s thresholds do not change by business size or industry: LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1, measured as good for at least 75 percent of real visits in Search Console’s field data. A site does not need every single visit to pass; it needs to clear that 75 percent bar consistently across the reporting period for Google to treat the page group as good.

Google reports all three tiers, not just pass or fail, which matters when reading the Core Web Vitals report: a URL group sitting in “needs improvement” is not failing, but it is also not yet getting the full benefit of a good score, and it is usually the cheapest tier to fix since the underlying problem is often smaller than one already scored as poor.

Why Core Web Vitals Matter Beyond Rankings

Ranking is only one reason to care about these three numbers. Each one maps to a specific business outcome that shows up whether or not Google is watching.

They set a ranking ceiling, not just a ranking boost

When two pages cover a search equally well, Google treats Core Web Vitals as one of the deciding factors between them. That makes a poor score a ceiling on how well a page can perform relative to a similarly relevant competitor, not simply a small deduction, which is why fixing it can unlock movement that content changes alone did not.

They directly affect how many visitors leave immediately

The longer a page takes to become usable, the higher the share of visitors who leave before it ever loads. This effect gets sharply worse the slower a page is, which is exactly why an emergency plumbing or HVAC search, where the visitor is already anxious and in a hurry, is the least forgiving type of search for a slow page.

They affect whether a tap on the phone number actually works

A poor INP score means taps and clicks feel delayed or unresponsive. On a contractor site, that delay falls directly on the one action that matters most: tapping to call. A visitor who taps twice because nothing seemed to happen, or who gives up and calls the next result, is a Core Web Vitals problem showing up as a lost job, not just a lost visit.

They protect the click a visitor almost made

A page that shifts as it loads, so a “Call Now” button moves just as someone taps toward it, produces exactly the kind of accidental miss-click or frustrated exit that Cumulative Layout Shift is built to catch. Fixing CLS is one of the few Core Web Vitals improvements a visitor can feel immediately, even without knowing the technical name for what changed.

Do Core Web Vitals Actually Affect Rankings, or Cause a Penalty?

Core Web Vitals are a confirmed part of Google’s page experience signals, but Google’s own engineers have described them as a smaller factor than content relevance, not a way to out-rank a page that answers the search better. The most accurate way to think about it: Core Web Vitals rarely decide who ranks first, but they can decide the tiebreak between two similarly strong pages, and a genuinely bad score can hold a good page back.

There is no penalty attached to a poor score. It is one signal among many, and it never overrides strong, relevant content. For a contractor, the more direct cost of poor Core Web Vitals is not a ranking penalty. It is the visitor who found you, waited three extra seconds, and called the next result instead. Page speed is a conversion problem wearing a ranking problem’s name.

Core Web Vitals sit alongside a separate, larger quality question Google’s systems are also weighing: whether the content itself demonstrates real experience and expertise. See our guide on E-E-A-T for how that broader framework works alongside these three technical metrics.

Why This Matters More for Plumbing, HVAC, and Solar Sites

Three things make Core Web Vitals a bigger deal for home service and solar sites than for most businesses.

Mobile share is higher

Emergency and same-day searches for plumbing and HVAC skew heavily toward phones, often on the go or with a weak connection. A desktop-tested “fast enough” site can still fail Core Web Vitals badly on a real mobile connection, and scores are reported separately for mobile and desktop in Search Console, with mobile the one to prioritize for this reason.

The stakes of a slow tap are higher

A slow response on an e-commerce product page costs one sale. A slow response on a plumber’s “Call Now” button during a burst pipe costs the job entirely, because the homeowner is already calling the next name on the map pack.

Solar pages carry more visual weight

Solar sites often load large hero images of installed panels, financing calculators, and incentive tables. Each of those is a common cause of poor LCP or CLS if it is not built carefully, and solar’s longer research cycle means a slow page loses a visitor who might otherwise have returned.

How to Check Your Scores

Three free tools give slightly different views of the same three metrics, and using more than one gives a fuller picture.

• Google Search Console: the Core Web Vitals report under Experience shows real visitor data for your actual pages, grouped as good, needs improvement, or poor.
• PageSpeed Insights: enter one URL and get both real-world data (if enough visitors exist) and a lab test, with specific fixes ranked by impact.
• Chrome DevTools Lighthouse: a deeper, page-by-page lab audit useful once you are already fixing something and want to confirm the change worked.

Search Console’s field data is the most trustworthy number, because it reflects real visitors on real devices and connections, not a single lab test from one location.

Common Causes on Contractor Sites, and the Fix

Most Core Web Vitals problems on plumbing, HVAC, and solar sites trace back to a small set of repeat offenders.

Can I fix these myself without a developer? Basic fixes such as compressing images and removing unused plugins can often be done without code. Fixing render-blocking scripts, font loading, and layout stability usually needs someone comfortable editing the site’s code or template. Fixing these is mostly a one-time technical job, not an ongoing content task, which is why it is usually handled as part of a broader website design or technical SEO engagement rather than on its own.

What Core Web Vitals Do Not Measure

Part of using Core Web Vitals correctly is knowing what they leave out, since treating them as a full health check leads to a false sense of security.

They are not a full SEO score

A page can pass all three Core Web Vitals and still rank poorly because the content is thin, the title does not match the search, or the site lacks trust signals. Speed supports good content. It does not replace it.

They are not an accessibility audit

A fast, stable page can still be hard to use for a visitor relying on a screen reader or keyboard navigation. Accessibility is checked separately, commonly with the WAVE tool or Lighthouse’s accessibility tab, not through Core Web Vitals.

They are not a security check

Core Web Vitals say nothing about whether a site is safe from malware, has a valid SSL certificate, or handles form data securely. Those are separate checks worth running alongside a Core Web Vitals audit, not instead of it.

A Practical First Audit for a Contractor Site

A first Core Web Vitals check does not need to be complicated. This order finds the highest-impact problems first, and how often to repeat it: check monthly, and immediately after any redesign, plugin update, or new booking or chat tool, since those are the most common causes of a new regression.

• Open Search Console’s Core Web Vitals report and note which URL groups show as “poor” or “needs improvement.”
• Run your homepage and your busiest service page through PageSpeed Insights and read the specific opportunities it lists, not just the score.
• Check whether your hero image is compressed: a photo straight from a phone camera is often 3 to 8 MB, when 150 to 300 KB is usually enough for the web.
• Count how many third-party scripts load on the page: chat widgets, review badges, ad pixels, booking tools. Each one adds weight.
• Test the page on an actual phone over cellular data, not just over office wifi on a laptop, since that is closer to how most visitors experience it.

A first audit like this usually surfaces two or three fixes that matter far more than the rest, which is a better use of time than trying to optimize everything at once.

Hosting and Multi-Location Pages: Two Overlooked Factors

Two contractor-specific factors affect Core Web Vitals more than owners usually expect.

Shared hosting is a common hidden cause

Many small business sites run on inexpensive shared hosting, where the same server resources are split across many unrelated websites. When a neighboring site on the same server gets a traffic spike, every site on that server can slow down, including yours, with no warning and nothing visibly wrong on your end. Field data in Search Console showing intermittent, unexplained slowness is a common sign of this.

Service-area and city pages multiply the problem

An HVAC or solar company with a dozen city or service-area pages effectively has a dozen separate Core Web Vitals scores, since Google measures groups of similar URLs. A slow template used across every city page means every one of those pages inherits the same problem at once, which is why fixing the shared template, rather than one page at a time, is usually the faster path to improvement.

Does a chatbot or booking widget hurt Core Web Vitals?

It can. Third-party widgets load their own scripts, and a heavy one can slow INP or push content around and raise CLS. Test the page before and after adding any new tool, the same way you would test after a redesign.

Core Web Vitals in an AI Search Era

Search results now often include an AI-generated summary above the traditional list of links, and that shift raises a natural question about whether page speed still matters the same way.

Do Core Web Vitals affect AI Overviews?

Google has not published a Core Web Vitals requirement specific to being featured in an AI summary. What is known is that AI-generated answers still draw from pages Google has already crawled, indexed, and judged trustworthy and usable, all of which page experience contributes to. A slow, unstable page is not automatically excluded from an AI summary, but it competes at a disadvantage against a fast, well-structured one for the same underlying reasons it competes at a disadvantage in traditional results.

Speed still protects the click that does happen

Whether a visitor arrives from a traditional result or clicks through from an AI summary, the same Core Web Vitals experience decides whether they stay or bounce once they land. As more of the discovery step moves into AI-driven surfaces, the on-page experience for the visitors who do click matters just as much, not less. This is part of what our AI SEO service looks at alongside content structure, since a technically fast, stable page is one of the easier signals for both traditional crawlers and AI systems to read cleanly.