First-party vs third-party stylesheets and the Core Web Vitals
99.3% of audited sites (197,620) serve first-party stylesheets (82% good LCP, 1.5s median), while the 56.1% (111,639) loading external third-party stylesheets drop to 81% good LCP (1.6s median).
99.3% of sites use first-party stylesheets stylesheet origin (first-party vs third-party), and 82% of those sites have a good LCP, against 82% of all sites.
LCP pass rate
Sites with first-party stylesheets stylesheet origin (first-party vs third-party) have a good LCP most often: 82%, against 82% of all sites. Sites with third-party stylesheets CSS origin have it least often, at 81%.
Stylesheet origin (first-party vs third-party) usage
First-party stylesheets is the most used: 99.3% of sites.
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 resource load delay: 319 ms median for first-party stylesheets against 351 ms for third-party stylesheets. Overall median field LCP is 1.5s for first-party stylesheets (TTFB 649 ms, load delay 319 ms, load duration 143 ms, render delay 224 ms) versus 1.6s for third-party stylesheets.
Understanding first-party vs third-party stylesheets
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 197,620 sites (99.3%) with first-party CSS, good LCP is 82% (1.5s median), whereas across 111,639 sites (56.1%) with third-party CSS, good LCP drops to 81% (1.6s median).
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, 99.3% use first-party CSS (82% good LCP) and 56.1% load third-party CSS (81% good LCP).
How stylesheet origin (first-party vs third-party) plays out per platform
What the field data shows when you isolate a single CMS or framework.
WordPress 65,503 sites 59.6% of WordPress sites load third-party CSS (68% good LCP vs 70% on first-party CSS).
Across 65,503 WordPress sites, 100.0% load first-party stylesheets (70% good LCP, 1.9s median) and 59.6% load external third-party stylesheets (68% good LCP, 2.0s median).
Shopify 8,570 stores 99.9% of Shopify stores serve first-party CSS (96% good LCP) and 78.0% load cross-origin CSS (95%).
Across 8,570 Shopify storefronts, 99.9% load first-party stylesheets (96% good LCP, 1.3s median) and 78.0% load cross-origin stylesheets (95% good LCP).
React & Next.js 9,569 sites React & Next.js sites loading third-party stylesheets (44.7%) pass LCP 7 points less often than sites on first-party CSS (78% vs 85%).
Across 9,569 React sites, 99.9% serve first-party CSS (85% good LCP, 1.4s median) and 44.7% load external third-party stylesheets (78% good LCP, 1.6s median).
By Arjen Karel · 210,902 crawled sites (196,263 with all devices Chrome field data, 198,997 sites with stylesheet origin (first-party vs third-party), October 2026). How we measured.