LCP element types on Wix sites

Sites with a text block as the LCP element have a good LCP most often: 94%, against 94% of all Wix sites. Sites with an <img> tag as the LCP element have it least often, at 94%.

An <img> tag is the most used: 70.4% of Wix sites. A text block is 26.7% of Wix sites.

Across the four LCP sub-parts in Chrome's field data, the largest gap between a text block and an <img> tag sits in resource load delay: 438 ms median for a text block against 449 ms for an <img> tag. Overall median field LCP is 1.1s for a text block (TTFB 402 ms, load delay 438 ms, load duration 104 ms, render delay 143 ms) versus 1.1s for an <img> tag.

On React, 70% of sites use an <img> tag as the LCP element, and 94% of React sites have a good LCP, against 94% of all sites.

FrameworkAs the LCP element on its sitesGood LCP

Wix sites with as the LCP element 5,589 sites<img> element 70%Text heading or paragraph 27%94%

React 5,588 sites<img> element 70%Text heading or paragraph 27%94%

<img> element Text heading or paragraph <video> element CSS background-image

Does the framework explain the as the LCP element difference?

On React, 94% of sites with a text block as the LCP element have a good LCP, against 94% of React sites with an <img> tag. Within React, sites with a text block and an <img> tag have a good LCP about equally often.

Why <img> and text blocks beat CSS background-image heroes

An <img> element in the HTML markup is visible to Chrome's preload scanner immediately and supports fetchpriority="high", srcset, and modern formats, reaching 94% good LCP (1.2s median). A text LCP element needs no image download at all and paints as soon as render-blocking CSS and web fonts resolve (94% good LCP, 1.1s median). A CSS background-image hides the image URL from the preload scanner until stylesheets are parsed and matched against the DOM, dropping good LCP to 97% (1.3s median).