#The three metrics and their pass thresholds
Largest Contentful Paint measures how long it takes the largest visible piece of content, usually a hero image or a headline, to render. Interaction to Next Paint measures the delay between a visitor's click, tap or keypress and the page visibly responding to it, replacing the older First Input Delay metric with a fuller picture of responsiveness across a whole visit rather than just the first interaction. Cumulative Layout Shift measures how much visible content moves around unexpectedly while the page loads, the jarring experience of a button shifting right before you tap it.
Each metric has a published threshold for what counts as a good, needs-improvement, or poor experience, and Google's own tools (PageSpeed Insights, Search Console's Core Web Vitals report) report a site's real-world standing against them.
FIGURE
Each metric has a published threshold for good, needs improvement and poor, reported in PageSpeed Insights and Search Console.
TABLE
Core Web Vitals: what each metric measures and its pass threshold
Thresholds as published by Google; "good" is the 75th-percentile field-data target.
| Metric | What it measures | Good threshold |
|---|---|---|
| LCP (Largest Contentful Paint) | Load speed of the main visible content | 2.5 seconds or less |
| INP (Interaction to Next Paint) | Responsiveness across all interactions during a visit | 200 milliseconds or less |
| CLS (Cumulative Layout Shift) | Unexpected visual movement while loading | 0.1 or less |
Thresholds as published in Google's own Core Web Vitals documentation, checked 2026-09-13.
#Why dealer sites specifically tend to fail
A dealer site rarely fails Core Web Vitals because of its own template. The failure comes from accumulation: a chat widget from one vendor, a trade-in valuation tool from another, an inventory search widget from a third, a review carousel from a fourth, a tag manager coordinating analytics tags from a fifth, each added independently over time, each loading its own scripts, none of them aware of what the others already cost the page.
The layout-shift failures follow the same pattern from a different angle: a chat bubble that pops in after the page has already rendered, an inventory widget that reflows the page once its data arrives, a cookie banner that pushes content down after a visitor has already started reading. Each one individually looks minor. Measured together across a real page load, they are usually the entire CLS problem.
FIGURE
The failure comes from accumulation: each vendor tool adds scripts and layout shifts, and nobody owns the total.
#What moves the score
The fix is rarely a redesign. The work is auditing what is loading (a dealer site commonly runs a dozen or more third-party scripts nobody has inventoried in one place), removing or deferring what is not earning its cost, and reserving layout space in advance for anything that loads asynchronously so it cannot shift content around it. That is the same discipline described for fixed ops and every other under-audited corner of a dealership's marketing stack: someone has to have looked at the full list.
Core Web Vitals is one ranking input among several, not a pass/fail gate on visibility by itself. A page with excellent content and business signals can still rank while carrying a mediocre score; a fast page with thin content will not automatically outrank a better answer. The practical reason to fix it anyway is conversion, not just ranking: a slow, jumpy page loses real visitors before they ever reach a lead form, independent of what it does to a ranking signal.
FIGURE
The fix is rarely a redesign. It is an inventory of what loads, then removing or deferring what does not earn its cost.