Faster fonts for speed fanatics
summary
Hosting fonts on the same origin cuts speed index roughly 35% compared with cross‑origin Google Fonts; using rel=preconnect masks connection latency and yields about a 7% speed‑index win; font-display: swap roughly halves first meaningful paint by showing system text then swapping in web fonts; rel=preload removes nested critical request chains so fonts load earlier; honoring save‑data can shrink delivered font bytes from ~50KB to ~10KB by skipping nonessential typefaces.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:41HOW BROWSERS RENDER FONTS
- 2:08A QUICK RECAP OF RESOURCE LOADING
- 3:43RENDER BLOCKING IS ALL ABOUT PRIORITIES
- 6:03WEB FONTS ARE RIPE FOR PERFORMANCE TUNING
- 15:05HOSTING YOUR OWN FONTS GIVES YOU CONTROL
- 16:22FRIENDLY REMINDER: MIND THE LICENSING AGREEMENTS!
- 16:56font-display FOR BETTER RENDERING CONTROL
- 17:53font-display: auto; BROWSER DEFAULT BEHAVIOR KICKS IN.
- 20:57CONSIDERATIONS WITH swap: . Don't use it for icon fonts (use font-display: block instead)
- 30:30SLIDE DECK LINK: JLWAGNER.NET/TALKS/FASTER-FONTS
related talks
32mHigh Performance Web Fonts
26mHigh Performance Web Fonts
31mFontastic web performance
28mHosting Fonts? Good Luck!
50mFont Performance Strategies
37mThe Critical Request: An investigation into what blocks render
47mThe Scoville Scale of Web Font Loading Opinions
47mThe Five Whys of Web Font Loading Performance
