First-party vs third-party stylesheets on Wix sites

100.0% of audited sites (5,621) serve first-party stylesheets (94% good LCP, 1.1s median), while the 34.0% (1,909) loading external third-party stylesheets drop to 93% good LCP (1.1s 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 first-party stylesheets stylesheet origin (first-party vs third-party), 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 dataBy Arjen Karel · corewebvitals.io/state-of-cwv
1

LCP pass rate

Sites with first-party stylesheets stylesheet origin (first-party vs third-party) have a good LCP most often: 94%, against 94% of all Wix sites. Sites with third-party stylesheets CSS origin have it least often, at 93%.

SitesGood, needs improvement, poor LCPMedian
All Wix sites3,07794%1.1s
First-party stylesheets 100.0%3,07794%1.1s
Third-party stylesheets 34.0%1,10693%1.1s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
2

Stylesheet origin (first-party vs third-party) usage

First-party stylesheets is the most used: 100.0% of Wix sites.

Sites using each option (sites can use more than one) 5,621 sites
First-party stylesheets 100.0% Third-party stylesheets 34.0%
First-party stylesheets 100.0% Third-party stylesheets 34.0%
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
3

LCP phase breakdown for first-party and third-party stylesheets

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

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
All Wix sites 2,353404 ms446 ms150 ms446 mslab 453 ms1.1s
Third-party stylesheets 847400 ms445 ms152 ms445 mslab 456 ms1.1s
First-party stylesheets 2,353404 ms446 ms150 ms446 mslab 453 ms1.1s
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 dataBy Arjen Karel · corewebvitals.io/state-of-cwv
4

Stylesheet origin (first-party vs third-party) per framework

React sets the stylesheet origin (first-party vs third-party) to first-party stylesheets on 100% of its sites, and 94% of React sites have a good LCP, against 94% of all sites.

FrameworkStylesheet origin (first-party vs third-party) on its sitesGood LCP
All Wix sites 5,621 sitesFirst-party stylesheets 100%Third-party stylesheets 34%94%
React 5,620 sitesFirst-party stylesheets 100%Third-party stylesheets 34%94%
First-party stylesheets Third-party stylesheets
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
5

Stylesheet origin or the framework

Does the framework explain the stylesheet origin (first-party vs third-party) difference?

Almost every site with first-party stylesheets stylesheet origin (first-party vs third-party) is a React site, and almost every React site has first-party stylesheets stylesheet origin (first-party vs third-party), so the data can't tell first-party stylesheets stylesheet origin (first-party vs third-party) and React apart.

How cross-origin CSS files add DNS and TLS round-trips to the critical rendering path

Because external stylesheets block rendering by default, fetching a CSS file from a third-party domain (such as fonts.googleapis.com, cdnjs, or a widget CDN) stalls first paint behind a fresh DNS lookup, TCP handshake, and TLS negotiation. Across 5,621 sites (100.0%) with first-party CSS, good LCP is 94% (1.1s median), whereas across 1,909 sites (34.0%) with third-party CSS, good LCP drops to 93% (1.1s median).

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

Understanding first-party vs third-party stylesheets

Copy external font and icon stylesheets (Google Fonts, Font Awesome, Bootstrap CDN) into your own build pipeline or origin server so every render-blocking CSS file shares the primary HTTP/2 or HTTP/3 connection. Across all audited sites, 100.0% use first-party CSS (94% good LCP) and 34.0% load third-party CSS (93% good LCP).

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals Bytes by resource type → Image source mix → Stylesheet loading mix → Uses @import → By Arjen Karel · 5,621 crawled Wix sites (3,077 with phone Chrome field data, October 2026) · How we measured