Tracking User Experience Metrics: Core Web Vitals for Dealership Websites

When this article first ran in January 2020, it argued that dealers should track how shoppers experience their website, not just marketing numbers like cost per click. Google has since made that measurable with three user experience metrics, the Core Web Vitals. This rewrite is for the dealer principal, general manager or marketing lead who wants to know what they mean for a dealership site, how to read them and what to fix first.

What Core Web Vitals measure

Core Web Vitals are three measurements of what a real visitor experiences while a page loads and while they use it. Google's PageSpeed Insights documentation names them: "The Core Web Vitals metrics are INP, LCP, and CLS."

• Largest Contentful Paint (LCP) measures loading: how long until the biggest thing on screen appears. On a vehicle detail page (VDP) that is usually the first unit photo. On the homepage it is often the hero banner or slider.
• Interaction to Next Paint (INP) measures response: how quickly the page reacts when a shopper taps something, such as an inventory filter, a photo arrow or a "Get pre-approved" button.
• Cumulative Layout Shift (CLS) measures stability: whether the page jumps while it loads, so the shopper taps the wrong thing because a banner or chat bubble pushed it down.

Google's web.dev team sets the "good" mark for each. LCP "should occur within 2.5 seconds of when the page first starts loading." Pages "should have a INP of 200 milliseconds or less." And CLS should stay at 0.1 or less. It measures them at "the 75th percentile of page loads, segmented across mobile and desktop devices." In plain words: three out of four visits must hit the mark, and phones are scored separately from desktops.

The thresholds, causes and fixes on a dealer site

Google's PageSpeed Insights documentation publishes all three bands. Here they are, with common dealer-site causes and fixes.

Google's web.dev guide to CLS lists the same culprits: "Images without dimensions," "Ads, embeds, and iframes without dimensions," "Dynamically injected content" and "Web fonts." Its first fix is direct: "Always include width and height size attributes on your images and video elements."

Why dealership websites struggle with Core Web Vitals

A dealer site asks more of a browser than most small-business sites:

• Inventory pages are photo galleries. A used side-by-side may have 30 or more photos, often uploaded at full resolution from a phone or pulled from a feed.
• The homepage carries OEM content. Brand banners, sliders and promotional embeds tend to be large and heavy.
• Every vendor adds a script. Chat, finance pre-qualification, trade-in value, reviews, call tracking, ad pixels and the OEM's own tags each load their own code, often from their own servers.
• Inventory filters do real work. Sorting by make, type and price on a few hundred units is heavier than a contact page.

Shoppers want all of it. The problem is that each piece comes from a different vendor, and nobody owns the total.

Do Core Web Vitals affect Google rankings?

Yes, but less than many vendors claim. Google's Search Central documentation says: "Core Web Vitals are used by our ranking systems." It also says "There is no single signal," and that good results in reports like Search Console's Core Web Vitals report "doesn't guarantee that your pages will rank at the top of Google Search results; there's more to great page experience than Core Web Vitals scores alone."

The most useful line for a dealer is this one: "Google Search always seeks to show the most relevant content, even if the page experience is sub-par. But for many queries, there is lots of helpful content available. Having a great page experience can contribute to success in Search, in such cases."

So a fast site does not outrank a more useful one. But when several dealers in your area offer similar inventory and content, page experience can help decide between them. Google also warns that "trying to get a perfect score just for SEO reasons may not be the best use of your time." For the rest of the technical picture, see our technical SEO audit for dealer websites.

The bigger reason to care is the shopper. A VDP that takes too long to show its photo, or jumps as the shopper reaches for "Text us," loses people before they become leads. That shows up as bounce rate on your dealership website, and in the end as a lower dealership website conversion rate.

Field data vs lab data

PageSpeed Insights shows two kinds of data:

• Field data comes from real Chrome users. PageSpeed Insights reports their experience "over the previous 28-day collection period." Google says field data "is useful for capturing true, real-world user experience."
• Lab data comes from one simulated visit. For mobile, Lighthouse simulates "a mid-tier device (Moto G4) device on a mobile network." Google says "Lab data is useful for debugging issues, as it is collected in a controlled environment. However, it may not capture real-world bottlenecks."

