Network resource types on Wix sites
Alongside HTML documents (100.0%), images (99.9%), scripts (100.0%), stylesheets (46.9%), and fonts (99.6%), 99.9% of audited sites (5,619) fire runtime fetch() requests (92% good LCP, 1.2s median) and 99.9% fire XMLHttpRequest calls (92% good LCP).
100.0% of Wix sites use script requests network resource type mix, and 92% of those sites have a good LCP, against 92% of all Wix sites.
LCP pass rate
Sites with script requests network resource type mix have a good LCP most often: 92%, against 92% of all Wix sites. Sites with stylesheet requests resource types have it least often, at 90%.
Network resource type mix usage
Script requests is the most used: 100.0% of Wix sites.
LCP phase breakdown by network resource types loaded
Across the four LCP sub-parts in Chrome's field data, the largest gap between script requests and stylesheet requests sits in resource load delay: 478 ms median for script requests against 509 ms for stylesheet requests. Overall median field LCP is 1.2s for script requests (TTFB 343 ms, load delay 478 ms, load duration 259 ms, render delay 137 ms) versus 1.3s for stylesheet requests.
Network resource type mix per framework
React sets the network resource type mix to script requests on 100% of its sites, and 92% of React sites have a good LCP, against 92% of all sites.
React 5,620 sitesJavaScript files 100%HTML document 100%Other resources (pings / beacons / manifests) 100%Fetch API requests 100%Images 100%XMLHttpRequest (XHR) calls 100%Web fonts 100%CSS stylesheets 47%92%Network resource types or the framework
Does the framework explain the network resource type mix difference?
Almost every site with script requests network resource type mix is a React site, and almost every React site has script requests network resource type mix, so the data can't tell script requests network resource type mix and React apart.
How early fetch() and XHR API calls compete with critical rendering assets
Almost every web page loads an HTML document (100.0%), images (99.9%), scripts (100.0%), stylesheets (46.9%), and web fonts (99.6%, 92% good LCP at a 1.2s median). However, 99.9% of sites (5,619) also fire client-side fetch() requests during initial load (92% good LCP, 1.2s median) and 99.9% (5,614) fire XHR calls (92% good LCP, 1.2s median), often to fetch client-rendered content, A/B test configs, or cart state.
Understanding network resource types
Render above-the-fold data server-side in the initial HTML document rather than waiting on client-side fetch() or XMLHttpRequest calls during startup, and defer telemetry beacons until after LCP. Across all audited sites, 99.9% load images (92% good LCP) while 99.9% fire fetch() calls during load (92% good LCP).
By Arjen Karel · 5,621 crawled Wix sites (728 with desktop Chrome field data, October 2026). How we measured.