Blocking frame breakdown
The blocking animation frame behind that interaction: script, forced reflow, style/layout, other (lab).
At a glance the headline numbers for Blocking frame breakdown
The blocking animation frame behind that interaction: script, forced reflow, style/layout, other (lab).
Script accounts for 73ms of the typical blocking frame.
Where the milliseconds go the phases at the median, against the budget
At the median the whole stack uses 79ms, inside the 200ms INP budget. The biggest piece is Script ms at 73ms, 92% of the total. computed
Why this matters for the Core Web Vitals, and where to start fixing it
The long animation frame behind a slow interaction splits into parts. Script time is JavaScript running. Style and layout time is the browser recomputing the page after changes. Forced reflow is the expensive special case: a script writes to the DOM, then reads a layout value back, and the browser must stop mid-script and lay out the page to answer.
The split decides the fix. Script time wants less work or yielding. Style and layout time wants a smaller scope: a smaller DOM, containment. Forced reflow wants reordered code: batch the reads first, then do the writes.
How does this affect the Core Web Vitals?
Passing INP barely moves across the range: 96% at one end, 93% at the other. This signal does not separate passing sites from failing ones.
Chrome field data from 189,915 sites, representing millions of real page loads. How we measured.