The State of Web Vitals

WordPress Total Blocking Time (TBT) and the Core Web Vitals

30.0% of audited sites (19,004) record 0ms of lab Total Blocking Time (98% good field INP, 80ms median) and 37.0% stay within 1 to 200ms (98% good INP), while the 17.1% exceeding 600ms TBT drop to 97% good INP (94ms median).

Field data PhoneDesktopAll Scope All sites October 2026 edition · All devices field outcomes · WordPress sites only
WordPress Scoped to 63,295 sites out of 203,892 analyzed (cms) Compare with all sites →

30.0% of WordPress sites have no lab Total Blocking Time (TBT). Of the 70.0% that do, 53% use 1 to 200ms TBT, and 98% of those sites have a good INP, against 98% of all WordPress sites.

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
1

INP pass rate

Sites with 1 to 200ms TBT lab Total Blocking Time (TBT) have a good INP most often: 98%, against 98% of all WordPress sites. Sites with over 600ms TBT Total Blocking Time have it least often, at 97%.

SitesGood, needs improvement, poor INPMedian
All WordPress sites60,85598%86ms
1ms to 200ms TBT (Good) 37.0%22,50098%85ms
0ms TBT (Zero long tasks) 30.0%18,10598%80ms
201ms to 600ms TBT (Needs Improvement) 15.9%9,76298%89ms
Over 600ms TBT (Poor) 17.1%10,48897%94ms
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
2

Lab Total Blocking Time (TBT) usage

70.0% of WordPress sites use lab Total Blocking Time (TBT), and 53% of those use 1 to 200ms TBT.

All WordPress sites 63,295 sites
0ms TBT (Zero long tasks) 30.0% Lab Total Blocking Time (TBT) 70.0%
Sites with lab Total Blocking Time (TBT) 44,291 sites
1ms to 200ms TBT (Good) 52.8% Over 600ms TBT (Poor) 24.4% 201ms to 600ms TBT (Needs Improvement) 22.8%
1ms to 200ms TBT (Good) 52.8% Over 600ms TBT (Poor) 24.4% 201ms to 600ms TBT (Needs Improvement) 22.8%
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
3

Lab Total Blocking Time (TBT) per framework

On jQuery, 37% of sites use 1 to 200ms TBT lab Total Blocking Time (TBT), and 98% of jQuery sites have a good INP, against 98% of all sites. On Vue, 36% of sites use 1 to 200ms TBT, and 97% of Vue sites have a good INP.

FrameworkLab Total Blocking Time (TBT) on its sitesGood INP
All WordPress sites 63,295 sites1ms to 200ms TBT (Good) 37%0ms TBT (Zero long tasks) 30%Over 600ms TBT (Poor) 17%201ms to 600ms TBT (Needs Improvement) 16%98%
React 2,233 sites1ms to 200ms TBT (Good) 35%Over 600ms TBT (Poor) 26%201ms to 600ms TBT (Needs Improvement) 21%0ms TBT (Zero long tasks) 18%98%
jQuery 60,314 sites1ms to 200ms TBT (Good) 37%0ms TBT (Zero long tasks) 29%Over 600ms TBT (Poor) 18%201ms to 600ms TBT (Needs Improvement) 16%98%
Vue 4,844 sites1ms to 200ms TBT (Good) 36%Over 600ms TBT (Poor) 23%0ms TBT (Zero long tasks) 21%201ms to 600ms TBT (Needs Improvement) 20%97%
Alpine 380 sites1ms to 200ms TBT (Good) 38%0ms TBT (Zero long tasks) 31%Over 600ms TBT (Poor) 17%201ms to 600ms TBT (Needs Improvement) 14%95%
1ms to 200ms TBT (Good) 0ms TBT (Zero long tasks) Over 600ms TBT (Poor) 201ms to 600ms TBT (Needs Improvement)
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
4

Total Blocking Time or the framework

Does the framework explain the lab Total Blocking Time (TBT) difference?

On jQuery, 99% of sites with 1 to 200ms TBT lab Total Blocking Time (TBT) have a good INP, against 98% of jQuery sites with 0ms TBT. Within jQuery, sites with 1 to 200ms TBT and 0ms TBT have a good INP about equally often. On Vue, 98% of sites with 1 to 200ms TBT lab Total Blocking Time (TBT) have a good INP, against 97% of Vue sites with 0ms TBT. Within Vue, sites with 1 to 200ms TBT and 0ms TBT have a good INP about equally often.

How lab Total Blocking Time translates into field INP responsiveness

Total Blocking Time sums the blocking portion (anything past 50ms) of every long main-thread task during lab page load. Across 19,004 sites (30.0%) with 0ms TBT and 23,392 sites (37.0%) within 1 to 200ms TBT, 98% and 98% pass field INP (80ms and 85ms median). When lab TBT rises to 201 to 600ms (15.9%), good INP dips to 98% (89ms median), and past 600ms TBT (17.1%, 10,805 sites) good INP falls to 97% (94ms median).

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
5

Understanding Total Blocking Time (TBT)

Keep lab Total Blocking Time under 200ms by code-splitting large bundles, deferring non-critical third-party tags until after first interaction, and yielding to the main thread via scheduler.yield() between startup tasks. Across all audited sites, 37.0% sit at 1 to 200ms TBT (98% good INP) while 17.1% exceed 600ms (97% good INP).

Go fix it Yield to the main thread → 14 methods to defer JavaScript → Interaction to Next Paint →
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals Main-thread CPU (lab) → Lab paint timeline → Document lifecycle (lab) → By Arjen Karel · 63,295 crawled WordPress sites (60,855 with all devices Chrome field data, October 2026) · How we measured