Interaction to Next Paint (INP) as FID Successor
You'll learn why Google is replacing First Input Delay (FID) with a more comprehensive responsiveness metric called Interaction to Next Paint (INP).
Understanding the Shift from FID to INP
While FID only measures the delay before processing starts on the very first user interaction, it misses crucial parts of the responsiveness story. Think of FID like measuring only how long it takes a waiter to acknowledge your order, but not how long until your food actually arrives at the table.
Interaction to Next Paint (INP) captures the complete interaction lifecycle: input delay + processing time + rendering the visual update. It measures this across all interactions during a page visit, not just the first one, and reports the worst (or near-worst) latency observed.
What INP Measures
INP tracks three phases of every interaction:
- Input delay – waiting for the main thread
- Processing time – executing event handlers
- Presentation delay – browser painting the update
The metric considers clicks, taps, and keyboard presses throughout the entire session, giving a realistic picture of actual user experience rather than a single moment.
Why This Matters
Many sites pass FID easily (the first click is often fast) but deliver sluggish interactions afterward—especially in complex SPAs with heavy JavaScript. INP catches these real-world slowdowns that FID missed. Google officially made INP a Core Web Vital in March 2024, replacing FID.
Good INP Thresholds
- Good: ≤200ms
- Needs improvement: 200-500ms
- Poor: >500ms
Key Takeaway: INP replaces FID by measuring the entire interaction cycle across all user inputs, providing a more complete and accurate picture of page responsiveness throughout the user's visit.