The State of Web Vitals

LCP sub-part breakdown on Wix sites

TTFB is the largest LCP sub-part on 46.1% of audited sites (1,819, 94% good LCP), followed by resource load delay on 50.4% (98% good LCP) and element render delay on 3.1% (77% good LCP).

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

50.4% of Wix sites use resource load delay as the largest LCP sub-part LCP sub-part breakdown, and 98% of those sites have a good LCP, against 94% of all Wix sites.

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field data · 3,945 sites with LCP sub-part breakdownBy Arjen Karel · corewebvitals.io/state-of-cwv
1

LCP pass rate

Sites with resource load delay as the largest LCP sub-part LCP sub-part breakdown have a good LCP most often: 98%, against 94% of all Wix sites. Sites with TTFB as the largest LCP sub-part dominant LCP phase have it least often, at 94%.

SitesGood, needs improvement, poor LCPMedian
All Wix sites3,07794%1.1s
Load duration is biggest sub-part 0.4%6100%1.1s
Load delay is biggest sub-part 50.4%1,27198%1.1s
TTFB is biggest sub-part 46.1%99194%1.2s
Render delay is biggest sub-part 3.1%8177%1.4s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field data · 3,945 sites with LCP sub-part breakdownBy Arjen Karel · corewebvitals.io/state-of-cwv
2

LCP sub-part breakdown usage

Resource load delay as the largest LCP sub-part is the most used: 50.4% of Wix sites.

Load delay is biggest sub-part 50.4% TTFB is biggest sub-part 46.1%
Load delay is biggest sub-part 50.4% TTFB is biggest sub-part 46.1% Render delay is biggest sub-part 3.1% Load duration is biggest sub-part 0.4%
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field data · 3,945 sites with LCP sub-part breakdownBy 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 resource load delay as the largest LCP sub-part and TTFB as the largest LCP sub-part sits in time to first byte (TTFB): 355 ms median for resource load delay as the largest LCP sub-part against 553 ms for TTFB as the largest LCP sub-part. Overall median field LCP is 1.1s for resource load delay as the largest LCP sub-part (TTFB 355 ms, load delay 519 ms, load duration 112 ms, render delay 140 ms) versus 1.2s for TTFB as the largest LCP sub-part.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
Wix sites with LCP sub-part breakdown 2,346404 ms446 ms446 mslab 453 ms1.1s
Render delay is biggest sub-part 81309 ms272 ms771 ms272 mslab 285 ms1.4s
TTFB is biggest sub-part 990553 ms356 ms162 ms356 mslab 370 ms1.2s
Load delay is biggest sub-part 1,269355 ms519 ms519 mslab 531 ms1.1s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field data · 3,945 sites with LCP sub-part breakdownBy Arjen Karel · corewebvitals.io/state-of-cwv
4

LCP sub-part breakdown per framework

React sets the LCP sub-part breakdown to resource load delay as the largest LCP sub-part on 50% of its sites, and 94% of React sites have a good LCP, against 94% of all sites.

FrameworkLCP sub-part breakdown on its sitesGood LCP
Wix sites with LCP sub-part breakdown 3,945 sitesLoad delay is biggest sub-part 50%TTFB is biggest sub-part 46%94%
React 3,945 sitesLoad delay is biggest sub-part 50%TTFB is biggest sub-part 46%94%
Load delay is biggest sub-part TTFB is biggest sub-part Render delay is biggest sub-part Load duration is biggest sub-part
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field data · 3,945 sites with LCP sub-part breakdownBy Arjen Karel · corewebvitals.io/state-of-cwv
5

LCP sub-part breakdown or the framework

Does the framework explain the LCP sub-part breakdown difference?

On React, 98% of sites with resource load delay as the largest LCP sub-part LCP sub-part breakdown have a good LCP, against 94% of React sites with TTFB as the largest LCP sub-part. Within React, sites with resource load delay as the largest LCP sub-part have a good LCP more often.

Why network transfer duration is rarely the real LCP bottleneck

Resource load duration is the largest sub-part on just 0.4% (16) of audited sites. Most LCP failures happen while waiting for the first HTML byte (46.1% TTFB-dominated, 94% good LCP, 1.2s median), waiting to discover the hero image (50.4% load-delay-dominated, 98% good LCP), or waiting on blocking head scripts and stylesheets (3.1% render-delay-dominated, 77% good LCP).

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field data · 3,945 sites with LCP sub-part breakdownBy Arjen Karel · corewebvitals.io/state-of-cwv
6

Understanding LCP sub-part breakdown

Fix your largest LCP sub-part first: cache HTML at the CDN edge when TTFB dominates, preload the hero image when load delay dominates, or remove blocking head scripts when render delay dominates. Across all audited sites, 46.1% are TTFB-dominated (94% good LCP, 1.2s median) versus 50.4% load-delay-dominated (98% good LCP, 1.1s median).

Go fix it LCP: resource load delay → LCP: element render delay → Time to First Byte → How I lowered the LCP by 70 percent →
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field data · 3,945 sites with LCP sub-part breakdownBy Arjen Karel · corewebvitals.io/state-of-cwv

By Arjen Karel · 5,621 crawled Wix sites (3,077 with phone Chrome field data, 3,945 sites with LCP sub-part breakdown, October 2026). How we measured.