Course contentsShow
← Web Development
Lesson 1295 of 2,98223. Web Font OptimizationFree lesson

When to Preload Fonts vs When Not To

Identifying critical fonts worth preloading and avoiding over-preloading.

When to Preload Fonts vs When Not To

You'll learn how to decide which fonts deserve preloading priority and when preloading actually hurts performance.


The Preloading Paradox

Just because you can preload fonts doesn't mean you should preload all of them. Think of browser preloading like a VIP fast-pass at an amusement park: if you give everyone a fast-pass, nobody actually gets priority, and you've just created expensive overhead.

When to Preload Fonts

Preload fonts that are:

  1. Critical and above-the-fold — Your main heading font that appears immediately when the page loads
  2. Used for primary content — Body text fonts that cover most of your visible text
  3. Self-hosted — You control the file, so the browser can fetch it early (not for Google Fonts or third-party CDNs in most cases)
  4. Small in file size — Subsetted or variable fonts that won't block other critical resources

When NOT to Preload Fonts

Avoid preloading fonts that are:

  1. Below the fold — Fonts used in footers, comments, or sections users won't see immediately
  2. Decorative or rare — Special fonts used only in small UI elements
  3. Numerous — Preloading 5+ font files creates resource congestion
  4. Already loaded — System fonts (Arial, Georgia) need no preloading
  5. Non-critical — Icon fonts or fonts paired with font-display: optional

The Rule of Two

A practical guideline: preload at most 1-2 fonts — typically your primary heading and body text fonts. Anything beyond that likely delivers diminishing returns and delays other important resources like CSS and JavaScript.

Key Takeaway: Preload only the most critical, above-the-fold, self-hosted fonts; over-preloading creates resource competition that slows down your entire page.