Web font file count on React sites
26.6% of audited sites (2,542) load 1 to 3 font files and pass LCP at 88% (1.3s median), while the 30.4% loading 7 or more font files drop to 78% (1.6s median).
26.6% of React sites use 1 to 3 font files web font file count, and 88% of those sites have a good LCP, against 84% of all React sites.
26.6% of React sites use 1 to 3 font files web font file count, and 93% of those sites have a good CLS, against 92% of all React sites.
Core Web Vitals pass rate
Sites with 1 to 3 font files web font file count have a good LCP most often: 88%, against 84% of all React sites. Sites with 7 or more font files font count have it least often, at 78%.
Sites with 1 to 3 font files web font file count have a good CLS most often: 93%, against 92% of all React sites. Sites with 4 to 6 font files font count have it least often, at 91%.
Web font file count usage
4 to 6 font files is the most used: 41.6% of React sites. 1 to 3 font files is 26.6% of React sites.
The four LCP phases
Across the four LCP sub-parts in Chrome's field data, the largest gap between 1 to 3 font files and 7 or more font files sits in time to first byte (TTFB): 475 ms median for 1 to 3 font files against 598 ms for 7 or more font files. Overall median field LCP is 1.3s for 1 to 3 font files (TTFB 475 ms, load delay 411 ms, load duration 123 ms, render delay 170 ms) versus 1.6s for 7 or more font files.
Across the four LCP sub-parts in Chrome's field data, the largest gap between 1 to 3 font files and 7 or more font files sits in time to first byte (TTFB): 475 ms median for 1 to 3 font files against 598 ms for 7 or more font files. Overall median field LCP is 1.3s for 1 to 3 font files (TTFB 475 ms, load delay 411 ms, load duration 123 ms, render delay 170 ms) versus 1.6s for 7 or more font files.
Web font file count per platform
On Wix, 46% of sites use 4 to 6 font files web font file count, and 94% of Wix sites have a good LCP, against 84% of all sites. On WordPress, 41% of sites use 7 or more font files, and 63% of WordPress sites have a good LCP.
On Wix, 46% of sites use 4 to 6 font files web font file count, and 97% of Wix sites have a good CLS, against 92% of all sites. On WordPress, 41% of sites use 7 or more font files, and 88% of WordPress sites have a good CLS.
Web font file count or the platform
Does the platform explain the web font file count difference?
On Wix, 95% of sites with 1 to 3 font files web font file count have a good LCP, against 95% of Wix sites with 4 to 6 font files. Within Wix, sites with 1 to 3 font files and 4 to 6 font files have a good LCP about equally often. On WordPress, 75% of sites with 1 to 3 font files web font file count have a good LCP, against 65% of WordPress sites with 4 to 6 font files. Within WordPress, sites with 1 to 3 font files have a good LCP more often.
On Wix, 98% of sites with 1 to 3 font files web font file count have a good CLS, against 97% of Wix sites with 4 to 6 font files. Within Wix, sites with 1 to 3 font files and 4 to 6 font files have a good CLS about equally often. On WordPress, 88% of sites with 1 to 3 font files web font file count have a good CLS, against 88% of WordPress sites with 4 to 6 font files. Within WordPress, sites with 1 to 3 font files and 4 to 6 font files have a good CLS about equally often.
How font proliferation delays text and hero rendering
Each font weight and style is a high-priority download that competes with hero images and triggers layout recalculations when late-arriving faces swap in. Across 2,542 sites (26.6%) loading 1 to 3 font files, 88% pass field LCP at a 1.3s median, compared with 78% (1.6s median) across the 30.4% (2,906) loading 7+ font files.
Understanding web font file count
Limit pages to 1 to 3 WOFF2 font files (or use variable fonts) and drop unused weights, italic variants, and decorative icon fonts. Across all audited sites, 26.6% load 1 to 3 fonts (88% good LCP, 1.3s median) versus 30.4% loading 7+ fonts (78% good LCP, 1.6s median).
By Arjen Karel · 9,570 crawled React sites (5,488 with phone Chrome field data, October 2026). How we measured.