The State of Web Vitals

WordPress main-thread task scheduling APIs and the Core Web Vitals

99.9% of audited sites (63,150) schedule tasks via setTimeout (97% good INP), 77.3% use requestAnimationFrame (97% good INP), 33.3% use requestIdleCallback (96% good INP), and 2.6% adopt modern scheduler.yield() (95% good INP, 97ms median).

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

99.9% of WordPress sites use setTimeout() main-thread scheduling API usage, and 97% of those sites have a good INP, against 97% of all WordPress sites.

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 36,524 with phone field data · 63,166 sites with main-thread scheduling API usageBy Arjen Karel · corewebvitals.io/state-of-cwv
1

INP pass rate

Sites with setTimeout() main-thread scheduling API usage have a good INP most often: 97%, against 97% of all WordPress sites. Sites with scheduler.yield() task scheduling have it least often, at 95%.

SitesGood, needs improvement, poor INPMedian
All WordPress sites36,52497%96ms
setTimeout() 99.9%36,44797%96ms
requestAnimationFrame() 77.3%28,27197%98ms
setInterval() 75.1%27,17796%99ms
requestIdleCallback() 33.3%12,01896%102ms
scheduler.yield() 2.6%98795%97ms
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 36,524 with phone field data · 63,166 sites with main-thread scheduling API usageBy Arjen Karel · corewebvitals.io/state-of-cwv
2

Main-thread scheduling API usage usage

SetTimeout() is the most used: 99.9% of WordPress sites.

Sites using each option (sites can use more than one) 63,166 sites
setTimeout() 99.9% requestAnimationFrame() 77.3% setInterval() 75.1% requestIdleCallback() 33.3%
setTimeout() 99.9% requestAnimationFrame() 77.3% setInterval() 75.1% requestIdleCallback() 33.3% scheduler.yield() 2.6%
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 36,524 with phone field data · 63,166 sites with main-thread scheduling API usageBy Arjen Karel · corewebvitals.io/state-of-cwv
3

Main-thread scheduling API usage per framework

Vue sets the main-thread scheduling API usage to setTimeout() on 100% of its sites, and 95% of Vue sites have a good INP, against 97% of all sites.

FrameworkMain-thread scheduling API usage on its sitesGood INP
WordPress sites with main-thread scheduling API usage 63,166 sitessetTimeout() 100%requestAnimationFrame() 77%setInterval() 75%requestIdleCallback() 33%97%
jQuery 60,246 sitessetTimeout() 100%requestAnimationFrame() 79%setInterval() 77%requestIdleCallback() 34%97%
React 2,228 sitessetTimeout() 100%requestAnimationFrame() 82%setInterval() 79%requestIdleCallback() 68%96%
Vue 4,844 sitessetTimeout() 100%requestAnimationFrame() 96%setInterval() 69%requestIdleCallback() 25%95%
Alpine 380 sitessetTimeout() 100%setInterval() 87%requestAnimationFrame() 81%requestIdleCallback() 49%88%
setTimeout() requestAnimationFrame() setInterval() requestIdleCallback() scheduler.yield()
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 36,524 with phone field data · 63,166 sites with main-thread scheduling API usageBy Arjen Karel · corewebvitals.io/state-of-cwv
4

Scheduling APIs or the framework

Does the framework explain the main-thread scheduling API usage difference?

Almost every site with setTimeout() main-thread scheduling API usage is a jQuery site, and almost every jQuery site has setTimeout() main-thread scheduling API usage, so the data can't tell setTimeout() main-thread scheduling API usage and jQuery apart. On Vue, 95% of sites with setTimeout() main-thread scheduling API usage have a good INP, against 95% of Vue sites with requestAnimationFrame(). Within Vue, sites with setTimeout() and requestAnimationFrame() have a good INP about equally often. On React, 96% of sites with setTimeout() main-thread scheduling API usage have a good INP, against 96% of React sites with requestAnimationFrame(). Within React, sites with setTimeout() and requestAnimationFrame() have a good INP about equally often.

How timer churn (setInterval) and yielding APIs affect input responsiveness

Nearly every site uses setTimeout() (99.9%, 97% good INP), while 75.1% run recurring setInterval() timers (96% good INP, 99ms median) and 77.3% use requestAnimationFrame() (97% good INP). For background work, 33.3% call requestIdleCallback() (96% good INP, 102ms median), while the 2.6% (1,622 sites) adopting scheduler.yield() achieve a 97ms median INP (95% good INP) by yielding to pending user input with priority continuation.

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 36,524 with phone field data · 63,166 sites with main-thread scheduling API usageBy Arjen Karel · corewebvitals.io/state-of-cwv
5

Understanding main-thread task scheduling APIs

Replace recurring setInterval() polling in sliders and notification plugins with IntersectionObserver or event-driven listeners, and yield inside long initialization loops using scheduler.yield(). On WordPress, 75.1% of sites run setInterval() timers (99ms median INP) while 2.6% use scheduler.yield() (97ms median INP).

Go fix it Yield to the main thread → The dataLayer INP yield pattern → JavaScript priority levels →
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 36,524 with phone field data · 63,166 sites with main-thread scheduling API usageBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals Interaction invoker types → CSS hints → Yielding strategy → INP phase breakdown → By Arjen Karel · 63,295 crawled WordPress sites (36,524 with phone Chrome field data, 63,166 sites with main-thread scheduling API usage, October 2026) · How we measured