How to fix Interaction to Next Paint (INP)
Speed1 min readFixes 2 checks inp, crux-inp
INP measures how quickly the page reacts when a visitor taps or clicks. Google wants it under 200 ms. Long JavaScript tasks and heavy third-party scripts are the usual cause.
Step by step, with screenshots: Core Web Vitals for e-commerce: product and category pages →
Check your own site
Runs these 2 checks and the other 185, free, in about 45 seconds.
What a passing site looks like
- Interaction to Next Paint: passesfail · −10 ptseffort M
- Real-user Interaction to Next Paint: passesinfo onlyeffort M
1. Interaction to Next Paint
Why it matters. INP measures how quickly the page reacts when someone taps or clicks. Lab tools cannot simulate it, so this comes from real Chrome users; slow responses feel like a frozen page.
How to fix it.
- Break up long JavaScript tasks and defer third-party scripts so the main thread is free when people interact.
- Respond to input visually first (a pressed state, a spinner), then do the heavy work.
- Reduce DOM size and avoid layout-heavy work inside click handlers.
2. Real-user Interaction to Next Paint
Why it matters. INP is how long the page takes to visibly react to taps and clicks, measured on real Chrome users over the last 28 days. Google's threshold for "good" is 200 ms.
How to fix it.
- Cut long JavaScript tasks and heavy third-party scripts; see the INP finding above.