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.
29.3% of React sites use <picture> art direction responsive image markup, and 89% of those sites have a good LCP, against 84% of all React sites.
LCP pass rate
Sites with <picture> art direction responsive image markup have a good LCP most often: 89%, against 84% of all React sites. Sites with fixed-source <img> responsive markup have it least often, at 84%.
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.
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): 442 ms median for <picture> art direction against 505 ms for fixed-source <img>. Overall median field LCP is 1.3s for <picture> art direction (TTFB 442 ms, load delay 476 ms, load duration 137 ms, render delay 164 ms) versus 1.4s for fixed-source <img>.
Responsive image markup per platform
On Wix, 91% of sites use fixed-source <img> responsive image markup, and 94% of Wix sites have a good LCP, against 84% of all sites. On WordPress, 94% of sites use fixed-source <img>, and 63% of WordPress sites have a good LCP.
Responsive image markup or the platform
Does the platform explain the responsive image markup difference?
On Wix, 92% of sites with <picture> art direction responsive image markup have a good LCP, against 95% 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, 65% of sites with <picture> art direction responsive image markup have a good LCP, against 62% 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 89% good LCP (1.3s median LCP), compared with 86% on sites using <img srcset> (84.9%) and 84% across sites with fixed-source images (91.3%).
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 (86% good LCP) and 29.3% deploy <picture> elements (89% good LCP). Always pair srcset with an accurate sizes attribute so mobile browsers do not download desktop-width candidates.
By Arjen Karel · 9,570 crawled React sites (5,488 with phone Chrome field data, 9,502 sites with responsive image markup, October 2026). How we measured.