Interaction invoker types
What kind of handler blocked the interaction: event listener, timer, promise reaction.
At a glance the headline numbers for Interaction invoker types
What kind of handler blocked the interaction: event listener, timer, promise reaction.
The interaction invoker types mix who uses what, and how fast each group loads
Interaction invoker types. On the fleet: 0.0% 0, 0.0% invoker, 0.0% sourcefunctionname. 0.0% of sites use at least one 0.
0 leads by count (0.0%) and by bytes (0.0%). computed
Passing INP per bucket every category and count level at once - color is the pass rate
Each row is a category, each column its own count bucket (few on the left, many on the right); the cell is the share of those sites passing INP.
No category moves the INP pass rate much, however many a site ships. computed
Few vs many - does quantity cost INP? the pass rate with few vs many of each category
Per category: the pass rate among pages with FEW of it (hollow ring) against pages with MANY (solid dot), worst trend first. Thin buckets are excluded from the endpoints.
More Event-listener costs the most: the INP pass rate falls from 99% with few to 98% with many. computed
Why this matters for the Core Web Vitals, and where to start fixing it
When an interaction lags, some piece of JavaScript held the main thread. This metric names the kind. An event listener means the click handler itself did too much. A timer means scheduled work got in the way, often a third-party script polling on setTimeout. A promise reaction means async work came back and ran in one long chunk.
The kind points at the owner. Slow event listeners are your code and your framework. Timer churn is usually the tag pile. Promise reactions are awaited work that needed breaking up. Identify the kind first, because the fix differs per kind.
How does this affect the Core Web Vitals?
The choice barely moves the INP: 99% pass at best, 97% at worst. This signal does not separate passing sites from failing ones.
The split is bigger on CLS. With Classic-script, 77% of sites pass it. With Resolve-promise, 66% do.
Chrome field data from 189,915 sites, representing millions of real page loads. How we measured.