# Display-font: swap

**URL:** <https://meta.discourse.org/t/display-font-swap/170390>\
**Category:** UX\
**Created:** [November 17, 2020, 7:19pm UTC](https://meta.discourse.org/t/display-font-swap/170390 "2020-11-17T19:19:10Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![awesomerobot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/awesomerobot/32/142900_2.png) [@awesomerobot](https://meta.discourse.org/u/awesomerobot)\
**Post date:** [November 17, 2020, 8:07pm UTC](https://meta.discourse.org/t/display-font-swap/170390/2 "2020-11-17T20:07:58Z")

</div>

`font-display: swap;` impacts the block and swap time when waiting for a font to load, but we’re including the font from the backend (we have a separate [discourse-fonts gem](https://github.com/discourse/discourse-fonts) — doing it this way eliminates making a call to Google and being tracked).

So because fonts are included as part of the Discourse application on initial load, I don’t think we’d see any benefit because fonts aren’t holding up rendering like they would be if we were calling out to Google (or another CDN) in our CSS.

Using `font-display: swap;` is still probably good advice for anyone adding custom fonts from a third-party CDN in a theme though.

---

_[View the full topic](https://meta.discourse.org/t/display-font-swap/170390)._