Evidence review
What to inspect before changing anything
Start with the delivered website and the real user journey. Record the current state so the team can distinguish an observed problem from an assumption and compare the same surface after deployment.
- 01Inventory font families, subsets and weights
- 02Measure text visibility and layout shift
- 03Check fallback metric differences
Implementation
A practical improvement plan
Make the smallest coherent change that solves the observed problem. Keep normal code review, accessibility, security and product checks in the loop instead of optimizing for the scan alone.
- 01Self-host or use dependable origins
- 02Subset and load only used variants
- 03Tune font-display and metric-compatible fallbacks
Verification
How to verify the result
Verification should test the intended outcome and the most likely regression. Use the production delivery path whenever headers, caching, rendering or third-party services affect the result.
- 01Throttle network and disable cache
- 02Compare layout before and after font load
- 03Check non-Latin and symbol coverage
Common pitfall
A shortcut to avoid
Preloading every weight can increase contention and delay more important content.
Further reading
Primary guidance and references
These sources provide standards, security guidance or the interpretation framework used to keep this guide bounded. Product-specific implementation still requires review in the actual codebase.