Home
Bookmarks
Leagues
LEARN
Courses
Career Paths
Assessments
Tutorials
Arcade
Glossary
GROW
Certifications
Log in
Glossary
Log inSign up
Courses/Introduction to Design Systems/Typography Systems: Hierarchy & Scale/
Exercise #8

System Fonts vs Custom Web Fonts: Performance Tradeoffs

When architecting a typography system, teams face a strategic decision:

  1. Native System Font Stack: Uses the operating system's pre-installed default font (-apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif):
    • Pros: Zero network payload (instant 0ms loading), no layout shift (CLS = 0), native OS feel (feels like an Apple app on Mac, an Android app on Pixel).
    • Cons: Brand expression varies slightly across platforms.
  2. Custom Web Fonts (e.g., Inter, Plus Jakarta Sans, Geist):
    • Pros: Perfectly identical visual identity across every browser and operating system.
    • Cons: Requires 50–150KB of font files; risks FOIT (Flash of Invisible Text) or FOUT (Flash of Unstyled Text) during slow network connections.

Pro Tip: If using web fonts, always preload the primary WOFF2 files and use font-display: swap so content remains readable immediately.

Topics

The Role of Typography in Product UX
Modular Type Scales & Mathematical Ratios
Line Height (Leading) & The Inverse Proportion Rule
Letter Spacing (Tracking): Optical Adjustments
Measure & Line Length: The 45–75 Character Rule
Font Weights & Semantic Role Assignment
Tabular Figures: Aligning Numbers in Data Tables
System Fonts vs Custom Web Fonts: Performance Tradeoffs
Fluid Typography with CSS `clamp()`
Challenge: Architecting a Production Typography Scale

From lesson

4

Typography Systems: Hierarchy & Scale

Level 3 · Design Tokens & Foundations

Top contributors

Community contribution details will appear here once real learner activity is available.

Share