Preloaded font count on React sites
3.0% of audited sites (288) preload 1 to 2 web fonts and reach 67% good LCP (2.1s median), whereas the 1.1% preloading 5 or more fonts drop to 74% good LCP (1.7s median).
94.8% of React sites have no preloaded font count. Of the 5.2% that do, 57% use 1 to 2 preloaded fonts, and 67% of those sites have a good LCP, against 84% of all React sites.
94.8% of React sites have no preloaded font count. Of the 5.2% that do, 57% use 1 to 2 preloaded fonts, and 87% of those sites have a good CLS, against 92% of all React sites.
Core Web Vitals pass rate
Sites with 1 to 2 preloaded fonts preloaded font count have a good LCP most often: 67%, against 84% of all React sites.
Sites with 1 to 2 preloaded fonts preloaded font count have a good CLS most often: 87%, against 92% of all React sites.
Preloaded font count usage
5.2% of React sites use preloaded font count, and 57% of those use 1 to 2 preloaded fonts.
LCP phase breakdown by number of preloaded fonts
Across the four LCP sub-parts in Chrome's field data, the largest gap between 1 to 2 preloaded fonts and 0 preloaded fonts sits in time to first byte (TTFB): 938 ms median for 1 to 2 preloaded fonts against 485 ms for 0 preloaded fonts. Overall median field LCP is 2.2s for 1 to 2 preloaded fonts (TTFB 938 ms, load delay 503 ms, load duration 164 ms, render delay 339 ms) versus 1.4s for 0 preloaded fonts.
Across the four LCP sub-parts in Chrome's field data, the largest gap between 1 to 2 preloaded fonts and 0 preloaded fonts sits in time to first byte (TTFB): 938 ms median for 1 to 2 preloaded fonts against 485 ms for 0 preloaded fonts. Overall median field LCP is 2.2s for 1 to 2 preloaded fonts (TTFB 938 ms, load delay 503 ms, load duration 164 ms, render delay 339 ms) versus 1.4s for 0 preloaded fonts.
Preloaded font count per platform
On Wix, 100% of sites use 0 preloaded fonts preloaded font count, and 94% of Wix sites have a good LCP, against 84% of all sites. On WordPress, 86% of sites use 0 preloaded fonts, and 63% of WordPress sites have a good LCP.
On Wix, 100% of sites use 0 preloaded fonts preloaded font count, and 97% of Wix sites have a good CLS, against 92% of all sites. On WordPress, 86% of sites use 0 preloaded fonts, and 88% of WordPress sites have a good CLS.
Wix 5,824 sites0 preloaded fonts 100%94%97%
WordPress 2,342 sites0 preloaded fonts 86%63%88%Font preload count or the platform
Does the platform explain the preloaded font count difference?
On WordPress, 57% of sites with 1 to 2 preloaded fonts preloaded font count have a good LCP, against 64% of WordPress sites with 0 preloaded fonts. Within WordPress, sites with 1 to 2 preloaded fonts and 0 preloaded fonts have a good LCP about equally often.
On WordPress, 88% of sites with 1 to 2 preloaded fonts preloaded font count have a good CLS, against 87% of WordPress sites with 0 preloaded fonts. Within WordPress, sites with 1 to 2 preloaded fonts and 0 preloaded fonts have a good CLS about equally often.
Why preloading 1 to 2 fonts helps LCP while preloading 5+ fonts starves the hero image
Normally the browser discovers web fonts only after downloading CSS and matching @font-face rules to DOM nodes. Preloading 1 to 2 core WOFF2 files (3.0% of sites, 288) starts font fetches immediately and lifts good LCP to 67% (2.1s median), ahead of the 94.8% with 0 font preloads (85% good LCP, 1.4s median). However, preloading 3 to 4 fonts (1.1%) drops good LCP to 70% (1.8s median), and preloading 5 or more fonts (1.1%) saturates early bandwidth and drops good LCP to 74% (1.7s median).
Understanding preloaded font count
Limit <link rel="preload" as="font" type="font/woff2" crossorigin> to at most 1 or 2 above-the-fold WOFF2 files, or consolidate weights into a single variable font file. Across all audited sites, 3.0% preload 1 to 2 fonts (67% good LCP) and 1.1% preload 5 or more (74% good LCP).
By Arjen Karel · 9,570 crawled React sites (5,488 with phone Chrome field data, October 2026). How we measured.