WordPress image hosting origins and the Core Web Vitals
98.4% of audited sites (62,217) serve images from their own origin (70% good LCP, 1.9s median), 70.0% load images from external domains or CDNs (68% good LCP), and 20.7% inline base64 data-URI images (68% good LCP, 2.0s median).
98.4% of WordPress sites use same-origin images image hosting origin, and 70% of those sites have a good LCP, against 70% of all WordPress sites.
LCP pass rate
Sites with same-origin images image hosting origin have a good LCP most often: 70%, against 70% of all WordPress sites. Sites with inline data-URI images image origin have it least often, at 68%.
Image hosting origin usage
Same-origin images is the most used: 98.4% of WordPress sites.
LCP phase breakdown by image hosting source
Across the four LCP sub-parts in Chrome's field data, the largest gap between same-origin images and inline data-URI images sits in resource load delay: 340 ms median for same-origin images against 409 ms for inline data-URI images. Overall median field LCP is 1.9s for same-origin images (TTFB 1129 ms, load delay 340 ms, load duration 167 ms, render delay 235 ms) versus 2.0s for inline data-URI images.
Image hosting origin per framework
Vue sets the image hosting origin to same-origin images on 99% of its sites, and 68% of Vue sites have a good LCP, against 70% of all sites.
Alpine 380 sitesSame-origin (self-hosted) 95%Cross-origin / external CDN 83%Inline data: URI images 25%80%
jQuery 60,268 sitesSame-origin (self-hosted) 98%Cross-origin / external CDN 70%Inline data: URI images 21%69%
Vue 4,842 sitesSame-origin (self-hosted) 99%Cross-origin / external CDN 91%Inline data: URI images 25%68%
React 2,233 sitesSame-origin (self-hosted) 98%Cross-origin / external CDN 79%Inline data: URI images 24%61%Image hosting origin or the framework
Does the framework explain the image hosting origin difference?
Almost every site with same-origin images image hosting origin is a jQuery site, and almost every jQuery site has same-origin images image hosting origin, so the data can't tell same-origin images image hosting origin and jQuery apart. On Vue, 68% of sites with same-origin images image hosting origin have a good LCP, against 68% of Vue sites with cross-origin images. Within Vue, sites with same-origin images and cross-origin images have a good LCP about equally often. On React, 61% of sites with same-origin images image hosting origin have a good LCP, against 59% of React sites with cross-origin images. Within React, sites with same-origin images and cross-origin images have a good LCP about equally often.
Why base64 inline data-URI images bloat HTML and delay LCP
Serving images from the same origin (98.4% of sites, 62,217) reuses the primary HTTP/2 or HTTP/3 connection (70% good LCP, 1.9s median). Cross-origin images (70.0%, 68% good LCP) include both dedicated media CDNs and external third-party pixels. Inlining images as base64 data: URIs (20.7% of sites, 13,075) inflates HTML/CSS byte size by ~33% and blocks the parser, dropping good LCP to 68% (2.0s median).
Understanding image hosting origins
Serve uploads from your primary domain or a preconnected media CDN, and disable lazy-load placeholder plugins that inject base64 data: URI images into post HTML. On WordPress, 98.4% of sites serve same-origin images (70% good LCP) while 70.0% load cross-origin images (68% good LCP).
By Arjen Karel · 63,295 crawled WordPress sites (60,855 with all devices Chrome field data, 63,231 sites with image hosting origin, October 2026). How we measured.