font-display on React sites

Here, a site counts under every font-display value present in its @font-face rules. Sites with at least one matching rule have a good LCP: swap at 85%, auto at 72%, fallback at 69%, block at 63%. Why does swap (85%) sit right next to auto (72%)? Three in four sites that load Google Fonts with swap also load icon or theme fonts with block or auto. Those multi-font pages count under both values.

Here, a site counts under every font-display value present in its @font-face rules. Sites with at least one matching rule have a good CLS: swap at 92%, auto at 88%, block at 85%, fallback at 84%. Why does swap (92%) sit right next to auto (88%)? Three in four sites that load Google Fonts with swap also load icon or theme fonts with block or auto. Those multi-font pages count under both values.

Across 9,533 React sites that declare web fonts, swap accounts for 71.3% of all @font-face rules, auto for 21.9%, block for 6.3%, fallback for 0.4%, and optional for 0.1%. At the site level, 32.9% of sites mix swap with blocking rules on the same page, 8.5% use only blocking rules (auto, block, or fallback), and 58.6% use swap or optional on every font rule.

When each site is counted once by its full rule mix, sites that keep every font on swap or optional have a good LCP on 93% of sites, against 74% for blocking-only sites and 72% for mixed sites. Mixed sites load a median of 6 font files across 59 @font-face rules (usually Google Fonts plus Font Awesome or theme icon fonts). Pure swap sites load a median of 5 font files across 39 rules.

When each site is counted once by its full rule mix, sites that keep every font on swap or optional have a good CLS on 95% of sites, against 87% for blocking-only sites and 88% for mixed sites. Mixed sites load a median of 6 font files across 59 @font-face rules (usually Google Fonts plus Font Awesome or theme icon fonts). Pure swap sites load a median of 5 font files across 39 rules.

Comparing sites that load the same number of font files separates font-display from font count. With 1 to 2 font files, sites on pure swap have a good LCP on 92% of sites, against 70% for sites with any block rule. On pages loading 8 or more font files, pure swap reaches 91% against 56% for sites with block.

Comparing sites that load the same number of font files separates font-display from font count. With 1 to 2 font files, sites on pure swap have a good CLS on 94% of sites, against 83% for sites with any block rule. On pages loading 8 or more font files, pure swap reaches 97% against 84% for sites with block. At every font count, pure swap matches or beats block on field CLS.

On Wix, 99% of declared @font-face rules use font-display: swap, 1% use auto, and 0% use block. 94% of Wix sites have a good LCP. On WordPress, 49% of rules use swap, 39% use auto, and 11% use block, and 63% of WordPress sites have a good LCP.

On Wix, 99% of declared @font-face rules use font-display: swap, 1% use auto, and 0% use block. 97% of Wix sites have a good CLS. On WordPress, 49% of rules use swap, 39% use auto, and 11% use block, and 88% of WordPress sites have a good CLS.

Platform@font-face rules on its sitesGood LCP

React sites with font-display 9,533 sitesswap 71%auto (browser default) 22%84%

Wix 5,822 sitesswap 99%94%

WordPress 2,333 sitesswap 49%auto (browser default) 39%block 11%63%

swap auto (browser default) block fallback optional

Does the platform explain the font-display gap?

On Wix, 95% of sites that keep every font on swap or optional have a good LCP, compared with 100% for blocking-only sites and 90% for Wix sites that mix swap with blocking rules. Within Wix, keeping every font on swap beats mixing rules by 5 percentage points. On WordPress, 72% of sites that keep every font on swap or optional have a good LCP, compared with 71% for blocking-only sites and 59% for WordPress sites that mix swap with blocking rules. Within WordPress, keeping every font on swap beats mixing rules by 13 percentage points.

On Wix, 98% of sites that keep every font on swap or optional have a good CLS, compared with 100% for blocking-only sites and 96% for Wix sites that mix swap with blocking rules. Within Wix, pure swap and mixed sites have a good CLS about equally often. On WordPress, 88% of sites that keep every font on swap or optional have a good CLS, compared with 91% for blocking-only sites and 86% for WordPress sites that mix swap with blocking rules. Within WordPress, pure swap and mixed sites have a good CLS about equally often.

How font-display affects LCP and CLS during page load

When text is the LCP element, font-display: block and font-display: auto hide it for up to 3 seconds while the font file downloads. If the font arrives late, that wait delays LCP directly. With font-display: swap, the browser paints the fallback system font right away so LCP is recorded on first render, then swaps in the web font once it downloads. Swapping an unadjusted fallback font can shift text lines. Even so, pure swap sites match or beat blocking sites on field CLS at every font count (95% good CLS).