What Is INP (Interaction to Next Paint)?

4 min readJune 22, 2026

Interaction to Next Paint (INP) is the Core Web Vital metric for responsiveness. It observes the latency of all the interactions a visitor makes during a page visit and reports a single value, measured in milliseconds, that all or nearly all of those interactions came in under. An interaction is something like clicking a button, tapping a menu, or pressing a key, and INP captures the full delay from that action to the moment the browser paints the next visual update on screen. Google scores INP at the 75th percentile of real user interactions, which means 75 percent of your visitors need to experience interactions faster than the threshold. The grades are 200 ms or less for good, 200 to 500 ms for needs improvement, and above 500 ms for poor. INP became a stable Core Web Vital in March 2024, replacing First Input Delay (FID), and it can only be measured accurately with field data from real users, not lab tools alone.

Why it exists

INP exists because First Input Delay, the metric it replaced, only measured the wait before the browser started handling the very first interaction on a page. It said nothing about how long that handling took, and it ignored every interaction after the first. A page could score a perfect FID and still feel sluggish the moment a user opened a cart drawer or filtered a list. INP closes that gap by measuring the whole interaction lifecycle across the entire visit, so the score reflects how the page actually feels to use, not just how it greets the first click.

Google set the good threshold at 200 ms by balancing two things: human perception research showing that visual feedback within roughly 100 ms feels instant, and what is realistically achievable across the web, including lower end mobile devices. The same threshold applies to every device because a user's expectation of a responsive page does not change based on the hardware in their hand.

How it works at Pineido

Every interaction INP measures breaks into three phases. Input delay is the time from the user's action until the event handler can start running, which grows when the main thread is busy with other work. Processing time is how long the event handler code itself takes to run. Presentation delay is the gap between the handler finishing and the browser painting the updated screen. INP reports the worst, or close to worst, interaction from the visit, so a single slow moment can drag the whole score down.

Because JavaScript runs on a single main thread and tasks run to completion, a long task blocks the browser from responding to anything else, including a waiting click. That is why the most common fix is yielding: breaking long tasks into smaller pieces so the browser can handle user input between them. Modern code uses scheduler.yield() where available, with a setTimeout fallback for older browsers. Beyond yielding, teams reduce third party script load, move heavy work off the main thread, keep event handlers lightweight, and avoid forced reflows that bloat presentation delay. You diagnose which phase is the culprit using the Interactions track in Chrome DevTools and confirm fixes with real user monitoring.

Common misconceptions

  1. INP is not the same as FID. FID only measured the delay before the first interaction was handled, while INP measures the full input, processing, and presentation delay across every interaction in the visit.

  2. A good Lighthouse or PageSpeed lab score does not guarantee a good INP. INP is a field metric scored from real user interactions at the 75th percentile, so lab tools can only approximate it.

  3. Optimizing your own JavaScript does not always fix INP. Third party scripts, hydration, rendering work, and background tasks can all keep interactions slow even after your code is lean.

  4. INP is not measured per interaction in your final score. It reports a single near worst value for the whole visit, so one heavy interaction can fail the page even if most are fast.

  5. Faster INP is not just about reducing total JavaScript size. The phase that hurts you, input delay versus processing versus presentation, decides which fix actually moves the number.

Frequently asked questions

What is a good INP score?

An INP of 200 ms or less is good, between 200 and 500 ms needs improvement, and above 500 ms is poor. Google measures this at the 75th percentile of real user interactions, so 75 percent of your visitors need interactions faster than 200 ms for the page to pass.

How is INP different from FID?

First Input Delay only measured the wait before the browser began handling the first interaction, and it ignored everything after. INP measures the full lifecycle of every interaction during the visit, including input delay, processing time, and presentation delay, then reports the near worst result. INP replaced FID as a Core Web Vital in March 2024.

Why is INP harder to fix than LCP and CLS?

CLS usually comes down to reserving space in HTML and CSS, and LCP responds to infrastructure changes like a CDN or server side rendering. INP almost always requires JavaScript refactoring across three separate phases of latency, plus real user data to find the problem. That is why it remains the most commonly failed Core Web Vital.

How do I improve INP?

Break long tasks into smaller pieces so the browser can respond to input between them, using scheduler.yield() with a setTimeout fallback. Reduce the load from third party scripts, keep event handlers lightweight, move heavy work off the main thread, and avoid forced reflows. Use the Interactions track in Chrome DevTools to find the slow phase, then verify with real user monitoring.

What are the three phases of an INP interaction?

Input delay is the wait from the user's action until the event handler starts. Processing time is how long the handler code runs. Presentation delay is the gap before the browser paints the visual update. Diagnosing which phase is slow tells you which fix will actually lower the score.

Can I measure INP with lab tools alone?

No. INP can only be measured accurately with field data that captures real user interactions, such as the Chrome User Experience Report shown in PageSpeed Insights or your own real user monitoring. Lab tools like Lighthouse estimate related signals such as Total Blocking Time, but they cannot reproduce the actual interactions your visitors make.

Get in touch

Tell us what you want built. We tell you where to start and what it takes.

One conversation. A clear plan.

You leave with

  1. A clear plan for the build
  2. An honest answer on cost and time
  3. Concrete next steps

ByFounder and Imaginator

Pineido, based in Strumica, North Macedonia, is a software company that builds websites, online shops, web and mobile apps, business automation and AI for companies at home and abroad. Work ships in 30-day sprints at a fixed price, and the client owns the code.

Published