Google Swapped Its Speed Metric in 2024. Most Businesses Never Noticed.
Picture a Tampa Bay accounting firm checking Google Search Console sometime in April 2024.
Green checkmarks everywhere. Core Web Vitals: passing. No warnings, no flags. Everything looks fine.
What they do not know: Google changed what it was testing three weeks earlier. The old metric, the one their site was measured against, no longer exists. The new metric is stricter. And the site that was passing the old test is now being evaluated by a standard it was never designed to meet.
They did not change a line of code. The test changed around them.
What Google Actually Swapped
On March 12, 2024, Google officially replaced First Input Delay, known as FID, with Interaction to Next Paint, or INP, as a Core Web Vital. Google’s announcement stated: “We’re announcing that INP will officially become a Core Web Vital and replace FID on March 12 of this year, and that FID will be deprecated in this transition.”
FID was a narrow measurement. It clocked one thing: how long the browser waited before beginning to process the very first click or tap a visitor made on a page. If that first interaction was reasonably fast, the site passed, regardless of what happened on any subsequent click.
INP measures something fundamentally different. It captures the worst interaction delay across the entire session, every click, every tap, every form field, from page load until the visitor leaves. If your product filter is slow, if your date picker stalls when a user picks a date, if your checkout form takes 400 milliseconds to acknowledge a button press, INP will find it. FID would have missed all of it.
What the Metric Change Did to Pass Rates
The Web Almanac 2024, produced by HTTP Archive using Chrome UX Report (CrUX) field data from approximately 17 million websites, collected June 2024, documented the before-and-after clearly.
With FID as the interactivity metric, 48% of mobile origins passed all three Core Web Vitals. With INP, that number dropped to 43%. Five percentage points of mobile sites, sites that were passing under the old standard, now fail. Without changing a single line of code.
The individual metric breakdowns from the Web Almanac 2024 SEO chapter reveal where the problem concentrates on mobile:
- 59% of mobile sites pass LCP (Largest Contentful Paint, when the main content finishes loading, threshold under 2.5 seconds)
- 74% of mobile sites pass INP (Interaction to Next Paint, worst interaction delay, threshold under 200 milliseconds)
- 79% of mobile sites pass CLS (Cumulative Layout Shift, visual stability during loading, threshold under 0.1)
LCP remains the single biggest failure point. But INP is a close second, and the mobile-desktop gap on INP is stark: 74% of mobile sites have good INP versus 97% on desktop. That 23-point gap means a site’s responsiveness on a phone is a materially different experience from the same site on a laptop.
Why INP Is Harder on Mobile
Mobile devices have slower processors and less memory than desktop machines. JavaScript that executes in 40 milliseconds on a developer’s laptop may take 180 milliseconds on a mid-range Android phone in active use. Add third-party scripts, a live chat widget, an analytics layer, a retargeting pixel, and the processing queue grows. When a visitor taps something and the browser is busy finishing that JavaScript work, INP accumulates the delay.
FID would have measured only the first tap. If that first tap happened before the heavy scripts had fully loaded, FID looked fine. INP measures what happens when someone taps the date field on a booking form that loads after a JavaScript hydration process. It measures the real interactivity of the real page under real conditions.
For the Tampa Bay accounting firm example: their homepage loads quickly, their navigation responds fast on the first click, and their FID was passing. But their contact form, which loads a calendar picker and availability checker via JavaScript after the initial page render, makes visitors wait 380 milliseconds before seeing any visual response. Under FID, that was invisible. Under INP, it is a failing score.
The Metric Change Did Not Move Rankings
The point is simple, because there is persistent confusion about what happened in March 2024.
The INP/FID metric switch, by itself, had “very little to no impact” on search rankings, per reporting from Search Engine Roundtable covering Google’s own communications at the time. Google was explicit about this: the change in which metric was being measured did not translate into a change in ranking weight.
What caused ranking changes in March 2024 was the March 2024 Core Update, a separate Google event that happened to occur in the same month. The two events are frequently conflated. They should not be. If a site saw ranking changes in March 2024, the metric switch was not the cause. The Core Update was.
The metric switch matters for a different reason: it changed which sites are penalized for failing Core Web Vitals. Sites that were previously passing are now failing. And failing CWV does carry a ranking penalty, not from the metric switch itself, but from the ongoing page experience signal that the new metric now grades.
How to Find Your Actual INP Status
Here is the critical practical point: INP cannot be measured in Lighthouse, or in the lab-data section of any performance tool. It requires real users actually interacting with the page. No simulated environment can replicate it.
When you run PageSpeed Insights on your site, you will see two sections: a lab data section at the top (the Lighthouse score and breakdown) and a field data section below (the CrUX real-user data). The Lighthouse score does not include INP. It will not tell you whether you are passing or failing the metric Google is using.
To find your INP status, scroll past the top score. Go to the field data section. Look for “Interaction to Next Paint” in the Core Web Vitals assessment. That number, at the 75th percentile of real Chrome user sessions over the past 28 days, is what Google is grading.
If you see “insufficient data,” your site does not receive enough Chrome-browser traffic for CrUX to build a reliable field data profile. Treat that as a separate situation, not as a passing score.
The Restaurant Booking Example
Consider a Tampa Bay restaurant with a booking site. Their homepage is clean and fast. Navigation responds immediately. The Lighthouse score is 81. They have looked at this and felt confident.
But their reservation form involves a JavaScript-powered date picker that loads as a separate component after the initial page render. A visitor lands on the page, scrolls to the booking form, and taps the date field. The browser is still processing a third-party script. There is a 410-millisecond delay before the date picker appears.
Under FID, this was invisible, the visitor’s first tap had been on the navigation, which responded quickly. Under INP, this interaction is measured and it fails the 200-millisecond threshold. The site that looks like it’s passing is actually failing the metric Google has been using since March 2024.
Fixing this kind of problem is a specific technical task, it involves understanding what JavaScript is executing when, and restructuring the loading order so interactive elements are ready before visitors need them. It is not a design change. It is not a content change. It is infrastructure work.
The Check That Matters
The pass rate on mobile dropped from 48% to 43% when Google changed this metric, not because sites got slower, but because the test got harder. If your Search Console still shows green, verify that the 28-day window reflects data collected after March 12, 2024. Early green signals after the switch may have been grandfathered from the FID era.
The right check: PageSpeed Insights, field data section, INP at the 75th percentile. Under 200 milliseconds is passing. Over 200 milliseconds is failing. The number at the top of the report is not the answer.
If you want to know your actual INP status, not the Lighthouse approximation but the real field data, iServU’s free technical assessment covers exactly that. Gabriel reads your CrUX data directly and tells you which metric is failing and what kind of fix it requires. No account managers. No handoffs. No sales deck.
Book your free assessment at iservu.com.
