INP · Responsiveness
Interaction to Next Paint: how long the page takes to respond to a tap, click or key press.
INP verdict
v1.2.2 vs v1.2.1 · / · mobileRegressed
Responsiveness got 31ms slower (+22.8%). A change only counts when it is at least 5% and at least 20ms. Here that means 20ms, so this one does.
Now · v1.2.2
169ms
Visits measured
237
on mobile, enough for a verdict
Where visits landed
share of visits in each rangeFewer visits in the good range than on v1.2.1 (84% against 92%). Four in five mobile visits respond in 200ms or less.
Moved in the same release
Things that can slow responses. A place to look, not a cause.
Changes in this release
2 commits since v1.2.1 · newest first
- Add reviews carouselPriya N.0f8d2b4
- Show star ratings on product cardsMaya R.c90b4d1
Listed because they shipped in this release, as a place to start looking. CodeGecko doesn’t know which commit, if any, caused a change.
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 | 109 · 30% | 260ms |
| Inline script | 51 · 14% | 180ms |
“New” means it never led on the previous release. Inline scripts are grouped together, and query strings are never collected.