Daan van den Bergh

OMGF can be downloaded for free without any paid subscription from <a href="https://wordpress.org/plugins/host-webfonts-local/" rel="ugc">the official WordPress repository</a>.
<blockquote>
How could using fonts via Google’s service possibly run afoul of GDPR? The fact of the matter is that, when a font is requested by the user’s browser, their IP is logged by Google and used for analytics. 
 — Lifehacker
</blockquote>
Leverage Browser Cache, reduce DNS lookups/requests, reduce Cumulative Layout Shift and make your Google Fonts 100% GDPR-compliant with OMGF!
OMGF is written with performance and user-friendliness in mind. It uses the Google Fonts API to automatically cache the fonts your theme and plugins use to minimize DNS requests and speed up your WordPress website.
<h4>How Does It Work?</h4>
After installing and configuring the plugin, OMGF will automatically start looking for Google Fonts whenever a page is requested on your website.
All Google Fonts are listed in the Optimize Local Fonts section of OMGF’s settings screen. There, you can choose to:
<ul>
<li>Preload fonts to reduce Cumulative Layout Shift above the fold.</li>
<li>Unload fonts that’re not used by you, your theme, and/or plugins.</li>
<li>Set a Fallback Font Stack (OMGF Pro required), to further reduce Cumulative Layout Shift, or</li>
<li>Enable Magic Fallbacks (OMGF Pro required), to automatically generate mathematically tuned system font fallbacks that match your Google Fonts’ exact proportions, eliminating layout shift while fonts load.</li>
<li>Replace (OMGF Pro required) font-families with system fonts to speed up loading times!</li>
</ul>
<h4>Other Features include</h4>
<ul>
<li>The integrated Google Fonts checker notifies you if a plugin or your theme has added Google Fonts (e.g., after an update) it can’t process.</li>
<li>The Performance Checker automatically monitors your Google Fonts’ performance and notifies you about potential improvements in 4 areas:
<ul>
<li>Unused subsets — subsets that are downloaded but never used, increasing Total Blocking Time,</li>
<li>Unused font styles/weights — font variants that are loaded but not used, causing unused CSS,</li>
<li>Missing preloads — fonts used above the fold that aren’t preloaded, increasing Largest Contentful Paint and First Contentful Paint,</li>
<li>Cumulative Layout Shift — layout shift caused by fonts loading after the page is rendered.</li>
</ul>
</li>
<li>Variable Fonts support,</li>
<li>Remove Resource Hints (preload, preconnect, dns-prefetch) pointing to <code>fonts.googleapis.com</code> or 
 fonts.gstatic.com,
<ul>
<li>Ensure text remains visible during webfont load by forcing the font-display attribute to your Google Fonts,</li>
</ul>
</li>
<li>Ensure text remains visible during webfont load by forcing the font-display attribute to all your other fonts! (OMGF Pro required),</li>
</ul>
<h4>Additional Features in OMGF Pro</h4>
<ul>
<li>Smart Optimize automatically detects which fonts, subsets, and weights are actually used on each page — preloading the ones that matter and removing the ones that don’t, to eliminate render-blocking resources and reduce unused CSS.</li>
<li>Magic Fallbacks generates mathematically tuned system font fallbacks that match your Google Fonts’ exact proportions, eliminating layout shift while fonts load.</li>
<li>Automatically configures itself to make sure all externally hosted Google Fonts on your site are hosted locally. OMGF Pro supports:
<ul>
<li><code>@font-face</code> and <code>@import</code> statements inside inline <code><style></code> blocks,</li>
<li><code>@font-face</code> and <code>@import</code> statements inside local stylesheets loaded by e.g. your theme and/or plugins,</li>
<li><code>@font-face</code> and <code>@import</code> statements inside externally hosted stylesheets loaded by your theme and/or 
plugins,</li>
<li>Web Font Loader (<code>webfont.js</code>),</li>
<li>Async Google Fonts (loaded using JS)</li>
<li>Material Icons.</li>
</ul>
</li>
<li>Multisite and WPML support.</li>
<li>Whitelabel stylesheets, which removes branding and comments from the stylesheets to further reduce the size.</li>
<li>Modify your fonts’ <code>src: url()</code> attribute to fully integrate with your configuration,
<ul>
<li>Use this to serve fonts and the stylesheets from your CDN, or</li>
<li>To serve fonts from an alternative path (e.g. when you’re using Security through Obscurity plugins like WP Hide, 
etc.), or</li>
<li>Anything you like!</li>
</ul>
</li>
<li>Developer Mode, which allows you to easily migrate between Development, Staging/Testing, Acceptance and Production 
environments.</li>
</ul>
<a href="https://daan.dev/wordpress/omgf-pro/" rel="nofollow ugc">Purchase OMGF Pro</a> | <a href="https://daan.dev/docs/omgf-pro/" rel="nofollow ugc">Documentation</a> | <a href="https://daan.dev/docs/omgf-pro/tested-themes-plugins/" rel="nofollow ugc">Tested Plugins & Themes</a>

OMGF | GDPR/DSGVO Compliant, Faster Google Fonts. Easy.


Does the job flawlessly. Thanks for making this plugin!


Just works!

Good plugin

OMGF automagically caches the Google Fonts used by your theme/plugins locally. No configuration (or brains) required!

GDPRess can be downloaded for free without any paid subscription from <a href="https://wordpress.org/plugins/gdpr-press/" rel="ugc">the official WordPress repository</a>.
In January 2022 <a href="https://daan.dev/blog/gdpr/google-fonts-violates-gdpr-germany/" rel="nofollow ugc">a German court ruled</a> that a website owner was in breach of GDPR and should pay a € 100,- fine, because embedded Google Fonts were used, essentially transferring the user’s personal data (IP address) without the user’s prior consent.
<h4>What’s embedding?</h4>
When an external (i.e., loaded from another server, besides your own) resource is embedded into a webpage, it basically means that the resource behaves as if it’s loaded from the same server hosting the webpage.
<h4>Why is using embedded resources in breach of GDPR?</h4>
Because of <a href="https://daan.dev/blog/how-to/google-fonts-gdpr/#h-how-the-internet-works" rel="nofollow ugc">the way the internet works</a>. When a browser (i.e., computer) requests a file (e.g., an image or a font file), the server needs the IP address of that computer to send it back. All these requests (including the IP address) are logged in a so-called <code>access.log</code>.
Once this IP address leaves the European Union, your website is violating the GDPR.
<h4>What does this plugin do?</h4>
GDPRess scans your homepage for third party scripts (JS) and stylesheets (CSS), and:
<ul>
<li>Allows you to download or exclude them from downloading.</li>
<li>Parses the stylesheets for loaded font files, downloads them, and rewrites the stylesheet to use the local copies.</li>
<li>Makes sure the local copies of each script/stylesheet are used in your site’s frontend.</li>
</ul>
In short, it makes sure no requests are made to external/embedded/3rd party scripts and stylesheets.

GDPRess | Eliminate external requests to increase GDPR compliance

Good job! Works even on my WP6++ sites.

Checked in Browser and it works as expected.

Thanks for this plugin.

Ralph Rathmann

Great Job. It Works! Installed and configured in less than 100seconds ;-)


Used it to localize Font Awesome CSS and font files. Works like a charm. Just perfect! Thank you for your hard work @daanvandenbergh


Great plugin!

GDPRess can be downloaded for free without any paid subscription from the official WordPress repository.

OMGF | GDPR/DSGVO Compliant, Faster Google Fonts. Easy. vs GDPRess | Eliminate external requests to increase GDPR compliance