INP (Interaction to Next Paint) is the Core Web Vitals metric that measures page responsiveness, meaning the time elapsed between a user interaction (click, tap, key press) and the moment the page visually responds.
Key Points
- It officially replaced FID (First Input Delay) as the responsiveness metric in Core Web Vitals, starting March 2024.
- An INP under 200 milliseconds is considered good by Google; over 500 milliseconds is considered poor.
- It measures all relevant interactions across the page lifespan, not just the first interaction, giving a fuller picture than FID.
- It is influenced by heavy JavaScript, long tasks that block the main thread, and inefficient event handling.
Practical Example
A menu that responds instantly to a click has a good INP, while a form that freezes for a few hundred milliseconds after a user presses a button has a poor INP.
Why It Matters
A high INP signals a page that feels slow or unresponsive, negatively affecting user experience and Core Web Vitals evaluation.
FAQ
Is INP the same metric as FID?
No, INP replaced FID in 2024, offering a fuller measurement of responsiveness across the entire visit, not just the first interaction.
How do I reduce INP on a page?
By reducing JavaScript that blocks the main thread, breaking up long tasks, and optimizing event handling.