Font optimization for WordPress
WP Core Web Vitals lets your text and images load before the icon font, and can take Google Fonts and Adobe Fonts off the page once you host your fonts yourself.

What can a WordPress plugin do about slow web fonts?
Keep the fonts your visitor doesn't need yet out of the way. An icon font downloads next to your hero image for a few arrows and a cart icon: the solid icons of Font Awesome 6.7 alone are a 158 kB file. Google Fonts first need a connection to another server. WP Core Web Vitals shows the icons a moment later and, once your fonts are on your own server, can remove the Google Fonts and Adobe Fonts links.
Built on the load order
Everything the browser fetches at the start of a page competes with your LCP image and the font of your text. The plugin hides the icons at first. A hidden icon doesn't need its font yet, so the icon font stays out of the way of your text fonts and images at the start of the page.
Fonts you host yourself come from your own domain, over the connection the page already has.
The font settings

Faster text rendering
Asks the browser to draw your text the quick way, with text-rendering: optimizeSpeed. Depending on the browser, it then skips ligatures (fi drawn as one glyph) and kerning (the fine spacing between letter pairs such as AV). In body text you'll hardly see the difference. Turn it off when your logo or headings use a font whose ligatures are part of the look. On
Remove Google Fonts and Adobe Fonts
Takes the Google Fonts and Adobe Fonts (Typekit) links and scripts out of your pages, whichever theme or plugin added them. With your fonts on your own server, they come over the connection the page already has, so your text font starts downloading sooner. Turn it on once the font files and their @font-face rules are on your server, or your visitors get fallback fonts. An @import of Google Fonts inside the theme's CSS stays, so remove that in the theme. Fonts from Adobe Fonts need a web license from the font's foundry before you host them yourself. Off
Fine-tuning

- Show icon fonts a moment later (On): keeps an icon font such as Font Awesome (158 kB for its solid icons in version 6.7) from downloading at the start of the page, next to your LCP image and the font of your text. The browser only fetches a font for text it shows, so the plugin hides the icons until the HTML is parsed and the deferred scripts have run. Hidden icons take no space: give the button or menu item around them a fixed size, or the page shifts (CLS) when they appear. Turn it off when an icon is the first thing people need, such as a hamburger menu that is the only control on a phone.
- Icon selectors: the CSS selectors of the icons to hold back, comma separated, such as .icon, .menu-icon. The plugin always adds
.faand.fas. Font Awesome 6 and 7 also use.fa-solid,.fa-regularand.fa-brands(or.farand.fab), so add the ones your theme uses. If the icon font still shows up among the first requests in the Network panel of DevTools, look for icons with a class that isn't on the list yet.
When to leave icons and Google Fonts alone
An icon that is the first thing people see, such as a logo built from an icon font or a hamburger menu that is the only control on a phone, shouldn't appear late. When it has your own class, leave that class out of the icon selectors; a .fa or .fas icon is always held back, so for that one turn the setting off. Sites with SVG icons don't need the setting.
Remove Google Fonts and Adobe Fonts on a theme without self-hosted fonts just gives you system fonts: fine for speed, but your designer will notice. Whether text waits for its font or shows a fallback first is up to the font-display in the @font-face rules of your fonts; the plugin doesn't change it.
Questions about web fonts in WordPress
Does the plugin host Google Fonts locally for me?
No, you host the files yourself. Download them (WOFF2 is enough), upload them to your theme and add the @font-face rules, then turn on Remove Google Fonts and Adobe Fonts. Self-host Google Fonts shows how.
Should I preload my fonts?
Yes, the one or two fonts of the text in the first screen, under Resource hints. The browser only asks for a font once the CSS is parsed and text needs it; a preload starts the download sooner, and the plugin adds the crossorigin it needs. Not every weight and style: fonts load at high priority, so each extra preload takes bandwidth from your LCP image.
Which font-display should I use?
Swap for brand fonts with a matched fallback, optional for body text when a system font will do. Font display in Lighthouse explains the choice.
The background: a device-aware font loading strategy.