The State of Web Vitals

INP distribution

How INP is distributed across real-user data, plus pass-rate breakdown.

Field data PhoneDesktopAll Scope All sites Q1 2026 edition · All devices field outcomes
1

At a glance the headline numbers for INP distribution

How INP is distributed across real-user data, plus pass-rate breakdown.

110ms
INP (p75)
94.8% good
86ms
INP (median)
334ms
INP (p99)
Long tail
The State of Web Vitals · Q1 2026 · 94,910 sites · all devices field datacorewebvitals.io/state-of-cwv
2

INP Distribution page loads across good, needs improvement and poor

0 6,925 13,850 20,774 27,699
p50 = 86ms
p75 = 110ms
p90 = 153ms
p99 = 334ms
0–25 25–50 50–75 75–100 100–125 125–150 150–175 175–200 200–225 225–250 250–275 275–300 300–325 325–350 350–375 375–400 400+
Good (≤200ms) Needs improvement Poor (>500ms) Percentile markers Total: 73,315 sites

INP 86ms. p75 110ms. p99 334ms. 94.8% pass.

The State of Web Vitals · Q1 2026 · 94,910 sites · all devices field datacorewebvitals.io/state-of-cwv
3

INP Pass Rates share per category

INP
94.8%
0.4%
Good Needs Improvement Poor

INP passes on 94.8% of sites. 4.8% need improvement, 0.4% fail.

The State of Web Vitals · Q1 2026 · 94,910 sites · all devices field datacorewebvitals.io/state-of-cwv
4

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.8% of sites have a good INP. The typical site sits at 110ms at the 75th percentile; the slowest 1% pass 334ms.

Go fix it Yield to the main thread → 14 methods to defer JavaScript → Reduce unused JavaScript → Limit analytics and tracking scripts →
Related signals CLS → LCP → FCP → TTFB → Chrome field data from 94,910 sites, representing millions of real page loads · How we measured