How to Optimize WordPress Fonts Without Hurting LCP or CLS

Fonts can make a WordPress site feel polished, but every font file adds work. A site that loads several families, many weights, icon fonts, and third-party font CSS can delay text, increase page weight, and cause layout movement.

The fastest font setup is usually the simplest one that still fits the design. Start by finding which font files the page really downloads. Then remove unused families and weights before trying advanced preload tricks.

Count the font files first

Open the Network panel in your browser and filter by Font. Reload the page. You may be surprised by what appears. A theme can load regular, medium, semibold, bold, italic, and several icon files even when the page only uses two of them.

Also check the Initiator or request chain. A remote stylesheet may request the fonts. A page builder may add another family. A form plugin or icon library can add more. If you only look at the WordPress Customizer, you may miss files added by plugins.

Record the font family, weight, style, file size, source, and where it is used. This gives you a list you can reduce.

Use fewer families and weights

For many sites, one body family and one heading family are enough. Often one family can handle both. You may only need normal text and one bold weight. Each extra variant should have a clear job.

A common mistake is loading 300, 400, 500, 600, 700, and 800 because a design system offers them. If the CSS only uses 400 and 700, the rest are wasted requests. Remove the unused files at the theme or plugin setting that added them.

System fonts are another strong option. They use fonts already available on the visitor’s device, so the page does not need to download a web font for normal text. FastWP.info uses a system-font stack for this reason.

Prefer WOFF2 for normal web delivery

WOFF2 is widely used for web fonts because it is designed for efficient web delivery. If a service or theme still sends older formats to modern browsers without a good compatibility reason, review the configuration.

Do not convert a font you do not have the right to modify or self-host. Font licenses differ. Some permit web use but require the files to come from an approved service. Others allow self-hosting. Check the license before moving or converting font files.

Understand font-display

The font-display descriptor controls how text behaves while a web font is loading. A value such as swap lets fallback text appear first and then swaps to the web font when it is ready. This avoids a long blank-text period, but the change in font metrics can cause a visible shift.

There is no one setting that is best for every design. The goal is readable text with as little layout movement as practical. Test the actual page on a cold load, especially on a slower connection.

If the fallback font is much wider or narrower than the final font, the swap can move headings and buttons. That can affect Cumulative Layout Shift. Choose a fallback with similar metrics when possible.

Do not preload every font

Preload gives a resource high early importance. That can help a font used immediately in the first viewport, but too many preloads compete with CSS, the main image, and other critical files. A preload also wastes bandwidth if the font is not used on the current page.

Start with no font preload. Measure the request chain. If one local font file used above the fold is discovered late and clearly delays text or LCP, test preloading that specific file. Make sure the URL, type, and crossorigin behavior match the final request so the browser can reuse the preload.

If your LCP element is an image, giving three fonts priority can make that image arrive later. Review WordPress LCP optimization before adding several high-priority hints.

Self-hosting can help, but it is not magic

Self-hosting a font can remove an extra third-party connection and give you control over caching headers and file selection. It can also support privacy goals in some regions. But a badly configured local setup with ten font files can still be slower than a simple remote setup.

If you self-host, keep the files on a fast origin or CDN, use long-lived cache headers for versioned files, and load only the variants you use. A WordPress CDN can help global visitors fetch static font files from a nearby edge when the configuration permits it.

Remove duplicate Google Fonts requests

WordPress sites often get duplicate font requests when the theme loads Google Fonts and a page builder loads the same family again. A form, popup tool, or block library may also request its own family.

View the page source and Network panel. If the same family comes from several stylesheets, choose one owner. Disable the extra font controls in the theme or plugin. This is safer than trying to hide duplicate requests after they have already been queued.

If you keep remote Google Fonts, the browser may need to connect to more than one Google host before it receives the file. Connection hints can sometimes help, but deleting an unnecessary family helps more.

Icon fonts deserve an audit too

An icon font can contain hundreds of symbols when the page only displays a search icon and one social icon. That is easy to overlook because the file may be smaller than a photo, yet it still adds CSS, a font request, and rendering work.

Inline SVG or a small SVG sprite can be a better choice for a small icon set. Do not replace a working icon system only for a tiny theoretical gain, but remove a large library when it exists for two simple icons.

Fonts, render blocking, and CSS

The browser often learns about a font after it downloads and parses a stylesheet containing @font-face. If that stylesheet is late, the font is late too. A huge render-blocking CSS file can therefore make font loading look like a font problem.

Check the full dependency chain. Our guide to reducing render-blocking files explains how to remove or defer assets without breaking the page.

Be careful with “remove Google Fonts” plugins

A plugin that blocks a remote font request can be useful when you intentionally want system fonts or local files. But blocking the request without changing the CSS may leave the design on an accidental fallback. Headings can wrap differently, buttons can change size, and the page can shift.

Make the font decision in the theme or builder when possible. Then use a blocking plugin only when you need it to stop a component you cannot otherwise control.

A practical font optimization order

  1. List every font request on an important page.
  2. Remove unused families, weights, styles, and icon fonts.
  3. Choose whether system fonts, local web fonts, or a remote service fits the site.
  4. Use an efficient format such as WOFF2 where licensing and browser support allow.
  5. Set a sensible font-display behavior and test layout movement.
  6. Preload only a truly critical font if measurement shows it helps.
  7. Check mobile, desktop, cached, and cold-load behavior.

After the font cleanup, rerun your normal speed tests. Look at LCP, CLS, transferred bytes, and the request waterfall. A smaller font setup should make the page simpler, not merely change one Lighthouse recommendation.

Subset fonts only when the savings are real

Some font files contain characters for many writing systems. A subset can reduce the file size when your site only needs a smaller character range. This can be useful, but it needs care. A bad subset can remove punctuation, currency symbols, accented letters, or characters that appear later in user names and translated content.

Use a subset supplied by the font provider when possible. If you create one yourself, keep the original licensed files and test the full character set your site may display. For a multilingual site, separate language subsets may add complexity that is not worth a small saving.

Test the first uncached visit

Fonts can look fast after the browser has cached them. Use a private window or clear the relevant browser cache when you test the first visit. Then test again with cache warm. Both experiences matter: the cold load shows discovery and transfer cost, while repeat visits show whether caching is working.

Sources and further reading

Related FastWP guides