Web font file count on React sites
26.6% of audited sites (2,542) load 1 to 3 font files and pass LCP at 83% (1.4s median), while the 30.4% loading 7 or more font files drop to 72% (1.7s median).
26.6% of React sites use 1 to 3 font files web font file count, and 83% of those sites have a good LCP, against 79% of all React sites.
41.6% of React sites use 4 to 6 font files web font file count, and 81% of those sites have a good CLS, against 80% 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: 83%, against 79% of all React sites. Sites with 7 or more font files font count have it least often, at 72%.
Sites with 4 to 6 font files web font file count have a good CLS most often: 81%, against 80% of all React sites. Sites with 1 to 3 font files font count have it least often, at 79%.
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): 575 ms median for 1 to 3 font files against 956 ms for 7 or more font files. Overall median field LCP is 1.5s for 1 to 3 font files (TTFB 575 ms, load delay 414 ms, load duration 133 ms, render delay 173 ms) versus 1.8s 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): 575 ms median for 1 to 3 font files against 956 ms for 7 or more font files. Overall median field LCP is 1.5s for 1 to 3 font files (TTFB 575 ms, load delay 414 ms, load duration 133 ms, render delay 173 ms) versus 1.8s 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 92% of Wix sites have a good LCP, against 79% of all sites. On WordPress, 41% of sites use 7 or more font files, and 66% of WordPress sites have a good LCP.
On Wix, 46% of sites use 4 to 6 font files web font file count, and 96% of Wix sites have a good CLS, against 80% of all sites. On WordPress, 41% of sites use 7 or more font files, and 75% 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 94% 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 69% 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 LCP about equally often.
On Wix, 95% of sites with 4 to 6 font files web font file count have a good CLS, against 96% of Wix sites with 7 or more font files. Within Wix, sites with 4 to 6 font files and 7 or more font files have a good CLS about equally often. On WordPress, 73% of sites with 4 to 6 font files web font file count have a good CLS, against 77% of WordPress sites with 7 or more font files. Within WordPress, sites with 4 to 6 font files and 7 or more 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, 83% pass field LCP at a 1.4s median, compared with 72% (1.7s 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 (83% good LCP, 1.4s median) versus 30.4% loading 7+ fonts (72% good LCP, 1.7s median).
By Arjen Karel · 9,570 crawled React sites (1,979 with desktop Chrome field data, October 2026). How we measured.