INP (Interaction to Next Paint)

Interaction to Next Paint (INP) measures how quickly a page visually responds to clicks, taps and key presses throughout a visit. It replaced FID as a Core Web Vital in March 2024; a good INP is 200 milliseconds or less.

Interaction to Next Paint is the Core Web Vital for responsiveness. Every time a user clicks a button, taps a menu or types in a field, the browser has to run the related code and then paint the result on screen. INP measures how long that takes, from the interaction until the next frame is shown.

INP replaced FID. Until March 2024, Google used First Input Delay. FID only measured the delay before the browser could start handling the very first interaction, and almost every site passed it. INP looks at all interactions during the whole visit and includes the time to process them and update the screen, so it catches problems FID missed.

How the value is calculated. The browser records clicks, taps and keyboard input; scrolling and hovering do not count. For each visit, INP reports one of the slowest interactions. On pages with many interactions, a small number of extreme outliers are ignored. Google then takes the 75th percentile across all visits. Good is 200 milliseconds or less, needs improvement is up to 500 milliseconds, and poor is more than 500 milliseconds.

Three phases of an interaction:

  1. Input delay: the browser is busy with other work, such as a long JavaScript task, and cannot start handling the event yet.
  2. Processing duration: the event handlers run.
  3. Presentation delay: the browser recalculates styles and layout and paints the next frame.

What usually causes poor INP:

  • Long tasks on the main thread, often from large JavaScript bundles, tag managers loaded with many tags, ad scripts and chat widgets.
  • Heavy event handlers that do all their work before giving the browser a chance to paint.
  • Very large DOM sizes, which make every style and layout recalculation slower.
  • Client-side rendering frameworks that re-render big parts of the page after small interactions.

How to improve it:

  • Break long tasks into smaller chunks and yield back to the main thread, so the browser can respond in between.
  • Show visual feedback first (open the menu, show a spinner) and do the heavier work afterwards.
  • Remove or delay third-party scripts that are not needed for the first interaction.
  • Keep the DOM lean and avoid layout thrashing in scripts.

Measuring INP. Because INP needs real interactions, lab tests cannot report it. Use the field data in Google Search Console and PageSpeed Insights, or collect it yourself with the web-vitals library. In Chrome DevTools, the Performance panel shows interaction timings while you click through a page, and Total Blocking Time in Lighthouse is a useful lab proxy.

INP problems are especially common on mobile devices with slower processors, which is exactly how most visitors browse. Testing on a mid-range phone gives a far more realistic picture than a fast laptop.

Questions about INP (Interaction to Next Paint)

What is a good INP score?

200 milliseconds or less at the 75th percentile of visits. Between 200 and 500 milliseconds needs improvement, and above 500 milliseconds is poor.

When did INP replace FID?

In March 2024. Since then INP has been the official responsiveness metric in Core Web Vitals, and FID is no longer reported in Google's tools.

Why does Lighthouse not show INP?

INP needs real user interactions, which a lab test does not have. Use field data from Search Console or PageSpeed Insights, and Total Blocking Time as a lab indicator.

Related terms