Custom font integration in Tailwind - Performance & Optimization

Performance: Custom font integration

MEDIUM IMPACT

This affects page load speed and visual stability by controlling how fonts load and render on the page.

Adding a custom font to a Tailwind CSS project

Tailwind

@font-face { font-family: 'MyFont'; src: url('/fonts/myfont.woff2') format('woff2'); font-display: swap; }

font-display: swap shows fallback text immediately and swaps in the custom font when ready, reducing invisible text and layout shifts.

📈 Performance GainImproves LCP and reduces CLS by avoiding invisible text and layout shifts.

Adding a custom font to a Tailwind CSS project

Tailwind

@font-face { font-family: 'MyFont'; src: url('/fonts/myfont.woff2') format('woff2'); font-display: auto; }

Using font-display: auto delays text rendering until the font loads, causing invisible text and layout shifts.

📉 Performance CostBlocks text rendering, increasing LCP and causing CLS due to layout shifts.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
font-display: auto	Minimal	Multiple reflows on font swap	High paint cost due to invisible text and repaint	[X] Bad
font-display: swap	Minimal	Single reflow on font swap	Lower paint cost with immediate fallback text	[OK] Good

Rendering Pipeline

The browser downloads the font file during the critical rendering path. font-display controls when text is painted with fallback or custom fonts, affecting layout stability and paint timing.

→Style Calculation

→Layout

→Paint

→Composite

⚠️ BottleneckPaint stage is most expensive due to delayed text rendering and repaints when font swaps.

Core Web Vital Affected

LCP

This affects page load speed and visual stability by controlling how fonts load and render on the page.

Optimization Tips

1Use font-display: swap to avoid invisible text and reduce layout shifts.

2Preload custom fonts to start downloading early and improve LCP.

3Avoid font-display: auto as it delays text rendering and causes CLS.

Performance Quiz - 3 Questions

Which font-display value helps reduce invisible text during font loading?

A swap

B auto

C block

D fallback

DevTools: Performance

How to check: Record a page load and look for 'Layout Shift' events and 'Text Paint' timings in the flame chart.

What to look for: Check if text is invisible initially and if layout shifts occur when fonts load, indicating poor font-display usage.

Practice

1. What is the main purpose of using @font-face in Tailwind CSS when integrating a custom font?

easy

A. To load and define a custom font so it can be used in your styles

B. To create animations for text using the font

C. To automatically download fonts from Google Fonts

D. To change the font size of text elements

Solution

1. Step 1: Understand the role of @font-face

   @font-face is a CSS rule that lets you load a custom font file into your website.

2. Step 2: Connect @font-face to Tailwind usage

   After loading the font with @font-face, you extend Tailwind's fontFamily to use that font in your classes.

3. Final Answer:

   To load and define a custom font so it can be used in your styles -> Option A

4. Quick Check:

   @font-face loads fonts = D [OK]

Hint: Remember: @font-face loads fonts, not styles [OK]

Common Mistakes:

• Thinking @font-face changes font size
• Confusing font loading with animations
• Assuming it downloads fonts automatically

2. Which of the following is the correct way to extend Tailwind's fontFamily in tailwind.config.js to add a custom font named 'MyFont'?

easy

A. fontFamily: { myfont: 'MyFont' }

B. fontFamily: { 'MyFont': ['custom', 'sans-serif'] }

C. fontFamily: { custom: ['MyFont', 'sans-serif'] }

D. fontFamily: { custom: 'MyFont', fallback: 'sans-serif' }

Solution

1. Step 1: Recall Tailwind fontFamily syntax

   Tailwind expects font families as arrays with font names and fallbacks, e.g., fontFamily: { key: ['FontName', 'fallback'] }.

2. Step 2: Match correct syntax

   fontFamily: { custom: ['MyFont', 'sans-serif'] } correctly uses custom as key and an array with 'MyFont' and 'sans-serif'. Others misuse keys or values.

3. Final Answer:

   fontFamily: { custom: ['MyFont', 'sans-serif'] } -> Option C

4. Quick Check:

   fontFamily uses arrays for fonts = C [OK]

Hint: Use arrays for font names and fallbacks in config [OK]

Common Mistakes:

• Using strings instead of arrays for fontFamily
• Swapping keys and values
• Missing fallback fonts

3. Given this Tailwind config extension:

fontFamily: { custom: ['MyFont', 'sans-serif'] }

and this HTML:

<p class="font-custom">Hello</p>

What font will the paragraph use if 'MyFont' is loaded correctly?

medium

A. No font, text will be invisible

B. The browser default font

C. 'sans-serif' fallback font only

D. 'MyFont' custom font

Solution

1. Step 1: Understand class usage

   The class font-custom applies the font family named 'custom' from Tailwind config.

2. Step 2: Check font loading

   If 'MyFont' is loaded correctly via @font-face, it will be used first, with 'sans-serif' as fallback.

3. Final Answer:

   'MyFont' custom font -> Option D

4. Quick Check:

   font-custom uses 'MyFont' if loaded = A [OK]

Hint: font-custom uses your custom font if loaded properly [OK]

Common Mistakes:

• Assuming fallback font is always used
• Confusing class name with default fonts
• Thinking text disappears without font

4. You added this to your CSS:

@font-face { font-family: 'MyFont'; src: url('/fonts/MyFont.woff2'); }

But your text with font-custom class still shows default font. What is the likely mistake?

medium

A. You used the wrong font file format

B. You forgot to extend fontFamily in tailwind.config.js

C. You applied the wrong Tailwind class name

D. You did not include the font file in your HTML

Solution

1. Step 1: Check font-face usage

   The font is loaded with @font-face, so the font file is available.

2. Step 2: Verify Tailwind config

   Without extending fontFamily in tailwind.config.js, the class font-custom won't apply the new font.

3. Final Answer:

   You forgot to extend fontFamily in tailwind.config.js -> Option B

4. Quick Check:

   fontFamily extension missing = B [OK]

Hint: Always extend fontFamily to use custom fonts in Tailwind [OK]

Common Mistakes:

• Not extending fontFamily in config
• Using wrong class names
• Forgetting to rebuild Tailwind after config change

5. You want to use two custom fonts, 'MyFontBold' and 'MyFontLight', in Tailwind. How should you configure tailwind.config.js and your CSS to use font-boldcustom and font-lightcustom classes for them?

hard

A. Define two @font-face rules with different font-family names and extend fontFamily with keys 'boldcustom' and 'lightcustom' pointing to those fonts

B. Use one @font-face with both fonts and extend fontFamily with a single key

C. Only extend fontFamily once and use CSS font-weight to switch fonts

D. Add both fonts in one @font-face and use font-custom class for both

Solution

1. Step 1: Define separate @font-face rules

   Each font variant needs its own @font-face with unique font-family names like 'MyFontBold' and 'MyFontLight'.

2. Step 2: Extend Tailwind's fontFamily

   In tailwind.config.js, add keys 'boldcustom' and 'lightcustom' pointing to these font-family names so you can use font-boldcustom and font-lightcustom classes.

3. Final Answer:

   Define two @font-face rules and extend fontFamily with 'boldcustom' and 'lightcustom' -> Option A

4. Quick Check:

   Separate font-faces + fontFamily keys = A [OK]

Hint: Use separate font-family names and keys for each font variant [OK]

Common Mistakes:

• Trying to combine fonts in one @font-face
• Using CSS font-weight instead of separate font-family
• Not extending fontFamily for each font variant