Total Blocking Time (lab)

Total Blocking Time on the lab crawl.

Field data PhoneDesktopAll Scope All sites Q1 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.

20ms
on the typical site
half of sites sit at or below
189ms
1 in 4 sites exceed this
the top quarter
6.8s
the heaviest 1%
the long tail
94,910
sites measured
desktop field data

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

The State of Web Vitals · Q1 2026 · 94,910 sites · desktop 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 19195 38389
0 0.01–0.038 0.038–0.143 0.143–0.541 0.541–2.05 2.05–7.74 7.74–29.3 29.3–111 111–419 419–1585 1585–5994 >p98
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · Q1 2026 · 94,910 sites · desktop 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 38,389 99% 45ms
0.038–0.143 74 97% 50ms
0.143–0.541 227 99% 50ms
0.541–2.05 925 100% 48ms
2.05–7.74 3,124 99% 48ms
7.74–29.3 7,534 99% 49ms
29.3–111 14,344 99% 49ms
111–419 15,446 99% 52ms
419–1585 9,921 98% 56ms
1585–5994 3,783 98% 58ms
>p98 1,131 98% 60ms
Good Needs Improvement Poor Faded rows: under 100 sites

Total Blocking Time (lab) 20ms. p75 189ms. p99 6.8s. At the low end (0ms): INP 45ms. At the high end (>p98): INP 60ms. computed

The State of Web Vitals · Q1 2026 · 94,910 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 94,910 sites, representing millions of real page loads · How we measured