INP distribution
How INP is distributed across real-user data, plus pass-rate breakdown.
At a glance the headline numbers for INP distribution
How INP is distributed across real-user data, plus pass-rate breakdown.
94.7% of sites pass INP. The typical site's INP is 87ms. The worst 10% are above 153ms.
The INP distribution site count at each INP, from good to poor
The tallest bar is between 75ms and 100ms. 38% of sites are in that one range, 100ms under Google's 200ms limit. Half of all sites are at 87ms or less. The worst 10% are above 153ms and the worst 1% above 334ms. That is 3.8 times the typical site.
The INP pass rate the share of sites that are good, needs improvement and poor
94.7% of sites pass INP. 4.8% are in the needs improvement band, between 200ms and 500ms. 0.4% are poor, above 500ms. A miss is usually needs improvement, not poor.
Why this matters for the Core Web Vitals, and where to start fixing it
Interaction to Next Paint measures how quickly the page responds when someone taps, clicks or types. It is the interactivity metric, and it is the one most sites struggle with, because it is decided by JavaScript. When the main thread is busy parsing and running scripts, it cannot respond to the interaction, and the visitor waits. Third-party tags and heavy frameworks are the usual cause.
Start by finding what runs on the main thread and cutting it down. Remove the scripts you do not need, defer the ones you do, and break up the long tasks that block input. Yielding to the main thread between chunks of work lets the browser handle interactions in between, instead of making the user wait for a long task to finish.
How are sites doing on INP?
94.7% of sites have a good INP. The typical site sits at 110ms at the 75th percentile; the slowest 1% pass 334ms.
Chrome field data from 189,915 sites, representing millions of real page loads. How we measured.