Interaction to Next Paint (INP) Definition
Interaction to Next Paint (INP) is a web performance metric that measures how quickly a page responds visually to user interactions: clicks, taps and key presses. It observes interactions throughout the visit and reports a value close to the slowest one.
INP became a Core Web Vital on March 12, 2024, replacing First Input Delay (FID). A good INP is 200 milliseconds or less.
What Is Interaction to Next Paint?
When a visitor taps a menu button, opens an accordion or adds a product to the cart, they expect an immediate visual reaction. INP measures the time between the interaction and the next frame painted on screen, the moment the visitor sees that something happened.
Unlike its predecessor FID, which only measured the delay before the first interaction started being processed, INP covers all clicks, taps and keyboard interactions during the visit and includes the whole response time. Hovering and scrolling are not counted.
- INP Thresholds
- The Three Phases of an Interaction
- Why INP Matters for SEO
- Common Causes of a Poor INP
- How to Improve INP
INP Thresholds
| INP | Rating |
|---|---|
| 200 milliseconds or less | Good |
| Between 200 and 500 milliseconds | Needs improvement |
| More than 500 milliseconds | Poor |
As with the other Core Web Vitals, web.dev recommends meeting the threshold at the 75th percentile of page loads recorded in the field, separately on mobile and desktop.
The Three Phases of an Interaction
- Input delay: the time before the browser can start handling the interaction, often because the main thread is busy with other JavaScript.
- Processing duration: the time spent running the event handlers triggered by the interaction.
- Presentation delay: the time needed to recalculate the layout and paint the next frame.
Improving INP means reducing whichever phase is the longest for the slow interactions on your pages.
Why INP Matters for SEO
- Core Web Vitals: INP is one of the three metrics Google uses for page experience, alongside LCP and CLS. Google presents page experience as one factor among many.
- Perceived quality: a page that freezes after a tap feels broken; visitors tap again, give up or lose trust.
- Conversions: slow menus, forms and buttons directly affect calls, bookings and sales.
- Mobile: less powerful phones run JavaScript more slowly, so INP problems are often worse on mobile.
Common Causes of a Poor INP
- Too much JavaScript: large bundles, many plugins and third-party scripts keep the main thread busy.
- Long tasks: scripts that run for more than 50 milliseconds without pausing block interactions.
- Heavy event handlers: complex work done immediately on click instead of after the visual update.
- Third-party scripts: chat widgets, tracking tags, advertising and consent tools.
- Large DOM: pages with thousands of elements take longer to update after each interaction.
How to Improve INP
- Remove unnecessary JavaScript: unused plugins, duplicate libraries and scripts loaded on pages that do not need them.
- Break up long tasks so the browser can respond to interactions between them.
- Show feedback first: update the interface immediately, then do heavier work afterwards.
- Audit third-party scripts and load non-essential ones later.
- Reduce DOM size, for example by simplifying page builder layouts and removing hidden duplicate sections.
- Avoid layout recalculations triggered repeatedly by scripts.
How to Measure INP
INP requires real interactions, so field data is essential: the Core Web Vitals report in Google Search Console and the field data of PageSpeed Insights, based on the Chrome User Experience Report. Lab tools such as Lighthouse cannot measure INP directly without interactions; they report Total Blocking Time, a related lab metric that signals main-thread blocking. Chrome DevTools can record real interactions and show the phases of each one.
Example: A Hair Salon Booking Page
A hair salon in Manchester notices in Search Console that its booking page has a poor INP on mobile. Recording the page in DevTools shows that tapping a time slot triggers a long script from the booking widget, plus a chat widget and three tracking tags competing for the main thread. The chat widget is loaded only after the first interaction, two unused tracking tags are removed, and the booking widget is updated to a lighter version. Taps on time slots now respond almost instantly, and the page’s field INP improves over the following weeks.
Common Misconceptions
- “A good Lighthouse score means a good INP”: Lighthouse does not measure INP in a standard test; only field data does.
- “INP is the same as FID”: FID measured only the input delay of the first interaction; INP measures the full response of all interactions.
- “Only big web apps have INP problems”: small business sites with many plugins and widgets often do too.
INP, FID and Total Blocking Time
| Metric | What it measures |
|---|---|
| INP | The full time from interaction to next paint, for all clicks, taps and key presses of a visit. A Core Web Vital since March 2024, measured in the field. |
| FID (retired) | Only the input delay of the first interaction. Replaced by INP because it missed most of the slow responses visitors experience. |
| Total Blocking Time | A lab metric: the time the main thread was blocked by long tasks during loading. Useful to predict INP problems in Lighthouse. |
INP on WordPress Sites
On WordPress, INP problems usually come from the accumulation of plugins that each add JavaScript to every page: sliders, popups, chat, analytics, social feeds, page builder animations and consent tools. Start by listing the scripts loaded on your most visited pages and removing those that bring no value there. Settings that delay JavaScript until the first interaction can help loading metrics, but they can also make the first tap slower, because all delayed scripts start at that moment. Always test real taps on a mobile phone after changing these settings, not only the lab score.
Interaction to Next Paint: Key Takeaways
INP measures how fast a page visually responds to clicks, taps and key presses throughout a visit. It replaced FID as a Core Web Vital in March 2024, and a good value is 200 milliseconds or less. Reduce JavaScript, break up long tasks, give visual feedback first, control third-party scripts and keep the DOM light. Measure with field data, since INP depends on real interactions.
From theory to responsive pages
Knowing what INP measures is the first step. The next is finding which scripts slow down the reactions of your key pages.
- An action plan adapted to your situation
- Clear explanations, no needless jargon
- Direct application to your sector
From diagnosis to results, step by step
Here is how I handle inp issues on client sites, and what my clients say about my work.
What Is Interaction to Next Paint?
When a visitor taps a menu button, opens an accordion or adds a product to the cart, they expect an immediate visual reaction. INP measures the time between the…
INP Thresholds
INPRating200 milliseconds or lessGoodBetween 200 and 500 millisecondsNeeds improvementMore than 500 millisecondsPoor
As with the other Core Web Vitals, web.dev…
The Three Phases of an Interaction
Input delay: the time before the browser can start handling the interaction, often because the main thread is busy with other JavaScript.Processing duration: the time…
FAQ: INP
What is Interaction to Next Paint?
A metric measuring how long a page takes to visually respond to user interactions such as clicks, taps and key presses.
What is a good INP score?
200 milliseconds or less at the 75th percentile of page loads. More than 500 milliseconds is considered poor.
When did INP replace FID?
INP became a Core Web Vital on March 12, 2024, replacing First Input Delay.
What causes a poor INP?
Mostly heavy JavaScript: long tasks, many plugins and third-party scripts, heavy event handlers and very large pages.
Can Lighthouse measure INP?
Not in a standard load test, since INP needs real interactions. Use field data, and Total Blocking Time as a lab indicator.
Does scrolling count in INP?
No. INP counts clicks, taps and keyboard interactions, not scrolling or hovering.
INP Resources:
Do you want to work with me?
I am SeoYass, an SEO expert with over 17 years of experience. I have worked with small and medium-sized businesses, successfully completing more than 350 projects.
Passionate about local SEO, I continue to learn and refine my strategies to deliver the best performance for my clients.

