Chrome ends support for First Input Delay metric, pushing developers to adopt holistic Interaction to Next Paint metric.
- Chrome has completely dropped support for the First Input Delay (FID) metric.
- Developers must transition to the new Interaction to Next Paint (INP) metric.
- Optimizing for INP requires a holistic approach to interaction responsiveness.
Google Chrome has officially ended support for the First Input Delay (FID) metric, marking a transition to prioritizing Interaction to Next Paint (INP).
The announcement by Rick Viscomi, who oversees web performance developer relations for the Chrome team, confirms INP as the core metric for evaluating interaction responsiveness.
The following tools will stop reporting FID data over the next few days:
- PageSpeed Insights
- Chrome User Experience Report (CrUX)
- web-vitals.js
- Web Vitals extension
Here are some steps to take to in light of the transition from FID to INP:
- Familiarize yourself with the INP metric by reviewing the official documentation on web.dev. Understand how INP measures the full lifecycle of an interaction from input to visual update.
- Audit your site’s current INP performance using tools like PageSpeed Insights or real-user monitoring services that support INP. Identify areas where interaction responsiveness needs improvement.
- Consult the “Optimize INP” guidance on web.dev for best practices on reducing input delay, optimizing event handling, minimizing layout thrashing, and other techniques to enhance INP.
- Update any performance monitoring tools or custom scripts that currently rely on the deprecated FID metric to use INP instead. For web-vitals.js users, be prepared for the breaking change in version 5.0.
- If leveraging the CrUX BigQuery dataset, plan to update data pipelines to handle the schema changes, removing FID fields after the 202409 release in October.
