Total Blocking Time (lab)

Total Blocking Time on the lab crawl.

Field data PhoneDesktopAll Scope All sites October 2026 edition · All devices 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.

18ms
on the typical site
half of sites sit at or below
185ms
1 in 4 sites exceed this
the top quarter
6.4s
the heaviest 1%
the long tail
188,458
sites measured
all-device field data

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

The State of Web Vitals · October 2026 · 193,102 sites · all devices field datacorewebvitals.io/state-of-cwv
2

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

0ms 63ms 125ms 188ms 250ms
200ms
0 39096 78192
0 0.01–0.038 0.038–0.141 0.141–0.532 0.532–2 2–7.53 7.53–28.3 28.3–107 107–401 401–1507 1507–5668 >p98
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · October 2026 · 193,102 sites · all devices field datacorewebvitals.io/state-of-cwv
3

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

Total Blocking Time (lab)SitesPassing INPINP
0 78,192 95% 81ms
0.01–0.038 22 94% 80ms
0.038–0.141 156 95% 84ms
0.141–0.532 443 97% 86ms
0.532–2 1,726 97% 84ms
2–7.53 5,827 97% 84ms
7.53–28.3 14,192 96% 86ms
28.3–107 27,625 95% 87ms
107–401 30,185 95% 91ms
401–1507 20,265 94% 95ms
1507–5668 7,619 93% 98ms
>p98 2,206 92% 101ms
Good Needs Improvement Poor Faded rows: under 100 sites

Total Blocking Time (lab) 18ms. p75 185ms. p99 6.4s. At the low end (0ms): INP 81ms. At the high end (>p98): INP 101ms. computed

The State of Web Vitals · October 2026 · 193,102 sites · all devices 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: 95% at one end, 92% 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, 88% of sites pass it. Where it is high, 70% do.

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