LCP element types on Wix sites

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

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

Across the four LCP sub-parts in Chrome's field data, the largest gap between an <img> tag and a text block sits in time to first byte (TTFB): 329 ms median for an <img> tag against 362 ms for a text block. Overall median field LCP is 1.2s for an <img> tag (TTFB 329 ms, load delay 480 ms, load duration 258 ms, render delay 139 ms) versus 1.2s for a text block.

React sets the as the LCP element to an <img> tag on 70% of its sites, and 92% of React sites have a good LCP, against 92% 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%92%

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

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

Does the framework explain the as the LCP element difference?

On React, 92% of sites with an <img> tag as the LCP element have a good LCP, against 92% of React sites with a text block. Within React, sites with an <img> tag and a text block 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 92% 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 (92% good LCP, 1.2s 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 60% (1.6s median).