WordPress web font formats and the Core Web Vitals
94.7% of font-using sites (58,232) serve modern WOFF2 fonts and reach 69% good LCP (2.0s median), while the 36.6% still serving legacy WOFF (67% good LCP) and 18.3% serving uncompressed TTF (65% good LCP) lag behind.
94.7% of WordPress sites use WOFF2 fonts web font format, and 69% of those sites have a good LCP, against 70% of all WordPress sites.
LCP pass rate
Sites with WOFF2 fonts web font format have a good LCP most often: 69%, against 70% of all WordPress sites. Sites with other font formats font formats have it least often, at 63%.
Web font format usage
WOFF2 fonts is the most used: 94.7% of WordPress sites.
LCP phase breakdown by web font format
Across the four LCP sub-parts in Chrome's field data, the largest gap between WOFF2 fonts and other font formats sits in time to first byte (TTFB): 1146 ms median for WOFF2 fonts against 1302 ms for other font formats. Overall median field LCP is 2.0s for WOFF2 fonts (TTFB 1146 ms, load delay 347 ms, load duration 167 ms, render delay 238 ms) versus 2.2s for other font formats.
Web font format per framework
jQuery sets the web font format to WOFF2 fonts on 96% of its sites, and 69% of jQuery sites have a good LCP, against 70% of all sites.
Web font format or the framework
Does the framework explain the web font format difference?
Almost every site with WOFF2 fonts web font format is a jQuery site, and almost every jQuery site has WOFF2 fonts web font format, so the data can't tell WOFF2 fonts web font format and jQuery apart. On Vue, 67% of sites with WOFF2 fonts web font format have a good LCP, against 67% of Vue sites with legacy WOFF fonts. Within Vue, sites with WOFF2 fonts and legacy WOFF fonts have a good LCP about equally often. On React, 60% of sites with WOFF2 fonts web font format have a good LCP, against 58% of React sites with legacy WOFF fonts. Within React, sites with WOFF2 fonts and legacy WOFF fonts have a good LCP about equally often.
Why WOFF2 replaces legacy WOFF, TTF, and OTF across all modern browsers
WOFF2 uses custom Brotli preprocessing to compress font glyphs ~30% smaller than legacy WOFF and up to 50%+ smaller than raw TTF or OTF files, and has been supported by every major browser since 2016. Across 58,232 font-using sites (94.7%) serving WOFF2, good LCP reaches 69% (2.0s median). Sites still serving legacy WOFF (36.6%, 22,534) drop to 67% good LCP (2.0s median), and sites serving raw TTF (18.3%, 11,262) drop to 65% good LCP (2.1s median).
Understanding web font formats
Convert legacy theme icon fonts (Font Awesome, Dashicons replacements, custom theme fonts) to WOFF2-only @font-face declarations and remove .ttf and .woff fallbacks. On WordPress, 94.7% of sites serve WOFF2 (69% good LCP) while 36.6% still download legacy WOFF (67%) and 18.3% download raw TTF (65%).
By Arjen Karel · 63,295 crawled WordPress sites (60,855 with all devices Chrome field data, 61,498 sites with web font format, October 2026). How we measured.