Responsive image markup on React sites

Fixed-source <img> (91.3%), srcset and sizes (84.9%), and <picture> elements (29.3%): how responsive image markup across the page moves Largest Contentful Paint.

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

29.3% of React sites use <picture> art direction responsive image markup, and 86% of those sites have a good LCP, against 79% of all React sites.

The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 1,979 with desktop field data · 9,502 sites with responsive image markupBy Arjen Karel · corewebvitals.io/state-of-cwv
1

LCP pass rate

Sites with <picture> art direction responsive image markup have a good LCP most often: 86%, against 79% of all React sites. Sites with fixed-source <img> responsive markup have it least often, at 78%.

SitesGood, needs improvement, poor LCPMedian
All React sites1,97979%1.5s
<picture> with <source> 29.3%57586%1.4s
<img srcset="..."> 84.9%1,44379%1.5s
Fixed-source <img> (no srcset) 91.3%1,84578%1.6s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 1,979 with desktop field data · 9,502 sites with responsive image markupBy Arjen Karel · corewebvitals.io/state-of-cwv
2

Responsive image markup usage

Fixed-source <img> is the most used: 91.3% of React sites. <picture> art direction is 29.3% of React sites.

Sites using each option (sites can use more than one) 9,502 sites
Fixed-source <img> (no srcset) 91.3% <img srcset="..."> 84.9% <picture> with <source> 29.3%
Fixed-source <img> (no srcset) 91.3% <img srcset="..."> 84.9% <picture> with <source> 29.3%
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 1,979 with desktop field data · 9,502 sites with responsive image markupBy Arjen Karel · corewebvitals.io/state-of-cwv
3

Where responsive image markup saves time: the four LCP phases

Across the four LCP sub-parts in Chrome's field data, the largest gap between <picture> art direction and fixed-source <img> sits in time to first byte (TTFB): 502 ms median for <picture> art direction against 722 ms for fixed-source <img>. Overall median field LCP is 1.4s for <picture> art direction (TTFB 502 ms, load delay 465 ms, load duration 161 ms, render delay 161 ms) versus 1.6s for fixed-source <img>.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
React sites with responsive image markup 1,315708 ms413 ms193 ms413 mslab 429 ms1.6s
<img srcset="..."> 931773 ms407 ms193 ms407 mslab 408 ms1.6s
Fixed-source <img> (no srcset) 1,255722 ms418 ms194 ms418 mslab 435 ms1.6s
<picture> with <source> 383502 ms465 ms465 mslab 487 ms1.4s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 1,979 with desktop field data · 9,502 sites with responsive image markupBy Arjen Karel · corewebvitals.io/state-of-cwv
4

Responsive image markup per platform

On Wix, 91% of sites use fixed-source <img> responsive image markup, and 92% of Wix sites have a good LCP, against 79% of all sites. On WordPress, 94% of sites use fixed-source <img>, and 66% of WordPress sites have a good LCP.

PlatformResponsive image markup on its sitesGood LCP
React sites with responsive image markup 9,502 sitesFixed-source <img> (no srcset) 91%<img srcset="..."> 85%<picture> with <source> 29%79%
Wix 5,802 sitesFixed-source <img> (no srcset) 91%<img srcset="..."> 91%<picture> with <source> 38%92%
WordPress 2,334 sitesFixed-source <img> (no srcset) 94%<img srcset="..."> 85%66%
Fixed-source <img> (no srcset) <img srcset="..."> <picture> with <source>
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 1,979 with desktop field data · 9,502 sites with responsive image markupBy Arjen Karel · corewebvitals.io/state-of-cwv
5

Responsive image markup or the platform

Does the platform explain the responsive image markup difference?

On Wix, 90% of sites with <picture> art direction responsive image markup have a good LCP, against 92% of Wix sites with fixed-source <img>. Within Wix, sites with <picture> art direction and fixed-source <img> have a good LCP about equally often. On WordPress, 72% of sites with <picture> art direction responsive image markup have a good LCP, against 66% of WordPress sites with fixed-source <img>. Within WordPress, sites with <picture> art direction and fixed-source <img> have a good LCP about equally often.

How srcset and <picture> select candidate URLs during preload scanning

Chromium's preload scanner evaluates <source media="..." type="..."> and <img srcset="..." sizes="..."> before the main parser builds the DOM. Sites that serve responsive <picture> elements (29.3% of sites) achieve 86% good LCP (1.4s median LCP), compared with 79% on sites using <img srcset> (84.9%) and 78% across sites with fixed-source images (91.3%).

The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 1,979 with desktop field data · 9,502 sites with responsive image markupBy Arjen Karel · corewebvitals.io/state-of-cwv
6

Understanding responsive image markup

Use <img srcset sizes> for multi-width content images and <picture> when serving mobile-specific crops or modern formats with fallbacks. Nearly every site (91.3%) has at least one fixed-source <img> for UI icons or logos, while 84.9% use <img srcset> on content images (79% good LCP) and 29.3% deploy <picture> elements (86% good LCP). Always pair srcset with an accurate sizes attribute so mobile browsers do not download desktop-width candidates.

The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 1,979 with desktop field data · 9,502 sites with responsive image markupBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals Stylesheet origin (1P/3P) → DOM size → Image format mix → Media source → By Arjen Karel · 9,570 crawled React sites (1,979 with desktop Chrome field data, 9,502 sites with responsive image markup, October 2026) · How we measured