Interaction to Next Paint (INP)
You'll learn what INP measures and why it's replacing FID as the responsiveness Core Web Vital.
While First Input Delay (FID) only measured the first interaction on a page, Interaction to Next Paint (INP) takes a broader view: it measures the latency of all user interactions throughout the entire page visit.
What INP Actually Captures
INP tracks the time between when a user interacts with your page (clicks a button, taps a link, types in a field) and when the browser paints the next frame showing the result. It looks at every interaction during the session, then reports the worst (or near-worst) latency value.
Think of it like this: FID was a first-impression metric—did your page respond quickly the very first time someone clicked? INP is the full experience metric—was your page responsive every time someone interacted with it?
Why the Change?
Google realized that a fast first interaction doesn't guarantee a responsive experience. A page might respond instantly on first click but freeze for seconds on subsequent interactions. INP captures this reality better.
INP Thresholds
- Good: ≤200ms
- Needs Improvement: 200-500ms
- Poor: >500ms
The goal is keeping all interactions feeling instant and fluid, not just the first one.
Key Difference from FID
FID only measured input delay (how long until JavaScript could respond). INP measures the total latency including processing time and rendering the visual update—giving you the complete picture of responsiveness.
Key Takeaway: INP replaces FID by measuring the responsiveness of all page interactions, not just the first one, making it a more comprehensive metric for real-world user experience.