Blocking frame breakdown

The blocking animation frame behind that interaction: script, forced reflow, style/layout, other (lab).

Field data PhoneDesktopAll Scope All sites Q1 2026 edition · All devices field outcomes
Metric LCP INP CLS
1

At a glance the headline numbers for Blocking frame breakdown

The blocking animation frame behind that interaction: script, forced reflow, style/layout, other (lab).

79ms
Median INP stack
the measures at p50
92%
Biggest: Script ms
73ms of the stack
121ms
Headroom at p50
vs the 200ms target
+0.33
Strongest correlation
Other ms vs INP (Spearman)

Script accounts for 73ms of the typical blocking frame.

The State of Web Vitals · Q1 2026 · 94,910 sites · all devices field datacorewebvitals.io/state-of-cwv
2

Where the milliseconds go the phases at the median, against the budget

200ms target
Script ms 73ms Forced reflow ms 0ms Style layout ms 6ms Other ms 0ms

At the median the whole stack uses 79ms, inside the 200ms INP budget. The biggest piece is Script ms at 73ms. computed

The State of Web Vitals · Q1 2026 · 94,910 sites · all devices field datacorewebvitals.io/state-of-cwv
3

Passing LCP per phase the share of sites passing, by how long each phase takes

100%75%50%25%
Script ms Forced reflow ms Style layout ms Other ms

Each line is one phase: left = sites where it is quick, right = sites where it drags (buckets, short to long). The steeper the fall, the more that phase decides LCP.

Forced reflow ms falls hardest: from its fastest to its slowest bucket the LCP pass rate drops 19 points, down to 65%. computed

The State of Web Vitals · Q1 2026 · 94,910 sites · all devices field datacorewebvitals.io/state-of-cwv
4

The 4 distributions how each phase spreads across sites - color is the share passing in that range

Script ms p50 73ms · p75 123ms
0>p98
Forced reflow ms p50 0ms · p75 21ms
0>p98
Style layout ms p50 6ms · p75 23ms
0>p98
Other ms p50 0ms · p75 0ms
0>p98
mostly passing tipping mostly failing

Script ms stays green across its whole range: it never decides LCP. Forced reflow ms turns red in its tail - the failing sites live there. computed

The State of Web Vitals · Q1 2026 · 94,910 sites · all devices field datacorewebvitals.io/state-of-cwv
5

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, 92% at the other. This signal does not separate passing sites from failing ones.

Related signals Interaction invoker types → Yielding strategy → CSS hints → INP phase breakdown → Chrome field data from 94,910 sites, representing millions of real page loads · How we measured