Total Blocking Time (lab)

Total Blocking Time on the lab crawl.

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

At a glance the headline numbers for Total Blocking Time (lab)

Total Blocking Time on the lab crawl.

19ms
on the typical site
half of sites sit at or below
190ms
1 in 4 sites exceed this
the top quarter
7.0s
the heaviest 1%
the long tail
191,935
sites measured
desktop field data

The typical site blocks the main thread for 19ms during the lab load.

The State of Web Vitals · October 2026 · 196,579 sites · desktop field datacorewebvitals.io/state-of-cwv
2

Distribution & median CLS site count and median CLS at each level of total Blocking Time (lab)

0.00 0.04 0.08 0.11 0.15
0.1
0 39431 78861
0 0.01–0.038 0.038–0.144 0.144–0.545 0.545–2.07 2.07–7.84 7.84–29.7 29.7–113 113–427 427–1619 1619–6139 >p98
Good (≤0.1) Needs improvement Poor (>0.25) Site count
The State of Web Vitals · October 2026 · 196,579 sites · desktop field datacorewebvitals.io/state-of-cwv
3

Passing CLS by total Blocking Time (lab) which level passes the CLS most often

Total Blocking Time (lab)SitesPassing CLSCLS
0 78,861 82% 0.02
0.038–0.144 157 76% 0.02
0.144–0.545 455 81% 0.02
0.545–2.07 1,807 81% 0.02
2.07–7.84 6,096 79% 0.03
7.84–29.7 14,949 78% 0.03
29.7–113 28,814 76% 0.03
113–427 30,745 75% 0.04
427–1619 20,216 75% 0.04
1619–6139 7,551 73% 0.04
>p98 2,262 72% 0.04
Good Needs Improvement Poor Faded rows: under 100 sites

Total Blocking Time (lab) 19ms. p75 190ms. p99 7.0s. At the low end (0ms): CLS 0.02. At the high end (>p98): CLS 0.04. computed

The State of Web Vitals · October 2026 · 196,579 sites · desktop field datacorewebvitals.io/state-of-cwv
4

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, 78% do.

Related signals Main-thread CPU (lab) → Lab paint timeline → Document lifecycle (lab) → Chrome field data from 196,579 sites, representing millions of real page loads · How we measured