Interaction and the next frame
- Click / tap / key
- Event processing
- Next paint
How it works
Reduce heavy main-thread work and inspect actual problematic interactions.
Example
Example: A catalog filter responds slowly because of extensive synchronous processing.
Common mistakes
One fast lab click does not describe every real interaction.
How can you check this in practice?
Test clicks, taps and keys in actual page workflows. In a performance trace, separate input delay, processing and time to the next paint. Long JavaScript tasks can delay responses even after a fast initial load; the good threshold is ≤200 ms.
Distinctions and limitations
INP assesses responsiveness throughout a visit, not only the first click. One lab scenario can miss a menu or form problem. An absence of measured interactions does not establish good INP.
Official sources
Editorial responsibility: Martin Zhelyazkov · Founder of Z-Consult
Updated: 05/11/2026
For a correction or question: office@z-consult.bg
