CSS @import chains on Wix sites

99.4% of audited sites (5,590) avoid @import in their stylesheets (92% good LCP, 1.2s median), while 0.6% (31) chain stylesheets via @import (100% good LCP, 1.1s median).

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

99.4% of Wix sites use no @import rules CSS @import rules, and 92% of those sites have a good LCP, against 92% of all Wix sites.

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
1

LCP pass rate

Sites with no @import rules CSS @import rules have a good LCP most often: 92%, against 92% of all Wix sites.

SitesGood, needs improvement, poor LCPMedian
All Wix sites72892%1.2s
Uses CSS @import 0.6%9100%1.1s
No @import rules 99.4%71992%1.2s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
2

CSS @import rules usage

No @import rules is the most used: 99.4% of Wix sites.

No @import rules 99.4%
No @import rules 99.4% Uses CSS @import 0.6%
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
3

How CSS @import chains affect the four LCP phases

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
All Wix sites 376343 ms478 ms259 ms478 mslab 462 ms1.2s
No @import rules 370342 ms478 ms258 ms478 mslab 462 ms1.2s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
4

CSS @import rules per framework

React sets the CSS @import rules to no @import rules on 99% of its sites, and 92% of React sites have a good LCP, against 92% of all sites.

FrameworkCSS @import rules on its sitesGood LCP
All Wix sites 5,621 sitesNo @import rules 99%92%
React 5,620 sitesNo @import rules 99%92%
No @import rules Uses CSS @import
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
5

CSS @import or the framework

Does the framework explain the CSS @import rules difference?

Almost every site with no @import rules CSS @import rules is a React site, and almost every React site has no @import rules CSS @import rules, so the data can't tell no @import rules CSS @import rules and React apart.

Why CSS @import defeats the browser preload scanner

Every external stylesheet blocks rendering by default, but <link rel="stylesheet"> tags are visible in the initial HTML markup so the preload scanner fetches them in parallel. @import hides dependencies inside CSS files: the browser must download the parent stylesheet, parse its rules, and only then open a second request for the imported file. Across 5,590 sites (99.4%) without @import, good LCP reaches 92% (1.2s median), while the 31 sites (0.6%) using @import record 100% good LCP (1.1s median).

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

Understanding CSS @import chains

Replace every @import url(...) rule inside your stylesheets with parallel <link rel="stylesheet"> tags in the HTML <head>, or inline imported CSS files at build time with your bundler. Eliminating the serial CSS hop lets the browser preload scanner discover all stylesheets and fonts during the initial HTML parse. Across all audited sites, 99.4% avoid @import (92% good LCP, 1.2s median) and 0.6% still use it (100% good LCP, 1.1s median).

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals Scripts per page → Image dimensions set → DOM depth → Script initiator → By Arjen Karel · 5,621 crawled Wix sites (728 with desktop Chrome field data, October 2026) · How we measured