The State of Web Vitals

Document lifecycle milestones on React sites

48.2% of audited sites (4,617) reach DOMComplete in under 350ms and pass field LCP at 93% (1.1s median), whereas the 17.5% taking over 1,500ms pass at 58% (2.2s median).

Field data PhoneDesktopAll Scope All sites October 2026 edition · Phone field outcomes · React sites only
React Scoped to 9,570 sites out of 210,902 analyzed (frameworks) Compare with all sites →

48.2% of React sites use under 350ms DOMComplete document lifecycle milestones, and 93% of those sites have a good LCP, against 84% of all React sites.

The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
1

LCP pass rate

Sites with under 350ms DOMComplete document lifecycle milestones have a good LCP most often: 93%, against 84% of all React sites. Sites with over 1,500ms DOMComplete DOMComplete time have it least often, at 58%.

SitesGood, needs improvement, poor LCPMedian
All React sites5,48884%1.4s
Under 350ms DOMComplete 48.2%2,53893%1.1s
350 to 700ms DOMComplete 20.0%1,11589%1.4s
700 to 1,500ms DOMComplete 14.3%83680%1.8s
Over 1,500ms DOMComplete 17.5%99958%2.2s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
2

Document lifecycle milestones usage

Under 350ms DOMComplete is the most used: 48.2% of React sites.

Under 350ms DOMComplete 48.2% 350 to 700ms DOMComplete 20.0% Over 1,500ms DOMComplete 17.5% 700 to 1,500ms DOMComplete 14.3%
Under 350ms DOMComplete 48.2% 350 to 700ms DOMComplete 20.0% Over 1,500ms DOMComplete 17.5% 700 to 1,500ms DOMComplete 14.3%
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
3

The four LCP phases

Across the four LCP sub-parts in Chrome's field data, the largest gap between under 350ms DOMComplete and over 1,500ms DOMComplete sits in time to first byte (TTFB): 412 ms median for under 350ms DOMComplete against 1202 ms for over 1,500ms DOMComplete. Overall median field LCP is 1.1s for under 350ms DOMComplete (TTFB 412 ms, load delay 417 ms, load duration 112 ms, render delay 154 ms) versus 2.3s for over 1,500ms DOMComplete.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
All React sites 4,169502 ms433 ms433 mslab 439 ms1.4s
Under 350ms DOMComplete 1,911412 ms417 ms417 mslab 425 ms1.1s
700 to 1,500ms DOMComplete 644817 ms427 ms427 mslab 432 ms1.8s
Over 1,500ms DOMComplete 7741202 ms459 ms256 ms459 mslab 450 ms2.3s
350 to 700ms DOMComplete 840485 ms464 ms464 mslab 468 ms1.4s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
4

Document lifecycle milestones per platform

Wix sets the document lifecycle milestones to under 350ms DOMComplete on 67% of its sites, and 94% of Wix sites have a good LCP, against 84% of all sites.

PlatformDocument lifecycle milestones on its sitesGood LCP
All React sites 9,570 sitesUnder 350ms DOMComplete 48%350 to 700ms DOMComplete 20%Over 1,500ms DOMComplete 18%700 to 1,500ms DOMComplete 14%84%
Wix 5,824 sitesUnder 350ms DOMComplete 67%350 to 700ms DOMComplete 20%94%
WordPress 2,342 sitesOver 1,500ms DOMComplete 47%700 to 1,500ms DOMComplete 26%350 to 700ms DOMComplete 17%63%
Under 350ms DOMComplete 350 to 700ms DOMComplete Over 1,500ms DOMComplete 700 to 1,500ms DOMComplete
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
5

Document lifecycle milestones or the platform

Does the platform explain the document lifecycle milestones difference?

On Wix, 95% of sites with under 350ms DOMComplete document lifecycle milestones have a good LCP, against 94% of Wix sites with 350 to 700ms DOMComplete. Within Wix, sites with under 350ms DOMComplete and 350 to 700ms DOMComplete have a good LCP about equally often. On WordPress, 80% of sites with under 350ms DOMComplete document lifecycle milestones have a good LCP, against 78% of WordPress sites with 350 to 700ms DOMComplete. Within WordPress, sites with under 350ms DOMComplete and 350 to 700ms DOMComplete have a good LCP about equally often.

What DOMInteractive and DOMComplete reveal about subresource contention

DOMInteractive marks when HTML parsing finishes and deferred scripts begin executing; DOMComplete waits for all synchronous subresources. Across 4,617 sites (48.2%) reaching DOMComplete in under 350ms, 93% pass field LCP at a 1.1s median, compared with 58% (2.2s median) on the 17.5% (1,676) exceeding 1,500ms.

The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
6

Understanding document lifecycle milestones

Defer non-critical scripts and lazy-load below-the-fold subresources so DOMInteractive and DOMComplete are not held back by slow third-party requests. Across all audited sites, 48.2% finish DOMComplete under 350ms (93% good LCP, 1.1s median) versus 17.5% above 1,500ms (58% good LCP, 2.2s median).

Go fix it How we measured → Head vs footer JavaScript →
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals Total Blocking Time (lab) → Main-thread CPU (lab) → Lab paint timeline → By Arjen Karel · 9,570 crawled React sites (5,488 with phone Chrome field data, October 2026) · How we measured