WordPress responsive image markup (srcset, picture) and the Core Web Vitals
Fixed-source <img> (92.3%), srcset and sizes (80.9%), and <picture> elements (7.4%): how responsive image markup across the page moves Largest Contentful Paint.
7.4% of WordPress sites use <picture> art direction responsive image markup, and 71% of those sites have a good LCP, against 70% of all WordPress sites.
LCP pass rate
Sites with <picture> art direction responsive image markup have a good LCP most often: 71%, against 70% of all WordPress sites. Sites with srcset and sizes responsive markup have it least often, at 68%.
Responsive image markup usage
Fixed-source <img> is the most used: 92.3% of WordPress sites. <picture> art direction is 7.4% of WordPress 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 srcset and sizes sits in time to first byte (TTFB): 1115 ms median for <picture> art direction against 1136 ms for srcset and sizes. Overall median field LCP is 1.9s for <picture> art direction (TTFB 1115 ms, load delay 373 ms, load duration 165 ms, render delay 258 ms) versus 2.0s for srcset and sizes.
Responsive image markup per framework
On jQuery, 93% of sites use fixed-source <img> responsive image markup, and 69% of jQuery sites have a good LCP, against 70% of all sites. On Vue, 92% of sites use fixed-source <img>, and 67% of Vue sites have a good LCP.
Responsive image markup or the framework
Does the framework explain the responsive image markup difference?
On jQuery, 71% of sites with <picture> art direction responsive image markup have a good LCP, against 68% of jQuery sites with fixed-source <img>. Within jQuery, sites with <picture> art direction have a good LCP more often. On Vue, 70% of sites with <picture> art direction responsive image markup have a good LCP, against 67% of Vue sites with fixed-source <img>. Within Vue, 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 (7.4% of sites) achieve 71% good LCP (1.9s median LCP), compared with 68% on sites using <img srcset> (80.9%) and 69% across sites with fixed-source images (92.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 (92.3%) has at least one fixed-source <img> for UI icons or logos, while 80.9% use <img srcset> on content images (68% good LCP) and 7.4% deploy <picture> elements (71% good LCP). Always pair srcset with an accurate sizes attribute so mobile browsers do not download desktop-width candidates.
By Arjen Karel · 63,295 crawled WordPress sites (36,524 with phone Chrome field data, 62,969 sites with responsive image markup, October 2026). How we measured.