LCP sub-part breakdown on React sites

Sites with resource load delay as the largest LCP sub-part LCP sub-part breakdown have a good LCP most often: 92%, against 84% of all React sites. Sites with element render delay as the largest LCP sub-part dominant LCP phase have it least often, at 78%.

TTFB as the largest LCP sub-part is the most used: 56.4% of React sites. Resource load delay as the largest LCP sub-part is 38.6% of React sites.

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 element render delay as the largest LCP sub-part sits in element render delay: 146 ms median for resource load delay as the largest LCP sub-part against 823 ms for element render delay as the largest LCP sub-part. Overall median field LCP is 1.2s for resource load delay as the largest LCP sub-part (TTFB 367 ms, load delay 564 ms, load duration 120 ms, render delay 146 ms) versus 1.8s for element render delay as the largest LCP sub-part.

Wix sets the LCP sub-part breakdown to resource load delay as the largest LCP sub-part on 51% of its sites, and 94% of Wix sites have a good LCP, against 84% of all sites. WordPress sets the LCP sub-part breakdown to TTFB as the largest LCP sub-part on 85% of its sites, and 63% of WordPress sites have a good LCP.

PlatformLCP sub-part breakdown on its sitesGood LCP

React sites with LCP sub-part breakdown 6,740 sitesTTFB is biggest sub-part 56%Load delay is biggest sub-part 39%84%

Wix 4,072 sitesLoad delay is biggest sub-part 51%TTFB is biggest sub-part 45%94%

WordPress 1,679 sitesTTFB is biggest sub-part 85%63%

TTFB is biggest sub-part Load delay is biggest sub-part Render delay is biggest sub-part Load duration is biggest sub-part

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

On Wix, 98% of sites with resource load delay as the largest LCP sub-part LCP sub-part breakdown have a good LCP, against 94% of Wix sites with TTFB as the largest LCP sub-part. Within Wix, sites with resource load delay as the largest LCP sub-part have a good LCP more often. On WordPress, 65% of sites with resource load delay as the largest LCP sub-part LCP sub-part breakdown have a good LCP, against 60% of WordPress sites with TTFB as the largest LCP sub-part. Within WordPress, sites with resource load delay as the largest LCP sub-part and TTFB as the largest LCP sub-part have a good LCP about equally often.

Why network transfer duration is rarely the real LCP bottleneck

Resource load duration is the largest sub-part on just 0.7% (49) of audited sites. Most LCP failures happen while waiting for the first HTML byte (56.4% TTFB-dominated, 79% good LCP, 1.6s median), waiting to discover the hero image (38.6% load-delay-dominated, 92% good LCP), or waiting on blocking head scripts and stylesheets (4.2% render-delay-dominated, 78% good LCP).