Wix font-display and the Core Web Vitals

swap, auto, block, fallback, or optional across 310,546 @font-face rules: how sites mix font-display rules on the same page and how that affects LCP and CLS.

Field data PhoneDesktopAll Scope All sites October 2026 edition · All devices field outcomes · Wix sites only
Wix Scoped to 5,623 sites out of 203,892 analyzed (cms) Compare with all sites →

Across Wix sites, 98.6% of all 310,546 declared @font-face rules set font-display: swap, while 1.1% leave it at auto. Most sites load more than one font stylesheet, so 99.9% of Wix sites have at least one swap rule and 1.5% have at least one block rule. Sites that keep every font on swap or optional have a good LCP on 95% of sites, against 100% for blocking-only sites and 88% for sites that mix swap with block or auto.

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field data · 5,619 sites with font-displayBy Arjen Karel · corewebvitals.io/state-of-cwv
1

Core Web Vitals pass rate

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 94%, auto at 88%. Why does swap (94%) 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.

SitesGood, needs improvement, poor LCPMedian
All Wix sites5,33394%1.2s
fallback <0.1%2100%1.1s
optional <0.1%1100%2.3s
swap 99.9%5,32794%1.2s
auto (browser default) 14.2%78188%1.4s
block 1.5%7981%1.5s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field data · 5,619 sites with font-displayBy Arjen Karel · corewebvitals.io/state-of-cwv
2

Font-display usage

Across 5,619 Wix sites that declare web fonts, swap accounts for 98.6% of all @font-face rules, auto for 1.1%, block for 0.3%, fallback for , and optional for . At the site level, 15.1% of sites mix swap with blocking rules on the same page, 0.1% use only blocking rules (auto, block, or fallback), and 84.8% use swap or optional on every font rule.

All declared @font-face rules 310,546 rules
swap 98.6%
swap 98.6% auto (browser default) 1.1% block 0.3% fallback <0.1% optional <0.1%
Sites with web fonts by site mix (non-overlapping) 5,619 sites
Only swap or optional 84.8%Mixed (swap + blocking on same page) 15.1%
Only swap or optional 84.8% Only blocking (auto, block, fallback) 0.1% Mixed (swap + blocking on same page) 15.1%
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field data · 5,619 sites with font-displayBy Arjen Karel · corewebvitals.io/state-of-cwv
3

Pass rate by site-wide font-display mix

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 95% of sites, against 100% for blocking-only sites and 88% for mixed sites. Mixed sites load a median of 6 font files across 56 @font-face rules (usually Google Fonts plus Font Awesome or theme icon fonts). Pure swap sites load a median of 5 font files across 41 rules.

Site font mixSitesGood, needs improvement, poor LCPMedian
All Wix sites5,33394%1.2s
Only swap or optional 84.8% · 5 fonts4,50095%1.2s
Only blocking (auto, block, fallback) 0.1% · 3 fonts4100%1.3s
Mixed (swap + blocking on same page) 15.1% · 6 fonts82788%1.4s
GoodNeeds improvementPoor
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field data · 5,619 sites with font-displayBy Arjen Karel · corewebvitals.io/state-of-cwv
4

font-display pass rate by number of font files

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 96% of sites, against 80% for sites with any block rule. On pages loading 8 or more font files, pure swap reaches 94% against 79% for sites with block.

Downloaded font files Only swap / optional Auto or fallback (no block) Includes font-display: block
1 to 2 font files
96% 1.1s median 580 sites
87% 1.3s median 55 sites
few sites
3 to 4 font files
96% 1.1s median 1,671 sites
88% 1.4s median 183 sites
few sites
5 to 7 font files
96% 1.2s median 1,738 sites
91% 1.4s median 328 sites
76% 1.5s median 35 sites
8 or more font files
94% 1.2s median 758 sites
84% 1.5s median 202 sites
79% 1.8s median 29 sites
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field data · 5,619 sites with font-displayBy Arjen Karel · corewebvitals.io/state-of-cwv
5

Font-display per framework

On React, 99% of declared @font-face rules use font-display: swap, 1% use auto, and 0% use block. 94% of React sites have a good LCP.

Framework@font-face rules on its sitesGood LCP
Wix sites with font-display 5,619 sitesswap 99%94%
React 5,618 sitesswap 99%94%
swap auto (browser default) block fallback optional
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field data · 5,619 sites with font-displayBy Arjen Karel · corewebvitals.io/state-of-cwv
6

font-display or the framework

Does the framework explain the font-display gap?

On React, 95% of sites that keep every font on swap or optional have a good LCP, compared with 100% for blocking-only sites and 88% for React sites that mix swap with blocking rules. Within React, keeping every font on swap beats mixing rules by 7 percentage points.

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 (98% good CLS).

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field data · 5,619 sites with font-displayBy Arjen Karel · corewebvitals.io/state-of-cwv
7

Understanding font-display

Set font-display: swap or font-display: optional on every @font-face rule, and check third-party icon stylesheets for leftover font-display: block rules. Across this dataset, 15.1% of sites mix rules on the same page because they load Google Fonts with display=swap alongside Font Awesome or theme icon fonts set to block or auto. At the same font file count, sites that keep every font on swap beat sites with any block rule by 15 to 20 percentage points on LCP. They do not lose a single point on CLS. Pair font-display: swap with size-adjust, ascent-override, and descent-override on body text fonts so the swap does not shift layout.

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field data · 5,619 sites with font-displayBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals Stylesheet origin (1P/3P) → CSS coverage (used vs unused) → Image format mix → Fonts per page → By Arjen Karel · 5,621 crawled Wix sites (5,333 with all devices Chrome field data, 5,619 sites with font-display, October 2026) · How we measured