Font optimization and self-hosting in NextJS - Performance & Optimization

Performance: Font optimization and self-hosting

HIGH IMPACT

This affects page load speed by reducing font file download time and rendering delays caused by font loading.

Loading custom fonts in a Next.js app

NextJS

import localFont from 'next/font/local';

const roboto = localFont({
  src: './fonts/roboto-regular.woff2',
  display: 'swap'
});

export default function App({ Component, pageProps }) {
  return <main className={roboto.className}>
    <Component {...pageProps} />
  </main>;
}

Self-hosting font files eliminates external requests and using font-display: swap avoids blocking text rendering.

📈 Performance GainReduces blocking time by 100-300ms; prevents layout shifts improving LCP and CLS

Loading custom fonts in a Next.js app

NextJS

import '../styles/globals.css';
// CSS imports Google Fonts via @import url('https://fonts.googleapis.com/css2?family=Roboto&display=swap');

export default function App({ Component, pageProps }) {
  return <Component {...pageProps} />;
}

Loading fonts via external Google Fonts CSS causes render-blocking requests and delays text rendering until fonts load.

📉 Performance CostBlocks rendering for 100-300ms depending on network; triggers layout shifts when fonts load

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
External Google Fonts CSS	No extra DOM nodes	Triggers reflow on font swap	High paint cost on font load	[X] Bad
Self-hosted fonts with font-display: swap	No extra DOM nodes	Single reflow on initial load	Low paint cost, smooth swap	[OK] Good

Rendering Pipeline

Fonts are requested during the critical rendering path. External fonts block text rendering until downloaded and parsed. Self-hosted fonts with font-display: swap allow text to render immediately with fallback fonts, then swap in custom fonts without blocking layout.

→Network Request

→Style Calculation

→Layout

→Paint

⚠️ BottleneckNetwork Request and Style Calculation due to font loading and applying styles

Core Web Vital Affected

LCP

This affects page load speed by reducing font file download time and rendering delays caused by font loading.

Optimization Tips

1Always self-host critical fonts to reduce external network delays.

2Use font-display: swap to avoid blocking text rendering and reduce layout shifts.

3Preload key font files to prioritize font loading in the critical rendering path.

Performance Quiz - 3 Questions

What is the main performance benefit of self-hosting fonts in a Next.js app?

A Reduces external network requests and improves font load speed

B Automatically compresses fonts to smaller sizes

C Eliminates the need for font-display CSS property

D Allows fonts to load only after user interaction

DevTools: Performance

How to check: Record a page load in DevTools Performance panel, filter for 'Font' requests, and observe when fonts finish loading relative to content paint.

What to look for: Look for font load blocking time and layout shifts caused by font swaps to confirm optimization.

Practice

1. What is the main benefit of self-hosting fonts in a Next.js application?

easy

A. Allows fonts to be loaded only on mobile devices

B. Automatically converts fonts to SVG format

C. Improves website speed and user privacy by serving fonts locally

D. Enables fonts to be downloaded from Google Fonts CDN

Solution

1. Step 1: Understand what self-hosting means

   Self-hosting fonts means serving font files from your own server instead of external sources.

2. Step 2: Identify benefits of self-hosting in Next.js

   This improves loading speed because fonts are fetched faster and enhances privacy by not contacting third-party servers.

3. Final Answer:

   Improves website speed and user privacy by serving fonts locally -> Option C

4. Quick Check:

   Self-hosting = faster load + privacy [OK]

Hint: Self-hosting means local font files, boosting speed and privacy [OK]

Common Mistakes:

• Thinking self-hosting converts font formats automatically
• Believing fonts load only on mobile devices
• Confusing self-hosting with using external CDNs

2. Which is the correct way to import a local font using Next.js 14+ syntax?

easy

A. import localFont from 'next/font/google';

B. import { localFont } from 'next/font/google';

C. import { localFont } from 'next/font/local';

D. import localFont from 'next/font/local';

Solution

1. Step 1: Recall Next.js font import syntax

   Local fonts are imported from 'next/font/local' as a default import.

2. Step 2: Check option correctness

   import localFont from 'next/font/local'; uses default import from 'next/font/local', which is correct. Options A, B, and D incorrectly use 'google' path or named imports.

3. Final Answer:

   import localFont from 'next/font/local'; -> Option D