Field data decides whether a page passes. A page or site passes when "the 75th percentiles of all three metrics are Good." Lab data tells you why it fails. The two will not match, and that is normal: Google explains that field data is "a historical report about how a particular URL has performed," while lab data "is based on a simulated load of a page on a single device and fixed set of network conditions."

One more detail matters for dealers. Individual VDPs come and go as units sell, so most have too little traffic for their own field data. When that happens, PageSpeed Insights "will fall back to origin-level granularity, which encompasses all user experiences on all pages of the website."

How to check your dealership's Core Web Vitals

1. Run your homepage in PageSpeed Insights. Read the field data section at the top first, on the Mobile tab, then Desktop. Note whether the page or the whole site (origin) is being reported.
2. Run your two busiest page types: a new-unit VDP and a used-unit VDP, then an inventory results page with filters applied.
3. Open the Core Web Vitals report in Google Search Console. Google describes it as showing "URL performance grouped by status (Poor, Need improvement, Good), metric type (CLS, INP, and LCP), and URL group (groups of similar web pages)."
4. Read the issues table, not just the chart. Each row names a status and an issue, with example URLs from each group. A group's status is its worst metric, so one poor metric marks the whole group poor.
5. Fix "Poor" before "Need improvement." Google's own advice: "We recommend fixing everything labeled 'Poor' first."
6. Use the lab report to find causes. Scroll PageSpeed Insights down to the diagnostics. It names the largest image, the scripts that block the page and the elements that shifted.
7. After a fix, click "Start Tracking" in Search Console. Google says this starts "a 28-day monitoring session"; if the issue does not appear in that window, it is considered fixed. Re-check field data after a month, not the next morning.

Our guide to tracking results in Google Search Console covers the rest of that tool.

Fix the template, then audit the widgets

Most advice on this topic stops at "compress your images." For a dealership, two things matter more, and the top results rarely mention either.

Fix templates, not pages

Search Console groups URLs because "It is assumed that these groups have a common framework and the reasons for any poor behavior of the group will likely be caused by the same underlying reasons." On a dealer site, that framework is the VDP template, the inventory list template and the homepage. One fix to the VDP template fixes every unit page at once, including units that arrive next week. Fixing one VDP by hand fixes one VDP, until it sells.

So ask your website provider about templates: "What does our VDP template load before the first photo appears?"

Audit every third-party script

Few stores have ever listed every widget on their site in one place. Do it once a year:

Then sort each script into keep, delay or remove. Delaying a widget until after the page loads, or until the shopper taps its button, often helps INP and LCP without losing the feature.

What to ask your website provider

Use this checklist at your next review:

• Are our homepage, VDPs and inventory pages "Good" on mobile field data, and if not, which metric fails?
• Are unit photos resized automatically, with the first photo loaded at once and width and height set on all of them?
• Which third-party scripts load on every page, and which can be delayed?
• What changed after the last fix, measured in field data a month later?

You can also see the same certified dealership websites on our sister site, PSXDigital's certified dealership websites page.

How PSX Ascend approaches site speed

PSX Ascend's certified powersports websites are built to be fast and adaptive. The product page puts it this way: "Performance, accessibility, technical structure, local relevance, and helpful content work together. The goal is not a score alone; it is a stable site that earns discovery and makes the next action easy." The standards it names are structured content, responsive media, accessible navigation and measured performance, with the aim to protect speed, stability and crawlability as the site grows. For the phone-specific side, such as tap targets and click-to-call, see our guide to the mobile website for powersports dealers.

Sources

• web.dev (Google), Web Vitals, last updated October 31, 2024 ("good" thresholds and the 75th percentile).
• web.dev (Google), Optimize Cumulative Layout Shift, last updated February 7, 2025 (common causes of poor CLS; width and height on images).
• Google for Developers, About PageSpeed Insights, last updated October 21, 2024 (Good, Needs Improvement and Poor bands; field vs lab data; 28-day period; origin fallback).
• Google Search Central, Understanding Google page experience, last updated September 22, 2026 (Core Web Vitals and ranking).
• Search Console Help, Core Web Vitals report (URL groups, status, validation).
• Google, PageSpeed Insights and Search Console.