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).
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.
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%.
CSS @import rules usage
No @import rules is the most used: 97.1% of WordPress sites.
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.
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.
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).
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).
By Arjen Karel · 63,295 crawled WordPress sites (60,855 with all devices Chrome field data, October 2026). How we measured.