4. Quick Check:

   Local fonts use default import from 'next/font/local' [OK]

Hint: Local fonts import default from 'next/font/local' [OK]

Common Mistakes:

• Using named imports instead of default import
• Importing local fonts from 'next/font/google'
• Confusing Google fonts import with local fonts

3. Given this code snippet in Next.js, what will be the font-family applied to the <main> element?

import localFont from 'next/font/local';

const myFont = localFont({
  src: './fonts/MyFont.woff2',
  variable: '--my-font',
});

export default function Home() {
  return (
    <main className={myFont.variable} style={{ fontFamily: 'var(--my-font)' }}>
      Hello World
    </main>
  );
}

medium

A. The font-family will be 'MyFont' loaded from the local file

B. The font-family will be the browser default because variable is unused

C. The font-family will be 'var(--my-font)' as a literal string

D. The code will throw a runtime error due to invalid style

Solution

1. Step 1: Understand localFont usage with CSS variable

   The localFont function creates a CSS variable '--my-font' that holds the font-family name for the loaded font.

2. Step 2: Analyze how fontFamily is applied

   The style uses fontFamily: 'var(--my-font)', which correctly applies the font loaded and assigned to the CSS variable.

3. Final Answer:

   The font-family will be 'MyFont' loaded from the local file -> Option A

4. Quick Check:

   CSS variable font applied = local font used [OK]

Hint: CSS variable holds font name, style uses var() to apply it [OK]

Common Mistakes:

• Thinking 'var(--my-font)' is a literal font name
• Assuming variable className is unused
• Believing code throws error due to style object

4. Identify the error in this Next.js font self-hosting code snippet:

import localFont from 'next/font/local';

const myFont = localFont({
  src: './fonts/MyFont.ttf',
  variable: '--font',
});

export default function Page() {
  return <div className={myFont.className} style={{ fontFamily: '--font' }}>Text</div>;
}

medium

A. The fontFamily style should use 'var(--font)' instead of '--font'

B. The src path must be an absolute URL, not relative

C. localFont does not support .ttf files, only .woff2

D. className should be applied to <main>, not <div>

Solution

1. Step 1: Check fontFamily style syntax

   CSS variables must be used with var(), so fontFamily should be 'var(--font)', not '--font'.

2. Step 2: Verify other parts

   The src path can be relative, .ttf is supported, and className can be on any element.

3. Final Answer:

   The fontFamily style should use 'var(--font)' instead of '--font' -> Option A

4. Quick Check:

   CSS variable usage requires var() [OK]

Hint: Use var(--variable) syntax for CSS variables in style [OK]

Common Mistakes:

• Omitting var() around CSS variable in style
• Thinking relative paths are invalid
• Assuming .ttf fonts are unsupported

5. You want to optimize font loading in a Next.js 14 app by self-hosting multiple font weights of 'OpenSans'. Which approach correctly applies different weights using next/font/local and CSS variables?

hard

A. Load all font files manually in _app.js without using next/font/local

B. Configure a single localFont with src as an array specifying path and weight for each file, assign a single CSS variable

C. Use next/font/google for all weights and ignore local hosting

D. Import only one font weight and use CSS font-weight property to simulate others

Solution

1. Step 1: Understand multiple font weights with localFont

   Multiple weights are handled in one localFont call using src: [{ path: './OpenSans-Regular.woff2', weight: '400' }, { path: './OpenSans-Bold.woff2', weight: '700' }], with a single CSS variable like '--font-opensans'.

2. Step 2: Combine variables in CSS or className for usage

   Apply the font className or variable to an ancestor element, then use font-family: var(--font-opensans) with font-weight in styles.

3. Step 3: Evaluate other options

   Import only one font weight and use CSS font-weight property to simulate others is incorrect because CSS font-weight cannot simulate different font files. Use next/font/google for all weights and ignore local hosting ignores self-hosting. Load all font files manually in _app.js without using next/font/local is manual and not optimized.

4. Final Answer:

   Configure a single localFont with src as an array specifying path and weight for each file, assign a single CSS variable -> Option B

5. Quick Check:

   src array + single variable = correct multi-weight self-hosting [OK]

Hint: Single localFont src array for weights + shared CSS variable [OK]

Common Mistakes:

• Trying to fake font weights with CSS alone
• Using Google fonts instead of self-hosting
• Manually loading fonts without next/font/local benefits