Performance fix guide
Late-Discovered Web Fonts
Web font requests are initiated late in the loading waterfall because they are referenced in external CSS files rather than preloaded.
Issue ID: CWV-LATE-FONTS-001
Severity: moderate
Impact: Med
Effort: S
Use this article when
- You need deeper remediation guidance than the issue card can show.
- You want CMS-specific steps before handing the fix to a developer.
- You want a repeatable re-check path after shipping the change.
What this issue is
Web font requests are initiated late in the loading waterfall because they are referenced in external CSS files rather than preloaded.
Why it matters
Web font requests are initiated late in the loading waterfall because they are referenced in external CSS files rather than preloaded. This affects load speed, Core Web Vitals, and how many visitors stay long enough to convert.
How we detect it
- FreeSiteAudit flags this issue when the rule for CWV-LATE-FONTS-001 fails and the page evidence points to Performance tool.
- You can usually confirm this by checking the page source or the relevant page settings inside your CMS.
Evidence examples
Check the affected page source, rendered output, or relevant CMS setting to confirm the missing or incorrect element.
How to fix it
- 1Preload critical web fonts with <link rel="preload" as="font" crossorigin>
- 2Self-host fonts to reduce connection overhead
- 3Limit the number of font families and weights loaded
How to re-check it
- Check Network waterfall and confirm fonts load early
Related tools
This issue is best verified with the full FreeSiteAudit crawl rather than a single-point mini tool.