The State of Web Vitals

Image hosting origins on Wix sites

2.5% of audited sites (142) serve images from their own origin (93% good LCP, 1.4s median), 100.0% load images from external domains or CDNs (94% good LCP), and 36.2% inline base64 data-URI images (94% good LCP, 1.2s median).

Field data PhoneDesktopAll Scope All sites October 2026 edition · Phone field outcomes · Wix sites only
Wix Scoped to 5,623 sites out of 203,892 analyzed (cms) Compare with all sites →

100.0% of Wix sites use cross-origin images image hosting origin, and 94% of those sites have a good LCP, against 94% of all Wix sites.

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field data · 5,619 sites with image hosting originBy Arjen Karel · corewebvitals.io/state-of-cwv
1

LCP pass rate

Sites with cross-origin images image hosting origin have a good LCP most often: 94%, against 94% of all Wix sites. Sites with inline data-URI images image origin have it least often, at 94%.

SitesGood, needs improvement, poor LCPMedian
All Wix sites3,07794%1.1s
Cross-origin / external CDN 100.0%3,07594%1.1s
Inline data: URI images 36.2%1,19994%1.2s
Same-origin (self-hosted) 2.5%7493%1.4s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field data · 5,619 sites with image hosting originBy Arjen Karel · corewebvitals.io/state-of-cwv
2

Image hosting origin usage

Cross-origin images is the most used: 100.0% of Wix sites.

Sites using each option (sites can use more than one) 5,619 sites
Cross-origin / external CDN 100.0% Inline data: URI images 36.2%
Cross-origin / external CDN 100.0% Inline data: URI images 36.2% Same-origin (self-hosted) 2.5%
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field data · 5,619 sites with image hosting originBy Arjen Karel · corewebvitals.io/state-of-cwv
3

LCP phase breakdown by image hosting source

Across the four LCP sub-parts in Chrome's field data, the largest gap between cross-origin images and inline data-URI images sits in time to first byte (TTFB): 404 ms median for cross-origin images against 421 ms for inline data-URI images. Overall median field LCP is 1.1s for cross-origin images (TTFB 404 ms, load delay 446 ms, load duration 110 ms, render delay 150 ms) versus 1.2s for inline data-URI images.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
Wix sites with image hosting origin 2,353404 ms446 ms150 ms446 mslab 453 ms1.1s
Cross-origin / external CDN 2,353404 ms446 ms150 ms446 mslab 453 ms1.1s
Inline data: URI images 940421 ms452 ms148 ms452 mslab 467 ms1.2s
Same-origin (self-hosted) 53522 ms468 ms159 ms468 mslab 469 ms1.4s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field data · 5,619 sites with image hosting originBy Arjen Karel · corewebvitals.io/state-of-cwv
4

Image hosting origin per framework

React sets the image hosting origin to cross-origin images on 100% of its sites, and 94% of React sites have a good LCP, against 94% of all sites.

FrameworkImage hosting origin on its sitesGood LCP
Wix sites with image hosting origin 5,619 sitesCross-origin / external CDN 100%Inline data: URI images 36%94%
React 5,618 sitesCross-origin / external CDN 100%Inline data: URI images 36%94%
Cross-origin / external CDN Inline data: URI images Same-origin (self-hosted)
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field data · 5,619 sites with image hosting originBy Arjen Karel · corewebvitals.io/state-of-cwv
5

Image hosting origin or the framework

Does the framework explain the image hosting origin difference?

Almost every site with cross-origin images image hosting origin is a React site, and almost every React site has cross-origin images image hosting origin, so the data can't tell cross-origin images image hosting origin and React apart.

Why base64 inline data-URI images bloat HTML and delay LCP

Serving images from the same origin (2.5% of sites, 142) reuses the primary HTTP/2 or HTTP/3 connection (93% good LCP, 1.4s median). Cross-origin images (100.0%, 94% good LCP) include both dedicated media CDNs and external third-party pixels. Inlining images as base64 data: URIs (36.2% of sites, 2,032) inflates HTML/CSS byte size by ~33% and blocks the parser, dropping good LCP to 94% (1.2s median).

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field data · 5,619 sites with image hosting originBy Arjen Karel · corewebvitals.io/state-of-cwv
6

Understanding image hosting origins

Serve images from your primary origin to share the main connection, or add <link rel="preconnect"> if you use a dedicated cross-origin image CDN, and avoid base64 data: URIs for anything larger than tiny CSS icons. Across all audited sites, 2.5% use same-origin images (93% good LCP) while 36.2% inline data: URIs (94% good LCP).

Go fix it Optimize images for Core Web Vitals → Third-party domains →
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field data · 5,619 sites with image hosting originBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals Bytes by resource type → Images per page → DOM size → Iframes per page → By Arjen Karel · 5,621 crawled Wix sites (3,077 with phone Chrome field data, 5,619 sites with image hosting origin, October 2026) · How we measured