Script coverage (used vs unused)
Of the JavaScript shipped, how much actually ran during load (used vs unused bytes, Chrome coverage).
At a glance the headline numbers for Script coverage (used vs unused)
Of the JavaScript shipped, how much actually ran during load (used vs unused bytes, Chrome coverage).
893 KB of JavaScript on the typical page never ran during load.
Where the milliseconds go the phases at the median, against the budget
At the median the whole stack uses 2.0s - already past the 200ms INP budget. The biggest piece is Used kb at 1.1s. computed
Passing LCP per phase the share of sites passing, by how long each phase takes
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.
Unused kb falls hardest: from its fastest to its slowest bucket the LCP pass rate drops 17 points, down to 71%. computed
The 2 distributions how each phase spreads across sites - color is the share passing in that range
Used kb stays green across its whole range: it never decides LCP. Used kb turns red in its tail - the failing sites live there. computed
Why this matters for the Core Web Vitals, and where to start fixing it
Chrome's coverage data splits the JavaScript you ship into bytes that ran during load and bytes that did not. The unused half still cost the full price: downloaded, parsed and compiled on the main thread, all before doing nothing.
Unused JavaScript is usually whole features shipped everywhere: the checkout bundle on the blog, admin widgets for anonymous visitors. Code splitting per route is the structural fix. Deleting dead dependencies is the cheap one.
How does unused JavaScript affect the Core Web Vitals?
Passing INP barely moves across the range: 99% at one end, 95% at the other. This signal does not separate passing sites from failing ones.
Chrome field data from 94,910 sites, representing millions of real page loads. How we measured.