What FID measured
When a visitor first interacts with a page, the browser may be busy running JavaScript. FID measured how long that first interaction waited before its event handlers could start. Google rated 100 milliseconds or less, at the 75th percentile of page loads, as good.
FID only covered part of the problem. It ignored the time the handlers took to run and the time to draw the result, and it only looked at the first interaction. A page could pass FID while a slow "Add to cart" button later in the visit made people tap twice.
FID was replaced by INP
On March 12, 2024, INP (Interaction to Next Paint) became a stable Core Web Vital and replaced FID. Chrome deprecated FID at the same time and gave developers until September 9, 2024 to move to INP, when support for FID ended in Chrome's tools, including the Chrome UX Report and PageSpeed Insights APIs.
| FID | INP | |
|---|---|---|
| Interactions | The first one only | Every click, tap and key press |
| What it times | Delay before handlers start | Input to the next frame painted |
| Good threshold | 100 ms or less | 200 ms or less |
| Status | Retired in 2024 | Core Web Vital |
Example
A product page loads a large script. A visitor taps the image gallery after 3 seconds, when the script has finished, so the delay is 20 ms: FID is excellent. Then they choose a size, and re-rendering the variants takes 400 ms before anything changes. FID never saw it. INP reports about 400 ms, which is "needs improvement" and closer to what the visitor felt.
How to measure responsiveness now
Measure INP from real visitors with real user monitoring or read it in the Chrome UX Report. In the lab, Lighthouse reports Total Blocking Time as a stand-in, since it doesn't click. The fixes that helped FID still help INP: less JavaScript during load, smaller tasks, and lighter event handlers.
Common FID mistakes
- Still reporting FID. Google no longer uses it for Core Web Vitals, and Chrome's tools stopped supporting it in September 2024.
- Assuming a good FID means a good INP. Many pages that passed FID fail INP, because INP counts every interaction and the full response.
- Comparing old FID charts with new INP charts. They measure different things with different thresholds.
Does MetricRaven report FID?
No. MetricRaven reports INP, the metric that replaced FID. With Page speed turned on in Settings (it is off by default, on every plan), it measures INP, LCP, CLS, FCP and TTFB from real visitors with Google's web-vitals library, and rates them with Google's current thresholds.
Pages → view all shows INP and LCP at the 75th percentile next to each page's purchase rate, and the API lists pages where visitors with a slow INP or LCP paid less often than visitors with fast loads. Read it as a lead to check against conversion rate, not as proof. See Page speed vs conversion.
Questions
- Is FID still a Core Web Vital?
- No. INP replaced FID as a Core Web Vital on March 12, 2024, and Chrome ended support for FID in its tools on September 9, 2024.
- What was a good FID score?
- 100 milliseconds or less at the 75th percentile of page loads. For INP, its replacement, good is 200 milliseconds or less.
- Why did Google replace FID with INP?
- FID measured only the delay before the first interaction started being handled. INP measures every interaction during the visit, from input to the next painted frame, so it captures slow responses FID missed.
- What should I measure instead of FID?
- INP from real visitors, through real user monitoring or the Chrome UX Report. In lab tests, Total Blocking Time is a rough stand-in.