WordPress CSS @import chains and the Core Web Vitals

97.1% of audited sites (61,463) avoid @import in their stylesheets (70% good LCP, 1.9s median), while 2.9% (1,832) chain stylesheets via @import (66% good LCP, 2.1s median).

Field data PhoneDesktopAll Scope All sites October 2026 edition · All devices field outcomes · WordPress sites only
WordPress Scoped to 63,295 sites out of 203,892 analyzed (cms) Compare with all sites →

97.1% of WordPress sites use no @import rules CSS @import rules, and 70% of those sites have a good LCP, against 70% of all WordPress sites.

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices 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: 70%, against 70% of all WordPress sites. Sites with CSS @import CSS @import have it least often, at 66%.

SitesGood, needs improvement, poor LCPMedian
All WordPress sites60,85570%1.9s
No @import rules 97.1%59,07270%1.9s
Uses CSS @import 2.9%1,78366%2.1s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
2

CSS @import rules usage

No @import rules is the most used: 97.1% of WordPress sites.

No @import rules 97.1%
No @import rules 97.1% Uses CSS @import 2.9%
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
3

How CSS @import chains affect the four LCP phases

Across the four LCP sub-parts in Chrome's field data, the largest gap between no @import rules and CSS @import sits in time to first byte (TTFB): 1125 ms median for no @import rules against 1188 ms for CSS @import. Overall median field LCP is 1.9s for no @import rules (TTFB 1125 ms, load delay 339 ms, load duration 166 ms, render delay 234 ms) versus 2.1s for CSS @import.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
All WordPress sites 43,6221127 ms340 ms235 ms340 mslab 340 ms1.9s
No @import rules 42,2851125 ms339 ms234 ms339 mslab 339 ms1.9s
Uses CSS @import 1,3371188 ms385 ms260 ms385 mslab 385 ms2.1s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
4

CSS @import rules per framework

Vue sets the CSS @import rules to no @import rules on 98% of its sites, and 68% of Vue sites have a good LCP, against 70% of all sites.

FrameworkCSS @import rules on its sitesGood LCP
All WordPress sites 63,295 sitesNo @import rules 97%70%
Alpine 380 sitesNo @import rules 96%80%
jQuery 60,314 sitesNo @import rules 97%69%
Vue 4,844 sitesNo @import rules 98%68%
React 2,233 sitesNo @import rules 95%61%
No @import rules Uses CSS @import
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices 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 jQuery site, and almost every jQuery site has no @import rules CSS @import rules, so the data can't tell no @import rules CSS @import rules and jQuery apart. On Vue, 68% of sites with no @import rules CSS @import rules have a good LCP, against 60% of Vue sites with CSS @import. Within Vue, sites with no @import rules and CSS @import have a good LCP about equally often. On React, 61% of sites with no @import rules CSS @import rules have a good LCP, against 48% of React sites with CSS @import. Within React, sites with no @import rules have a good LCP more often.

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 61,463 sites (97.1%) without @import, good LCP reaches 70% (1.9s median), while the 1,832 sites (2.9%) using @import record 66% good LCP (2.1s median).

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
6

Understanding CSS @import chains

Replace @import rules in WordPress child themes and Google Fonts snippets with parallel wp_enqueue_style() calls or <link rel="stylesheet"> tags in the document <head>. On WordPress, 97.1% of sites avoid @import (70% good LCP, 1.9s median) while 2.9% still trigger @import chains (66% good LCP, 2.1s median).

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals Scripts per page → Image dimensions set → DOM depth → Script initiator → By Arjen Karel · 63,295 crawled WordPress sites (60,855 with all devices Chrome field data, October 2026) · How we measured