Interaction to Next Paint (INP)
23 quoted answers, each with its source
The short answer
Interaction to Next Paint became a stable Core Web Vital on March 12, 2024, replacing First Input Delay; Chrome deprecated support for First Input Delay and gave developers until September 9, 2024 to transition. As of September 2, 2025, web.dev states that an INP at or below 200 milliseconds means good responsiveness, above 500 milliseconds means poor responsiveness, and above 200 milliseconds and at or below 500 milliseconds means needs improvement, measured at the 75th percentile of field page loads segmented across mobile and desktop. INP calculation ignores one highest interaction for every 50 interactions, and the final value is the longest interaction observed after ignoring outliers; hovering, zooming, and scrolling are not observed, and a page can return no INP value. A seobeni.com article dated June 4, 2026 asserts that Core Web Vitals act as a tiebreaker between pages otherwise equal in relevance and authority, not a multiplier that overrides content quality.
Every part of this comes from the quotes below. How we write these.
What the rules actually say18
Quoted straight from the people who make or enforce the rules.
The web.dev article "Interaction to Next Paint (INP)" states that INP…
- is a stable Core Web Vital metric.
- assesses responsiveness using data from the Event Timing API.
1 quote from 1 source
Interaction to Next Paint (INP) is a stable Core Web Vital metric that assesses responsiveness using data from the Event Timing API.
The web.dev article "Interaction to Next Paint (INP)" states that an INP below or at 200 milliseconds means a page has good responsiveness.
1 quote from 1 source
An INP below or at 200 milliseconds means a page has good responsiveness.
The web.dev article "Interaction to Next Paint (INP)" states that an INP above 500 milliseconds means a page has poor responsiveness.
1 quote from 1 source
An INP above 500 milliseconds means a page has poor responsiveness.
The web.dev article 'Interaction to Next Paint (INP)' states that an INP above 200 milliseconds and below or at 500 milliseconds means a page's responsiveness needs improvement.
1 quote from 1 source
An INP above 200 milliseconds and below or at 500 milliseconds means a page's responsiveness needs improvement.
Interaction to Next Paint (INP) has a documented position that its good threshold is measured at the 75th percentile of page loads recorded in the field, segmented across mobile and desktop devices.
1 quote from 1 source
To ensure you're delivering user experiences with good responsiveness, a good threshold to measure is the 75th percentile of page loads recorded in the field, segmented across mobile and desktop devices:
The web.dev article "Interaction to Next Paint (INP)" states that INP calculation ignores one highest interaction for every 50 interactions.
1 quote from 1 source
To give a better measure of the actual responsiveness for pages with a high number of interactions, we ignore one highest interaction for every 50 interactions.
The web.dev article "Interaction to Next Paint (INP)" states that the final INP value for a page…
- is the longest interaction observed.
- ignores outliers.
1 quote from 1 source
The final INP value is the longest interaction observed, ignoring outliers.
The web.dev article "Interaction to Next Paint (INP)" states that hovering, zooming, and scrolling are not observed for the purposes of INP.
1 quote from 1 source
Users may also interact with the page in other ways, like hovering, zooming, or scrolling. These interactions are not observed for the purposes of INP.
The web.dev article "Interaction to Next Paint (INP)" states that measuring INP in JavaScript requires taking the 98th percentile across all interactions on page unload.
1 quote from 1 source
To measure INP in JavaScript, you need to measure event timings for all interactions, and then take the 98th percentile across all these interactions on page unload.
The web.dev article "Interaction to Next Paint (INP)" states that event entries below 104 milliseconds don't report by default using performance observers.
1 quote from 1 source
event entries below 104 milliseconds don't report by default using performance observers.
The web.dev article "Interaction to Next Paint (INP)" states that First Input Delay only measured the input delay of the first interaction on a page.
1 quote from 1 source
While both are responsiveness metrics, FID only measured the input delay of the first interaction on a page.
The web.dev article 'Interaction to Next Paint (INP)' states that it is possible for a page to return no INP value.
1 quote from 1 source
It's possible for a page to return no INP value.
The web.dev article "Interaction to Next Paint (INP)" states that the…
- Event Timing API does not report event entries for interactions occurring within iframes.
- INP metric reports event entries for interactions occurring within iframes.
1 quote from 1 source
The API does not report event entries for interactions that occur within iframes but the metric does as they are part of the user experience of the page.
A web.dev blog post announced that Interaction to Next Paint is…
- now a stable Core Web Vital metric.
- replacing First Input Delay.
1 quote from 1 source
Interaction to Next Paint is now a stable Core Web Vital metric, replacing First Input Delay.
Measured finding1
Something someone actually measured, with the method attached.
The web.dev article "Interaction to Next Paint (INP)" states that Chrome usage data shows 90% of a user's time on a page is spent after it loads.
1 quote from 1 source
Chrome usage data shows that 90% of a user's time on a page is spent after it loads
Changed on2
A dated change. This is where advice quietly stops being true.
A web.dev blog post stated that…
- developers would have until September 9, 2024 to transition over to INP.
- Chrome was officially deprecating support for First Input Delay.
1 quote from 1 source
Now that INP has replaced FID as a Core Web Vital metric, Chrome is officially deprecating support for FID. What this means is that Chrome tools will no longer guarantee FID availability and developers will have until September 9, 2024 to transition over to INP.
Often said, but we could not find it in the rules2
Lots of people say this. We went looking for an official source that backs it up and could not find one, so treat it as something people repeat rather than something settled.
The seobeni.com article asserts, regarding Interaction to Next Paint (INP), that Core Web Vitals…
- act as a tiebreaker between pages that are otherwise equal in relevance and authority.
- are not a multiplier that overrides content quality.
1 quote from 1 source
Core Web Vitals are a confirmed Google ranking signal that measure three dimensions of page experience: loading speed (LCP), interactivity (INP), and visual stability (CLS). They act as a tiebreaker between pages that are otherwise equal in relevance and authority — not a multiplier that overrides content quality.