# Checklist — Google Fonts GDPR & WordPress performance

**Extension:** [Google Fonts Control by Volade v1.0.0](https://volade.com/en/cms/wordpress/extensions/google-fonts-control-by-volade)  
**Article:** https://volade.com/en/blog/wordpress-google-fonts-control-2026

## Phase 1 — Audit

- [ ] DevTools Network: filter `fonts.googleapis.com` and `fonts.gstatic.com`
- [ ] List loaded families (theme, Elementor, plugins)
- [ ] Document US transfer context (Munich C-252/21)
- [ ] Measure LCP before changes (PageSpeed)

## Phase 2 — Install GFC

- [ ] Install Google Fonts Control by Volade (full ZIP with volade-sdk)
- [ ] Run theme + enqueue scan
- [ ] Review inventory under Settings → Google Fonts Control

## Phase 3 — Sync

- [ ] Sync woff2 for each detected family
- [ ] Verify `wp-content/uploads/volade-gfc/` folder
- [ ] Apply **GDPR strict** or **Performance** preset

## Phase 4 — Front-end tests

- [ ] Zero Google Fonts requests on page load
- [ ] Gutenberg / customizer preview OK (block editor safe preset)
- [ ] Mobile: correct fonts, no blocking FOUT
- [ ] Re-measure LCP

## Phase 5 — Handoff

- [ ] JSON inventory export downloaded
- [ ] DPO note: self-host = no documented Google transfer
- [ ] Plan: re-scan after theme change

**Reminder:** GFC complements Complianz — it does not replace your cookie banner.