Lukas Rydygel

The plugin will automatically parse all registered styles and import the ressources from Google to your server and load them.
<h3>Usage</h3>
Simply include the fonts from Google by using <code>wp_enqueue_scripts</code>.
The plugin will parse the URL from the enqueued stylesheets and detect front from Google.
The files will be downloaded to your server and the CSS will be changed to match the new paths.
You may flush the fonts from your server using the button in the admin bar.
<h3>Notes</h3>
When using multiple fonts in one style-tag, please make sure to use no load the script without a version, to avoid WordPress from normalizing the URL.
<pre><code>wp_enqueue_style('...', '...', [], null);
</code></pre>
As Google will accept the parameter <code>family</code> multiple times, WordPress will merge them into one.
Be aware, that some caching plugins which also provide minification, may cause this plugin to break, as the fonts will be parsed before the plugin hook.

Google-Fonts-Wrapper

The plugin will automatically parse all registered styles and import the ressources from Google to your server and load them.

FluxPress

EasyFonts is the smart way to host Google Fonts locally in WordPress. Activate it and your Google Fonts are detected, downloaded, and served from your own domain — no requests to Google, faster loading, and full GDPR compliance.
Unlike basic font plugins, EasyFonts doesn’t just self-host blindly. It measures which fonts actually render in real visitors’ browsers, so it can preload your above-the-fold fonts, flag the ones you never use, and generate zero-CLS metric-matched fallbacks — the things that actually move your Core Web Vitals (LCP, CLS) scores.
<h4>Why host Google Fonts locally?</h4>
<ol>
<li>GDPR / DSGVO: German courts have ruled that sending visitor IPs to Google Fonts without consent violates GDPR. Self-hosting removes the connection entirely — no data leaves your server.</li>
<li>Speed & Core Web Vitals: Every call to <code>fonts.googleapis.com</code> and <code>fonts.gstatic.com</code> adds DNS lookups, connections, and render-blocking delay that hurt LCP and TTFB. Local hosting kills that latency.</li>
</ol>
<h4>What EasyFonts does</h4>
<ul>
<li>Automatic local hosting — Detects Google Fonts loaded via <code><link></code> stylesheets, <code>@import</code> rules, inline <code>@font-face</code>, theme/plugin CSS files, external/CDN stylesheets, and the Web Font Loader (webfont.js) — then downloads and serves them locally.</li>
<li>Combine into one stylesheet — Merges all hosted font CSS into a single file, removes duplicate <code>@font-face</code> rules, and can inline it as minified CSS so it’s not render-blocking.</li>
<li>Used vs Unused font discovery — Automatically identifies fonts that never render on real pages so you can disable unnecessary downloads and preloads.</li>
<li>Real usage measurement — A lightweight beacon measures which font families and weights actually render, and which appear above the fold — directly on your live pages, no loopback crawler.</li>
<li>Smart preloading — Auto-preloads the above-the-fold fonts that matter (capped, so you never over-preload), boosting LCP.</li>
<li>font-display control — Force <code>font-display: swap</code> (or block, fallback, optional, auto) on every face to fix “Ensure text remains visible during webfont load.”</li>
<li>Per-family & per-weight control — Toggle Load and Preload for any family or individual weight; disable fonts you don’t use.</li>
<li>Subset trimming — Keep only the character sets you need (Latin, Cyrillic, Greek, Vietnamese, Arabic, Devanagari, CJK and more) to cut font weight.</li>
<li>Zero-CLS fallbacks — Reads each font’s real metrics and generates size-matched fallback faces (<code>size-adjust</code>, <code>ascent-override</code>) to eliminate layout shift while fonts load.</li>
<li>Async / JS-injected font blocking — Optionally catches Google Fonts injected by JavaScript at runtime and self-hosts them too (handles fonts most plugins miss).</li>
<li>Clean resource hints — Strips now-useless <code>preconnect</code>, <code>dns-prefetch</code>, and <code>preload</code> tags pointing at Google’s servers.</li>
<li>Variable font support — Detects and hosts modern variable fonts as a single optimized file instead of many static weights.</li>
<li>CDN support — Serve hosted fonts and the stylesheet from your CDN.</li>
<li>Bunny Fonts support — Also self-hosts fonts from <code>fonts.bunny.net</code>.</li>
<li>Import / Export settings — Move your configuration between sites in one click.</li>
<li>Multisite ready — Works per-site across a network, with tables created automatically for new sites.</li>
<li>WP-CLI — Scan and manage fonts from the command line.</li>
<li>Page builder & theme compatible — Elementor, Divi, Bricks, Beaver Builder, WPBakery, Oxygen, plus Astra, GeneratePress, Kadence, Blocksy, and WooCommerce. Editors are automatically excluded so your styling stays intact while you build.</li>
</ul>
<h4>Why choose EasyFonts over OMGF and other font plugins?</h4>
<ul>
<li>It measures, not guesses. EasyFonts sees what actually renders in real browsers, so preload and fallbacks are based on data — not a static guess.</li>
<li>Detection most plugins charge for. Inline CSS, theme/plugin CSS, external stylesheets, and Web Font Loader detection are free here — features that are paid add-ons elsewhere.</li>
<li>Zero-CLS fallbacks for any font — generated from real font metrics, not limited to a fixed list.</li>
<li>Async JS-injected fonts — caught and self-hosted, a common gap in other plugins.</li>
<li>Truly zero-config. Activate it and it works; everything else is optional fine-tuning.</li>
<li>No data sent anywhere. All processing is on your server.</li>
</ul>
<h4>How it works</h4>
<ol>
<li>Install and activate EasyFonts.</li>
<li>Open Easy Fonts in your admin menu.</li>
<li>Click Optimize now (or just let visitors browse) — fonts are detected, self-hosted, and measured automatically.</li>
<li>Review Used vs Unused fonts, fine-tune Load/Preload, and adjust settings if you like.</li>
<li>Done — your Google Fonts now load locally, faster, and GDPR-compliant.</li>
</ol>

EasyFonts – Host Google Fonts Locally, Fast & Auto-Optimize, GDPR Compliant

Host Google Fonts locally, Auto combine and remove duplicate fonts, Auto preload. pass Core Web Vitals — GDPR compliant, auto-config.

Google-Fonts-Wrapper vs EasyFonts – Host Google Fonts Locally, Fast & Auto-Optimize, GDPR Compliant