Load representative templates and record each requested font file, family, weight and style.
Inventory requests, not assumptions
Load representative templates and record each requested font file, family, weight and style. Include an article, landing page and form. Theme settings do not always describe every request added by a builder or embedded component. Mark requests whose origin you cannot yet explain.
Match files to visible use
Inspect a heading and paragraph to see which family and weight the browser applies. Repeat for navigation and buttons. Google’s font guidance describes how styling affects font discovery and loading. Your inventory should connect the transfer to an actual component, not just count files.
Identify duplicate configuration
Check theme typography, builder defaults and page-level overrides. If two families serve the same role unintentionally, decide which configuration owns it before removing a source. Review every template affected by that default. A local page fix can leave the global duplication untouched.
Remove conservatively
On staging, trial removing a weight that your audit found unused. Check emphasized text, hover states, headings and error messages afterward. Include translated content before changing subsets. If the browser synthesizes a missing style, ask the designer whether the result still matches the intended appearance.
Keep the inventory current
Record the final list and its purpose alongside the theme configuration. Recheck after a redesign or builder migration. Report observed transfer changes without inventing a site-wide percentage gain. A smaller request set is useful evidence, but the reading and loading experience should decide whether the change stays.
Put it into practice
- Inventory requests, not assumptions
- Match files to visible use
- Identify duplicate configuration
- Remove conservatively
- Keep the inventory current
AI-assisted educational content prepared for the Velonic resource library. How these guides are prepared.