Quick answer: Searching core web vitals fid replaced by inp march 2024? Google has announced the phase-out of FID (first input delay), in favor of INP (interaction to next paint), as its measure of responsiveness in Core Web Vitals, on March 12, 2024. INP less than 200 milliseconds is good, between 200 and 500 milliseconds is a need for improvement and beyond 500 milliseconds is poor. There are currently three Core Web Vitals: LCP, INP and CLS (cumulative layout shift).
Core Web Vitals FID Replaced by INP March 2024: What Happened
March 2024 saw the replacement of Click-to-Show FID with INP in Core Web Vitals.INP has replaced Click-to-Show FID in Core Web Vitals March 2024.
Google’s Core Web Vitals cover the three metrics which include visual load speed, visual stability, and interactive and responsiveness. Mobile page experience and these metrics have been used for ranking since May 2021. The interactivity slot sold on March 12th 2024. However, the FID data was also lost in Google Search Console at that stage and INP took center stage as the metric for responsiveness in Core Web Vitals.
One handy ramification is that all the old articles advising you on optimization of the FID are dated. Sometime later, in 2024, FID is reportedly disabled in Chrome tooling as well; I could only find one source for this, so what is the current Google documentation?
FID vs INP Comparison
The following is the original comparison between FID and INP.
| Aspect | FID (retired) | INP (current) |
| What it measured | Input delay of the first interaction only | Latency of interactions across the whole page visit |
| What it ignored | Processing/rendering time. | Nothing in the response of the interaction |
| Good threshold | 100 ms or less | 200 ms or less |
| Typical blind spot | At the end of a session, slower interactions on the video. | Difficult to hand off interactive pages |
The real world difference is coverage. FID captures the lapse of time before a reaction begins, but not slow interactions at later moments in a session, which INP will catch. INP also captures processing time and the rendering that happens afterwards, as a more representative measure of how a page feels. According to one source about 93% of the sites had good FID, but only around 74% had good INP, exposing real problems. Assume that it is a rough guide, as the source fails to specify where its information is obtained.
How INP Is Scored
Google uses 75th percentile real user data to measure Core Web Vitals and set the Good performance benchmark. To pass the overall assessment, all three metrics must be good.
One area of divergence between the different sources is thresholds. According to one 2026 guide, the thresholds have been restricted since the change, and another one says that the thresholds are the same as the way they were originally defined. I haven’t seen this target being updated to 200ms for INP, check web.dev targets for this.
About 50% of sites still have a rough or local spot. The analysis indicates that as of October 2025, passing percentages hover around 57% for desktop and 50% for mobile, while another suggests that 48% of mobile sites meet all three criteria.
The INP Triage Ladder (Original Framework)
Follow this order in diagnosing a failing INP score. It is not an official process from google, it is an editorial method.
- Get the failed URL group. Use Search console’s Core Web Vitals report. Most remediations are focused on a page template and thus are able to fix many URLs.
- Copy the least effective communication. Find it in DevTools for Chrome by tracing it on the Interactions track. Only clicks/taps and keyboard interactions are measured, not scrolling or dragging the pointer.
- Classify the delay. Is the delay during the handler’s delay to start or is it within the handler or is it part of the subsequent rendering?
- Fix by cause. Match the fix with the delay, such as in the next section.
Common INP Causes and Fixes
INP is a common problem that can be resolved with various techniques.
| Cause | Typical fix |
| JavaScript tasks that run for longer periods of time (50 ms or more) | Try taking steps forward in the work to move it along. |
| Heavy event handlers | Make it as easy as possible on the handler and shift what you can! |
| Scripts from other providers (e.g. analytics and ads) | Remove or defer unused/non-essential scripts |
| Waterfalls when loading S.P.A.’s | Minimize client-side JavaScript when loading the page |
| CPU-heavy computation | Send it off to a web worker. |
Deferring three or four third-party scripts is typically a change that can take place the same day another source states (good for starting out with deferral). The INP in a single page apps is generally poor, since the adding of the JavaScript work of client-side routing, dynamic updates etc.
Measuring INP Correctly
Use field data in addition to lab tests. There is a gap between Lighthouse, which can’t measure INP, and a poor field result, that can sit with a good Lighthouse score. Total Blocking Time can be used as a lab proxy. To get real user data, rely on Search Console Core Web Vitals report and PageSpeed Insights, or use the web-vitals JavaScript library, using onINP for your own tracking.
INP Audit Checklist (Linkable Asset)
This linkable asset is an INP Audit Checklist.
- Viewed the Core Web Vitals report in Search Console
- There are failing URL groups/templates identified.
- Performing comparison of the field and lab result of INP
- Used the DevTools Interactions track on the interaction slowest interaction
- Tasks that are long and heavy event handlers – Listed
- Checked third party scripts and delayed non-essential scripts
- Tested heavy work in a web worker where it fits
- Rechecked, post deploy, based on field data over time.
- Updated out of date FID advice in my content
Guest Post Angles
These topics are adequate for web efficiency, SEO and developer publications:
- INP causes on WordPress websites: plugin and theme.
- The discrepancy between Lighthouse and field INP.
- Page experience and rankings: how much Core Web Vitals really matter.
Audit One Template This Week
To better understand what core web vitals fid replaced by inp march 2024 means for your website, grab a copy of your highest traffic page template and view its field in Search Console. If it is more than 200 milliseconds, identify the least responsive interaction, take measures to resolve the largest problem and repeat. One template fixed right educates you even more than a site-wide checklist.
