INP: The New Core Web Vitals Metric That Replaced FID
26/07/2026
In March 2024, Google replaced the old FID metric in Core Web Vitals with a new one — INP (Interaction to Next Paint). If you track site speed, this is a change you must understand because it directly affects your user-experience score.
What INP measures
INP measures how long a site takes to visually respond to a user interaction — a click, tap, or key press. Unlike FID, which measured only the first delay, INP looks at all interactions during the visit and reports roughly the worst one. It is a far more honest picture of real „sluggishness".
What counts as good
- Good: under 200 ms
- Needs improvement: 200–500 ms
- Poor: over 500 ms
Common causes of poor INP
The usual culprit is heavy JavaScript blocking the main thread: oversized bundles, third-party scripts (chat, analytics, ads), expensive event handlers, and long tasks that never let the browser respond.
How to fix it
Break long tasks into smaller chunks, defer or lazy-load non-essential scripts, remove redundant plugins and third-party scripts, and use caching so the server ships pages faster. Fast hosting with NVMe storage and good caching lowers the baseline load before JS even starts.
Measure INP with PageSpeed Insights or Search Console (Core Web Vitals report). If your server slows responses, see our plans and the SEO hosting guide — a faster base is the first step to a green INP.