Quick Summary
Google replaced First Input Delay with Interaction to Next Paint (INP) in March 2024. INP measures how long your page takes to visually respond after a click or tap. Dealer inventory pages — the SRP, fail it more than any other page on the site because every filter click rebuilds the DOM, fires analytics, and re-renders pricing logic on the same main-thread task. Pages with a poor INP (above 500ms) lose ranking ground in mobile organic, which is where 70%+ of inventory traffic lives. The fix list is short and almost all of it is platform-side: debounce filter inputs, defer third-party tags off the click handler, lazy-render off-screen vehicle cards, and yield to the main thread between filter and re-render. If your platform won't ship those changes, that's a vendor conversation, not an SEO problem.
What You Should Know
For GMs
- Tell your team to pull a CrUX report on your inventory URL this week, if mobile INP is above 500ms, you're losing mobile rankings to faster competitors.
- Tell your digital lead to time-test five filter clicks on the SRP from a mid-tier Android phone, not their iPhone. The gap is usually 3x.
- Make INP a line item in the next platform QBR. If your provider can't quote a date for the fix, that's the answer.
For Marketing Directors
- Audit which third-party tags fire on filter click, chat widgets, trade-in tools, and session recording are the usual suspects. Move them to load on idle.
- Request lazy rendering of vehicle cards below the fold. A 60-card SRP rendering all at once is the single biggest INP killer.
- Add INP to your monthly performance dashboard alongside LCP and CLS. Track p75 mobile, not desktop averages.
For Dealer Principals
- This is a vendor question, not an agency one. Ask your website provider in writing whether SRP INP is on the 2026 roadmap and when.
- If two of your competitors are on the same platform and one has fixed it, the platform can fix it. Push.
- Budget impact is small, most fixes are configuration, not custom dev. The real cost is ranking ground lost while you wait.
“INP is the Core Web Vital nobody on the dealer side budgeted for. Filter clicks on inventory pages light up every analytics tag, every chat handler, every motion library, and that is exactly the interaction Google now scores you on.”
Tim Boyle
Founder & President, A3 Brands
Your Core Web Vitals dashboard is green and the inventory page still hands every click to the dealer down the road. That's INP — the Core Web Vital that quietly replaced FID in March 2024, and the one most dealer SRPs fail without realizing it. Across our paying-client cohort, we've watched pages that scored well on FID slip under INP because filter clicks now have to clear a different bar. Here's what changed, why dealer inventory pages fail more than any other page type on the site, and the four fixes that actually close the gap.
What changed in March 2024
Google replaced First Input Delay (FID) with Interaction to Next Paint (INP) as one of the three Core Web Vitals on March 12, 2024. The two metrics measure different things. FID only timed how long the browser took to start handling a click. INP times the full round trip, click in, pixels updated on screen, across every interaction on the page, and reports the worst one (or close to it) at the 75th percentile.
That distinction is the whole story for dealers. FID was easy to pass because browsers are fast at acknowledging a click. INP is hard to pass because actually rebuilding an inventory grid after a filter change is slow. A page that scored green on FID can score red on INP without a single line of code changing.
The thresholds Google publishes: under 200ms is good, 200–500ms needs improvement, over 500ms is poor. Most dealer SRPs we audit land between 450ms and 900ms on mobile. That's not a corner case, that's the median.
200ms
INP threshold for a passing score
Google's 'good' bar at the 75th-percentile mobile field score. Most dealer SRPs measure 450ms to 900ms.
Why dealer inventory pages fail INP
Inventory grids do more work per click than any other page on a dealer site. A typical filter click, say, narrowing to "Certified, under $30k, AWD", kicks off five things in roughly the same browser task: a fetch to the inventory API, a full re-render of the results grid, a price recalculation that runs incentives logic, an analytics event, and usually a re-init of any chat or trade-in widget riding along on the page.
All of that runs on the main thread. The main thread is single-lane. While it's busy rebuilding 60 vehicle cards, the browser cannot paint pixels, which is exactly what INP measures. Every millisecond the main thread spends on a vehicle card is a millisecond the user stares at an unchanged screen.
The second culprit is third-party tags. Most dealer sites carry 30–50 tags through Google Tag Manager. When a filter click fires an event, every listener attached to that event runs before the browser is allowed to paint. We've seen single filter clicks trigger eight different vendor scripts. That's where the 700ms numbers come from. Our technical SEO audit process almost always finds the culprit in the tag stack before it finds it in the platform code.
The fix list (and what your platform will accept)
There are four fixes that move the needle, ranked by impact and by how likely your dealer platform is to actually ship them.
1. Debounce filter inputs (high impact, easy ask).
Range sliders and text inputs that fire on every keystroke or pixel of drag are the worst offenders. A 150ms debounce drops INP dramatically and is a one-line change. Every major platform supports this; some haven't enabled it.
2. Defer third-party tags off the interaction handler (high impact, medium ask).
Move chat widgets, session recorders, and non-essential analytics to load on requestIdleCallback or after a 2-second delay. This is a GTM configuration change you can usually make yourself without involving the platform.
3. Virtualize the results grid (high impact, hard ask).
Only render the vehicle cards visible in the viewport plus a small buffer. Rendering 12 cards instead of 60 cuts main-thread work by roughly 80%. This is a platform-side build and not all providers offer it.
4. Yield to the main thread between work units (medium impact, hard ask).
Use scheduler.yield() or setTimeout(0) to break long tasks into chunks the browser can interrupt to paint. Same conversation: platform-side, requires real engineering.
The honest read is that fixes 1 and 2 will get most dealers from "poor" to "needs improvement." Fixes 3 and 4 are what get you to "good." If your provider won't commit to 3 and 4 in 2026, you have the same conversation as the one in our website traffic dropped guide, at some point the platform is the problem.
INP fix list, ranked by impact and platform difficulty
| Fix | Impact | Who ships it |
|---|---|---|
| Debounce filter inputs (150ms) | High | Platform — usually a config flag |
| Defer third-party tags off click | High | You, in Google Tag Manager |
| Virtualize results grid | High | Platform — real engineering |
| Yield to main thread between tasks | Medium | Platform — real engineering |
| Lazy-load below-fold vehicle images | Low | Already done on most platforms |
How to measure INP on your own SRP
There are two numbers that matter and they don't always agree. Field data comes from real Chrome users and is what Google ranks on. You get it from the Chrome User Experience Report (CrUX) in Search Console under Core Web Vitals, or from PageSpeed Insights when you run a URL. Lab data comes from synthetic tests like Lighthouse and is useful for debugging but doesn't drive rankings.
For dealers, always look at the field number, always look at the mobile p75, and always look at the URL group for inventory specifically. The site-level average hides the SRP problem because your homepage and VDPs usually pass. We cover the broader read on this in our automotive SEO guide when ranking drops are platform-driven and not content-driven.
For day-to-day debugging, install the Web Vitals Chrome extension and click through your own SRP from a throttled mid-tier Android profile in DevTools. That replicates what 70% of your shoppers actually experience. The number you'll see on your own laptop in Wi-Fi has almost nothing to do with what Google scores you on.
Don't trust your laptop
The INP score you see on your own MacBook over Wi-Fi has almost nothing to do with the score Google ranks you on. Google uses 75th-percentile field data from real Chrome users, and the majority of your shoppers are on mid-tier Android phones over LTE. Always pull the mobile field score from Search Console and replicate the user environment in DevTools — slow 4G, 4x CPU throttle, mid-tier Android profile.
What this actually does to rankings
Core Web Vitals are a confirmed Google ranking signal, but they're a tiebreaker, not a primary one. The way it shows up for dealers is at the bottom of page one of mobile organic for high-intent inventory queries, "used trucks under 25k near me," "certified Honda CR-V Phoenix." If two dealers have similar inventory, similar reviews, and similar backlinks, INP is one of the things that decides which one outranks the other.
That tiebreaker matters more than it sounds. Search visibility on mobile compounds with click-through rate; faster pages keep users from bouncing back to the SERP, which Google reads as a quality signal. The GEO Citation Lab found that top-quartile cited pages average 1,943 words; bottom-quartile pages average 170, an 11.4x ratio, which tells you content depth still leads the ranking conversation. But CWV decides which of two deep, well-linked pages comes out on top.
The second-order effect is AI search. Pew Research Center reported in July 2025 that 60% of question-format queries trigger AI Overviews, and AI Overviews pull from the same organic ranking pool that CWV influences. A slow SRP doesn't just lose its blue-link rank; it loses its shot at being the inventory page Google's AI cites. Backlinks compound the same way, which is why we put link-building work and technical work on the same roadmap, not separate ones.
The vendor conversation, scripted
Most dealers can't push code to their own SRP. The fix lives at the platform, Dealer.com, DealerOn, Sincro, DealerInspire, fusionZONE, and the rest. Which means this comes down to how you ask.
The email that works looks something like this: "Our SRP INP is currently [X]ms at the mobile p75 per Search Console. Google's threshold for 'good' is 200ms. Can you confirm whether (a) input debouncing on filter controls, (b) virtualized rendering of the results grid, and (c) deferred loading of non-essential third-party tags are on the 2026 roadmap, and if so, the target ship date?" Specific, dated, and quotable in a QBR.
The answer you get tells you everything. If they cite a date, great, track it. If they say "we're monitoring" or "every site is unique," that's a stall. Compare notes with other dealers on the same platform; if one rooftop has the fix and you don't, it's a config flag, not an engineering project. We see the same dynamic in our dealership SEO pricing guide, the platform is often where 30% of the spend is going and 10% of the value is coming from.
How to push your platform on INP
Pull the number
Mobile p75 INP from Search Console Core Web Vitals report, filtered to your inventory URL group.
Email in writing
Ask whether debouncing, virtualization, and tag deferral are on the 2026 roadmap and request a target ship date.
Compare with peers
Find another rooftop on the same platform. If they shipped it, it's a config flag, not a build.
Make it a QBR line item
Track the date. If two QBRs pass without progress, the platform is the problem, not SEO.
What we don't know yet
A few honest caveats. We don't have public data on the exact ranking weight Google assigns to INP versus the other two CWV metrics; the company has only said it's a confirmed signal. So when we say "INP is a tiebreaker," that's based on observed correlations across the dealers we work with, not a Google-published coefficient.
We also don't yet know how AI engines weigh CWV when picking sources. ChatGPT and Perplexity haven't published anything on it. The GEO Citation Lab found that ChatGPT cites approximately 5.64x deeper per citation than Google AI Overview, but cites fewer total sources, meaning fewer pages get picked, and the criteria are still partly opaque. CWV may matter to AI ranking; it may not. We'll know in 12 months.
Finally, INP is going to keep moving. The 200ms threshold is what Google publishes today; the trend across every CWV metric since 2020 has been to tighten the threshold once enough sites pass it. Build the fix list assuming the bar gets harder, not easier.
Key Takeaways
- ✓INP replaced FID as a Core Web Vital in March 2024 and measures full click-to-paint time, not just input delay.
- ✓Dealer SRPs fail INP more than any other page because filter clicks rebuild the DOM, fire analytics, and re-init widgets on one main-thread task.
- ✓Passing scores: under 200ms is good, 200–500ms needs improvement, over 500ms is poor. Most dealer SRPs land between 450ms and 900ms on mobile.
- ✓Four fixes drive 90% of the gain: debounce filter inputs, defer third-party tags, virtualize the results grid, and yield to the main thread.
- ✓Fixes 1 and 2 are usually configuration. Fixes 3 and 4 are platform-side and require a vendor commitment with a date.
- ✓Always read mobile p75 field data, not lab scores or desktop averages. The Chrome User Experience Report in Search Console is the source of truth.
- ✓CWV is a tiebreaker ranking signal, it decides which of two similar dealers wins page-one mobile real estate, including AI Overview citations.
Founder & President, A3 Brands
Tim spent a decade distributing products to 3,000+ dealerships, ran the Internet Sales department at Baker Automotive Group, and served as Acura's Field Program Manager and Digital Strategist at Shift Digital before founding A3 Brands — the only SEO agency built exclusively for car dealerships.
Frequently Asked Questions
What is INP and how is it different from FID?
What is a passing INP score for a dealer inventory page?
Why do dealer inventory pages fail INP more than other pages?
Can a dealer fix INP on their own or does it require the platform?
Does INP actually affect Google rankings for dealers?
How do I check my dealership's current INP score?
Sources & References
- Google Search Central — Core Web Vitals — Confirms INP replaced FID as a Core Web Vital on March 12, 2024, and publishes the 200ms / 500ms thresholds.
- Chrome User Experience Report (CrUX) — Source of the field-data INP scores Google uses for ranking; surfaced in Search Console and PageSpeed Insights.
- GEO Citation Lab — Backs the page-length and citation-depth statistics on top-quartile content and ChatGPT vs AI Overview citation behavior.
- Pew Research Center, July 2025 — Source for the share of question-format and long-tail queries that trigger AI Overviews.
- web.dev INP guidance — Reference for debouncing, yielding, and virtualization patterns recommended by the Chrome team.
Find out if your SRP is failing INP
We'll pull your live Core Web Vitals data, identify which third-party tags are killing your mobile INP score, and tell you exactly what to ask your platform to fix. No pitch, no obligation.