Good is the minority: dealer site speed, Core Web Vitals, and the script tax
Across a sample of more than 3,300 dealer domains, most pages fail the field thresholds on mobile. The cause is rarely the platform. It is the number of things we asked the page to load.
Manifold Studio · automotive search & data

Audio briefing
Listen to this insight
Extraction-ready summary
- Core Web Vitals are field measurements at the 75th percentile: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, Cumulative Layout Shift under 0.1. A lab score proves nothing about a shopper on a three-year-old phone.
- In a mobile field-data sample of more than 3,300 dealer domains, a domain counted as good only when all three metrics passed, and good was the minority. The failures cluster on Largest Contentful Paint and Interaction to Next Paint, which are the two the vendor list controls.
- A randomized delivery experiment on one brand's dealer pages removed the usual excuse: when visitors were randomly assigned to a faster delivery path for the same page, the faster arm produced more shopper action. Randomization, not correlation, is what makes that arguable.
- Every marketing tag is a loan against interaction responsiveness. A performance budget per template, a tag register with a named owner per tag, and one holdout test will do more for conversion than any speed vendor that solves the problem by adding another script.
A vehicle detail page took 6.2 seconds to show a photograph of the car. That is a field number, not a lab score: 75th percentile, mobile, a mid-range Android two generations behind the current handset, on cellular in a mid-size metro. The shopper had already tapped back, opened a competitor's listing and read a price. The dealer's page eventually loaded perfectly.
This is the part of retail marketing that no creative review touches. A page that loads is not a feature. It is the precondition for every other feature, and on dealer sites it is usually the thing that has been traded away one vendor request at a time.
What is actually being measured
Core Web Vitals are three numbers taken from real Chrome usage rather than a test device in an office, reported at the 75th percentile and segmented by device class. A URL passes when three quarters of its real loads clear the thresholds.
Metric
Largest Contentful Paint
- What it measures
- Time until the main content is visible
- Good
- 2.5s or less
- Middling
- 2.5s to 4.0s
- Poor
- over 4.0s
Metric
Interaction to Next Paint
- What it measures
- Time the page takes to respond to a tap
- Good
- 200ms or less
- Middling
- 200ms to 500ms
- Poor
- over 500ms
Metric
Cumulative Layout Shift
- What it measures
- How much the content jumps while loading
- Good
- 0.1 or less
- Middling
- 0.1 to 0.25
- Poor
- over 0.25
| Metric | What it measures | Good | Middling | Poor |
|---|---|---|---|---|
| Largest Contentful Paint | Time until the main content is visible | 2.5s or less | 2.5s to 4.0s | over 4.0s |
| Interaction to Next Paint | Time the page takes to respond to a tap | 200ms or less | 200ms to 500ms | over 500ms |
| Cumulative Layout Shift | How much the content jumps while loading | 0.1 or less | 0.1 to 0.25 | over 0.25 |
Interaction to Next Paint replaced First Input Delay in March 2024, and that single change explains why a great many sites that passed for years stopped passing. First Input Delay measured only the delay before the first interaction could be handled. Interaction to Next Paint measures every interaction on the page and takes the worst one. A site whose first tap was fine but whose third tap stalled behind a chat widget was never fast. It was unmeasured.
The sample, and what it says
For this piece we measured 3,300-plus dealer domains, pulled from brand store-locator files rather than from a vendor's customer list, using mobile field data over a trailing 28-day window. A domain counted as good only if all three metrics cleared their thresholds at the 75th percentile. Under that rule, good is the minority: most dealer domains fail at least one metric, and the failures are not evenly spread. Cumulative Layout Shift is the one most sites pass. Largest Contentful Paint and Interaction to Next Paint are where the sample breaks.
That distribution tells you where the cause is. Layout shift is a design discipline problem, and most dealer themes have solved it. Largest Contentful Paint on a vehicle detail page is one element, almost always the hero photograph or the inventory module, and both are typically lazy-loaded or injected by JavaScript that has to arrive first. Interaction to Next Paint is main-thread contention, which in practice means the total JavaScript on the page and the order in which it wakes up.
Neither of those is a design decision. Both are a consequence of the vendor list.
Method note: these are point-in-time figures, so re-run the sample before quoting a number in a review. The thresholds are Google's published ones, unchanged. The point of the number is the shape of the distribution, not the third significant figure.
The experiment that removes the usual excuse
The standard objection is that fast sites are fast because they belong to better operators, and better operators sell more cars. That is a real confound, and it is why cross-sectional speed data can never prove causality on its own.
One national brand answered it with a randomized experiment across its dealer pages. Visitors were assigned at random to receive the same page through a faster delivery path or through the standard one: same inventory, same offers, same photography, same forms. Assignment was random, so the two groups were alike in every respect except delivery. The faster arm produced more shopper action, including more vehicle-detail views per session and more lead submissions.
That design is the whole value of the study. It converts a correlation everyone already believed into a causal claim you can defend to a fixed-ops director who does not care about milliseconds. If your brand's digital team ran something similar, ask for the readout and cite the design, not a lift percentage lifted from a summary slide.
The script tax
Open a dealer vehicle detail page in a browser and count the third-party origins. A typical set looks like this.
What is on the page
Chat or messaging widget
- Who asked for it
- Sales, sometimes the OEM program
- What it costs
- 200KB to 900KB of JavaScript, often booted on interaction
- What it returns
- A channel with real value and usually no measured lead attribution by store
What is on the page
Session recording and heatmaps
- Who asked for it
- Marketing, occasionally a pilot nobody closed
- What it costs
- Main-thread work on every page view, sometimes on every scroll
- What it returns
- Behavioral evidence, if anyone watches the replays
What is on the page
A/B testing or personalization
- Who asked for it
- Marketing
- What it costs
- Blocks rendering while the variant is decided
- What it returns
- Lift measurement, on a sample that is often too small per rooftop
What is on the page
Review widget
- Who asked for it
- Reputation or OEM program
- What it costs
- Third-party render in a critical layout slot
- What it returns
- Star ratings and review text
What is on the page
OEM co-op tag
- Who asked for it
- Brand program
- What it costs
- Varies, generally non-negotiable
- What it returns
- Co-op eligibility
What is on the page
Retargeting and audience pixels
- Who asked for it
- Media agency
- What it costs
- Small files, repeated across five platforms
- What it returns
- Remarketing pools
What is on the page
Inventory widget
- Who asked for it
- Website or inventory vendor
- What it costs
- The heaviest element on the page, frequently the LCP element
- What it returns
- The vehicles themselves
What is on the page
Consent banner and tag manager
- Who asked for it
- Legal and analytics
- What it costs
- One blocking script supervising seven others
- What it returns
- Compliance and tag control
| What is on the page | Who asked for it | What it costs | What it returns |
|---|---|---|---|
| Chat or messaging widget | Sales, sometimes the OEM program | 200KB to 900KB of JavaScript, often booted on interaction | A channel with real value and usually no measured lead attribution by store |
| Session recording and heatmaps | Marketing, occasionally a pilot nobody closed | Main-thread work on every page view, sometimes on every scroll | Behavioral evidence, if anyone watches the replays |
| A/B testing or personalization | Marketing | Blocks rendering while the variant is decided | Lift measurement, on a sample that is often too small per rooftop |
| Review widget | Reputation or OEM program | Third-party render in a critical layout slot | Star ratings and review text |
| OEM co-op tag | Brand program | Varies, generally non-negotiable | Co-op eligibility |
| Retargeting and audience pixels | Media agency | Small files, repeated across five platforms | Remarketing pools |
| Inventory widget | Website or inventory vendor | The heaviest element on the page, frequently the LCP element | The vehicles themselves |
| Consent banner and tag manager | Legal and analytics | One blocking script supervising seven others | Compliance and tag control |
Every one of these was bought to answer a question. Not one of them was bought with a millisecond budget attached, and none of the people who bought them owns the total. That is the script tax: a page assembled by eight stakeholders, each optimizing their own line item, with nobody accountable for the sum.
The pattern is visible in the metric that breaks first. Tags that fire on idle are expensive but survivable. Tags that boot on scroll, re-render a header, or hold the main thread for 300 milliseconds when a shopper taps a trim selector are what push Interaction to Next Paint past 500 milliseconds, and the shopper experiences that as a site that ignores them.
What a speed program actually looks like
- Measure field data per template, not per site. A vehicle detail page, a search results page, a service scheduler and a parts lookup are four different products with four different budgets.
- Write the budget down: transferred weight, compressed JavaScript, third-party origin count, per template. Review against it the way you review against brand guidelines.
- Keep a tag register with a named owner per tag and the question it answers. Any tag without an owner is removed. This is the same register as the stack audit, and it is the single highest-leverage document in the whole discipline.
- Fix the three things that weigh most, in order: font loading, hero imagery, and the boot sequence of third-party scripts. Most dealer pages are fixed by deferring what does not need to run before the first paint.
- Attack the HTML latency you can control: server response time and edge caching for the document itself. A cached document that arrives in 200 milliseconds changes what the rest of the page can do.
- Refuse the speed tool that solves speed by adding a script. There are legitimate performance vendors. A tag that claims to optimize the page while becoming part of the page is not one of them.
- Prove the change in the field with a holdout: hold a third of traffic or a control set of rooftops, change one template, and compare 28 days of field data and leads. Without a holdout you have an opinion with a chart.
The uncomfortable part
Good Core Web Vitals will not sell a car on their own. There is no version of this where a 2.1-second Largest Contentful Paint becomes a headline in a monthly review. What speed does is stop taxing everything else you already pay for: paid clicks that land on a page nobody waits for, crawl budget spent on templates that time out, merchandising work on vehicle descriptions a shopper never reaches, and a lead form that loads after the decision was made somewhere else.
It is also the only conversion lever in the building that can be fixed without changing price, offer or inventory. That is rarer than it sounds, and it is why the deck has a section on it.
Creative compliance gate
No creative reaches a flight before the manufacturer signs it off.
Every piece of creative named in this insight, including anything produced with AI assistance, clears the brand’s review before media spend, organic scheduling or event capture goes live. The four rules below are the ones that keep a campaign on its date.
- 01
Submit the asset pack, not the idea
Stills, cut-downs, captions, alt text and end cards travel together, with the intended flight dates attached. Reviews stall on packages that arrive in pieces.
- 02
Build the review into the flight date
Two to three weeks covers most OEM programs. Any clip carrying a product claim, an incentive or a co-op match needs longer, and a launch week is the wrong time to find that out.
- 03
Nothing flies unapproved
That includes the "test" post, the organic support cut and the paid boost of an organic clip. If it is public, it was published, and compliance will treat it that way.
- 04
Store the approval with the asset
Keep the sign-off reference and its expiry alongside the creative. Reusing an approved cut saves the next review; reusing an expired one restarts it.
Answer engine fuel
Questions buyers actually ask
Is Core Web Vitals a ranking factor?
It is one signal among many, and a modest one. Treat ranking as a side effect. The direct effect is on the shopper: a page that responds late loses the session before any offer is read, and that loss shows up in conversion rate and in the cost of every paid click you send there.
Will moving to a new platform fix it?
Only if the vendor list moves with it. Most dealer pages are slow because of what is loaded onto the template, not what renders it. A replatform that carries the same twenty tag requests into a new CMS reproduces the same numbers with a larger invoice. Set the budget before the migration, not after.
Lighthouse gives me a 95, but Search Console says poor. Which is right?
Search Console is the field, Lighthouse is the bench. The field includes real devices, real networks, real interactions and every tag that only fires for a logged-in or consented visitor. If the two disagree, the field number is the one your shopper experiences.
What does a realistic performance budget look like?
Set it per template, because a homepage and a vehicle detail page are different products. A workable starting point: under 1.5 MB transferred on a mobile vehicle detail page, under 300 KB of compressed JavaScript, no more than eight third-party origins on the page, and one named owner for each. Then hold it in review the way you hold brand guidelines.
Primary sources
Filed under Infrastructure
More from this desk →Read next
The duplicate stack: an audit that finds what you are paying for twice
Forty-one tools, nineteen actual jobs, eleven jobs with more than one owner. The consolidation audit is a register, four tests and an order of removal, and its real output is not savings. It is a stack small enough that one person can be accountable for it.
InfrastructureToken minimizing: price finished work, not tokens
Per-token prices fell about 98% since 2024 and corporate AI bills still rose. The spend is not in answers, it is in agents re-telling the problem — so the unit that matters is cost per finished task.