INP · Responsiveness
Interaction to Next Paint: how long the page takes to respond to a tap, click or key press.
INP verdict
v1.2.8 vs v1.2.7 · / · mobileNowv1.2.7
Improved
Responsiveness got 81ms faster (−48.1%). A change only counts when it is at least 5% and at least 20ms. Here that means 20ms, so this one does.
faster−20ms · too small to count · +20msslower
Now · v1.2.8
87ms
Good
v1.2.7167msChange−81msGood up to200ms
Visits measured
139
on mobile, enough for a verdict
v1.2.7 · mobile233 / 30
v1.2.8 · mobile139 / 30
v1.2.8 · desktop9 / 30
Where visits landed
share of visits in each rangev1.2.785%15%
v1.2.899%
Good ≤ 200msNeeds improvementPoor > 500ms
More visits in the good range than on v1.2.7 (99% against 85%). Nearly all 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 | 57 · 31% | 240ms |
| shop.example.com/_next/static/chunks/app/layout.js | 40 · 22% | 210ms |
“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.8 vs v1.2.7 · mobile · pages need 30 visits on both sidesPageVisitsv1.2.7v1.2.8ChangeVerdict
139167ms87ms−48.1%Improved
100182ms118ms−35.2%Improved
119191ms124ms−35.2%Improved
40164ms106ms−35.2%Improved