At a glance the headline numbers for Total Blocking Time (lab)
Total Blocking Time on the lab crawl.
The typical site blocks the main thread for 16ms during the lab load.
Distribution & median INP site count and median INP at each level of total Blocking Time (lab)
Passing INP by total Blocking Time (lab) which level passes the INP most often
Total Blocking Time (lab) 16ms. p75 172ms. p99 6.5s. At the low end (0ms): INP 45ms. At the high end (>p98): INP 61ms. computed
Why this matters for the Core Web Vitals, and where to start fixing it
Total Blocking Time counts the parts of long tasks where a click would have waited. It is the lab stand-in for INP: a crawler does not click, so instead we measure how often the main thread was too busy to answer if someone had.
High TBT with good field INP usually means real visitors interact after the dust settles. The risk lives in the early click, the visitor who taps the menu while the tag pile is still booting. The fix list is the script list: less of it, later, in smaller pieces.
How does this affect the Core Web Vitals?
Passing INP barely moves across the range: 99% at one end, 98% at the other. This signal does not separate passing sites from failing ones.
The effect is bigger on LCP. Where the blocking time is low, 90% of sites pass it. Where it is high, 77% do.
Chrome field data from 189,915 sites, representing millions of real page loads. How we measured.