Fonts loaded from Google’s servers cost three round trips before the first glyph renders: DNS, connection, then the CSS and files. Self-hosting removes all of it and — bonus — removes the GDPR complication of transmitting visitor IPs to Google. We compared the three realistic routes on a theme with two font families, four weights.
The routes
| Route | How it works | Setup | Kept working after theme switch? |
|---|---|---|---|
| OMGF | Downloads Google Fonts CSS + files locally, rewrites | 10 min | Yes — runs at output level |
| Perfmatters | Local hosting toggle (with its own downloader) | 5 min | Yes |
| Manual (download + theme CSS) | You host files, write @font-face | 45 min | No — rebuild on theme change |
Measured on the same theme
- Requests to Google: 4 → 0 in all routes. External font CSS was render-blocking; local @font-face preload removed ~120ms of critical path on a 40ms-RTT connection.
- LCP: 1.42s → 1.21s on the test page — meaningful on a page already optimized per the font-loading guide, dramatic on worse connections.
- GDPR posture: no third-party font request, one less consent-banner argument — relevant to the analytics consent analysis in the analytics comparison.
Which route
- Already running Perfmatters (from the script manager setup): use its toggle — no new plugin.
- Stand-alone need: OMGF — purpose-built, handles preloading and font-display correctly.
- Never switch themes, want zero plugins: manual hosting is fine but becomes tech debt — our theme-switch analysis in when to switch themes suggests that debt gets paid eventually.
Three reasons: it removes ~120ms of critical-path DNS/connection/CSS latency, avoids the GDPR issue of sending visitor IPs to Google, and removes dependency on Google's uptime. If you already run Perfmatters, use its built-in local-hosting toggle. OMGF is the better stand-alone: purpose-built with proper preloading and font-display handling. On our two-family test theme: LCP improved 1.42s → 1.21s (~210ms). Gains are larger on high-latency mobile connections. No — Google Fonts are licensed for self-hosting, and search engines are indifferent to font origin. Just ensure font-display: swap so text renders during load.Why should I self-host Google Fonts?
OMGF or Perfmatters for local fonts?
How much faster is self-hosting fonts?
Does self-hosting fonts affect SEO or licensing?
