The trade-off behind font-display: swap
font-display: swap has become the default recommendation for web font loading because it never leaves a reader staring at invisible text. The cost is a flash of unstyled text (FOUT): the fallback face renders first, then the custom font arrives and the layout reflows. For many sites that is an acceptable price for speed.
On very slow, unstable connections, though, that price gets higher. Matt Hobbs makes the case that swap's infinite swap period can produce a frustrating experience for these users, and that font-display: fallback or even font-display: optional deserves consideration when such conditions are likely — which, for most sites, they eventually are.
If there’s one thing I’d like readers to take away from this post it’s that
font-display: swapis a very good option for users with a fast internet connection. But its infinite swap period could be frustrating for users on very slow and unstable connections. If you have users viewing your site under these conditions (I’m pretty certain you will at some point in time), then it may be worth consideringfont-display: fallbackor evenfont-display: optional.
How optional eliminates FOUT
font-display: optional removes the flash entirely. The font is either applied almost immediately or not applied at all for that page view — but it is still downloaded asynchronously. In practice this means the first visit shows the fallback, and by the next page load the font is cached and gets used.
This distinction matters: it addresses slow connections specifically, not the separate problem of users trying to minimize data usage. Those are different constraints, and the latter calls for other techniques.
The full discussion appeared in the 2020 Web Performance Calendar, which this year carried a strong lineup of articles.



