INP · Responsiveness
Interaction to Next Paint: how long the page takes to respond to a tap, click or key press.
INP verdict
v1.2.1 vs v1.2.0 · / · mobileNowv1.2.0
Unchanged
Responsiveness didn’t change. A change only counts when it is at least 5% and at least 20ms. Here that means 20ms, so this one doesn’t.
faster−20ms · too small to count · +20msslower
Now · v1.2.1
138ms
Good
v1.2.0138msChange0msGood up to200ms
Visits measured
165
on mobile, enough for a verdict
v1.2.0 · mobile216 / 30
v1.2.1 · mobile165 / 30
v1.2.1 · desktop59 / 30
Where visits landed
share of visits in each rangev1.2.092%
v1.2.192%
Good ≤ 200msNeeds improvementPoor > 500ms
Same shape as v1.2.0. Nine in ten mobile visits respond in 200ms or less.
Moved in the same release
Things that can slow responses. A place to look, not a cause.
Scripts behind long frames
The script that blocked longest on each visit with long frames · Mobile
| Script | Visits | Blocking p75 |
|---|---|---|
| www.googletagmanager.com/gtm.js | 76 · 30% | 260ms |
| Inline script | 35 · 14% | 180ms |
“New” means it never led on the previous release. Inline scripts are grouped together, and query strings are never collected.
INP across releases
Typical visit · each point is a deploy, ringed by its INP verdictGood ≤ 200ms
ImprovedRegressedUnchanged
INP by page
v1.2.1 vs v1.2.0 · mobile · pages need 30 visits on both sidesPageVisitsv1.2.0v1.2.1ChangeVerdict
165138ms138ms+0.0%Unchanged
118150ms150ms+0.0%Unchanged
141158ms158ms+0.0%Unchanged
47135ms135ms+0.0%Unchanged