Fonts & frontend assets
Audit typography, loading and reusable frontend configuration.
Trusted resources
Use these primary references alongside the practical guides below.
A webfont returns 404: trace CSS paths and generated assets
Fix missing WordPress font requests by tracing the declaring stylesheet, relative URL resolution and generated asset deployment.
Read the guideBuild a WordPress font inventory before removing unused weights
Trace font requests to theme and builder settings and keep the weights and character sets readers actually need.
Read the guideFont fallback testing: stop headings jumping when the web font arrives
Compare fallback and final font layouts to catch shifting headings, buttons and forms on WordPress.
Read the guideFonts work at origin but fail through the CDN: CORS troubleshooting
Inspect cross-origin font failures, distinguish policy errors from missing files and verify the actual font request after a CDN change.
Read the guideUnused CSS reports: avoid deleting styles required by hidden states
Use browser Coverage to investigate WordPress CSS while protecting menus, form errors, responsive layouts and dynamic components.
Read the guideWordPress web fonts: keep the character, reduce the wait
Audit font families, weights and loading behavior without sacrificing readable text.
Read the guide