UAU Ready
Description
When a website in Europe needs to be GDPR-compliant without sacrificing speed, OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts replaces external requests to Google Fonts with a local version hosted on your own server, eliminating data transfers to third parties. This approach serves blogs, portfolios, and corporate websites that want to combine privacy and performance with support for over 900 font families, as well as offering smart caching and preloading to further optimize delivery.
Key Features of OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts
- Automatic local hosting
Downloads Google Fonts to your server and serves them from your own domain, eliminating external requests. - Total GDPR compliance
No visitor data is sent to Google, ensuring privacy from the very first visit. - Cache optimization
Caches fonts with expiration headers, reducing load time on subsequent pages. - Smart preloading
Addsrel="preload"to each font, loading it even before CSS is parsed. - Control over font families
Manually select which families will be hosted or let the plugin detect the ones used in the theme.
Benefits of OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts
- Faster loading
Reduces the number of DNS connections and prevents network blocking by third-party services. - Privacy without hassle
Brings the site into compliance with European legislation without the need for extra consent plugins. - Simplified maintenance
Automatically updates downloaded fonts as new versions are released. - Better mobile experience
Locally served fonts load consistently even on slow networks.
Who Is OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts For?
- European websites that need GDPR compliance.
- Blogs and portfolios that use Google Fonts.
- Developers looking to combine performance with privacy.
How to Download OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts
OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts is available for download here at Ultrapack. After downloading the .zip file, install it via Plugins > Add New > Upload Plugin, select the .zip, and activate it. The configuration panel will appear under Settings > OMGF PRO, and the file is complete and ready for immediate installation.
By hosting Google Fonts locally, OMGF PRO simultaneously solves two common bottlenecks: the external dependency that slows down loading and the exposure of browsing data to foreign servers. It’s the right tool for websites that prioritize both speed and visitor privacy, without requiring any technical changes to the design or the typography already in place.
Frequently asked questions
Is OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts GPL-licensed?
Yes. OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts is distributed under the GPL (GNU General Public License). You may legally use, modify and redistribute it on as many sites as you want.
Can I use OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts on multiple sites?
Yes. You can use OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts on multiple sites. The number of sites connected to Ultrapack Auto Updater is limited by your plan.
How much does OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts cost at Ultrapack?
OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts costs US$2.99 as a single purchase, and it is also included in the subscription plans starting at US$12/mo (VIP I).
Does OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts include updates?
Yes. The current version of OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts is 5.2.11, published at Ultrapack on Sep 23, 2026. Subscribers update straight from the WordPress dashboard with UAU (Ultrapack Auto Updater).
Is OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts scanned before publication?
Yes. Every version of OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts goes through a malware scan (ClamAV and YARA rules, at UltraHub) before it is published.
What are the requirements for the plugin OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts?
Requires WordPress 6.2 or higher and PHP 7.2 or higher. Tested up to WordPress 7.0.
What changed in this version
Version 5.2.11
- Note: this release requires OMGF v6.3.11 or higher. On older versions the clean up below is postponed until OMGF is updated, and Material Icons stylesheets aren't processed until then.
- Security: hardened the detection of Material Icons stylesheets, in line with OMGF v6.3.11.
- Fixed: Magic Fallbacks kept asking to contact support about fonts which never existed, e.g. 'Arial,Helvetica,sans-serif !important', 'var(--tve-font-family,Mulish)' and 'inherit'. Whenever the Google Fonts API returned no fonts for a font family found in a local or inline stylesheet — which is always the case for a font installed with WordPress' Font Library — OMGF Pro < v5.2.9 ran the optimization again with the entire document, instead of that font's @font-face statements. Every font-family declaration in that document was then stored as a font family. This release removes those entries from the Optimized Fonts table, and Magic Fallbacks now ignores any value which can't be the name of a font, instead of reporting it.
Version 5.2.10
- Note: this release detects stylesheets which were skipped before, so optionally run Save & Optimize once after updating to add them to your cache. Nothing breaks if you don't.
- Fixed: Optimize Local/External Stylesheets skipped any link element written over multiple lines (or with a line break inside its href attribute), while browsers load those just fine. The pattern used to find them couldn't match line breaks, but could run past the > which ends an element. Both are fixed, and line breaks are now stripped from the URL before it's requested, just like browsers do.
- Improved: the classes which collect @import statements (and the one which adds the Material Icons subset) registered their filters once per instance, while they're constructed on every processing run. Because nothing ever removed those filters, they stacked up within a single request, which meant the same @import could be optimized several times over, and the Material Icons subset could be added to the subset list more than once.
- Fixed: @import statements spread over multiple lines weren't detected. CSS allows whitespace (incl. line breaks) after @import and inside url, and a backslash followed by a line break is a line continuation inside a string, but none of those were matched. A raw line break inside the URL is still ignored, because that's an unterminated string, which browsers don't load either.
- Fixed: Smart Optimize (Unused Fonts) could return a blank page when an inline @import statement was fully unloaded. The pattern used to remove that statement removed everything between the first @import and the last occurrence of the stylesheet's URL, and exceeded PCRE's runtime limits on documents larger than ~100KB, in which case the entire document was replaced with nothing (accompanied by a 'preg_replace_callback: Passing null to parameter #3 ($subject)' deprecation notice). Matching is now confined to a single @import statement, and a failed search/replace leaves the document untouched.
- Fixed: Smart Optimize (Unused Fonts) didn't remove any @font-face rules from stylesheets whose fonts are split into subsets. The subset was matched against the font file's URL using a pattern which
- couldn't match the hyphen separating the subset from the font-weight (e.g., source-sans-pro-normal-latin-400.woff2), so no rule ever matched. The subset is now matched against the @font-face rule's
- unicode-range, and only falls back to the filename for rules which don't define one.
- Fixed: Smart Optimize (Unused Fonts) now removes a stylesheet's link element from the HTML entirely when all of its @font-face rules are unloaded, instead of leaving behind a request for an empty stylesheet. Generated stylesheets always start with a header comment, which meant they were never detected as empty. This also fixes the deregistration of fully unloaded Async Stylesheets.
- Fixed: an unused Material Icons stylesheet wasn't removed from the HTML. Its cached URL was looked up in the wrong list, so it was never recognized, and clearing the link element's href attribute left behind a request for the page itself. Its link element is now removed entirely.
Version 5.2.9
- Fixed: with Magic Fallbacks enabled, the first click on a Replace checkbox checked all corresponding "Don't Load" checkboxes, but left the Replace checkbox itself unchecked.
- Fixed: with Magic Fallbacks enabled, a Replace checkbox stayed disabled after unchecking the Preload checkbox(es) of the corresponding font family.
- Fixed: A corrupted (non-array) Fallback Font Stack option no longer causes a fatal error ('Cannot access offset of type string on string') when opening the Optimize Fonts settings screen.
- Fixed: Magic Fallback aliases were incorrectly stored as font families during Save & Optimize, causing a 'could not find a matching fallback font' notice.
- Fixed: Magic Fallbacks no longer tries to find a fallback for icon fonts (e.g., Material Icons/Symbols) and no longer shows a 'could not find a matching fallback font' notice for them.
- Fixed: Smart Optimize now purges the page cache on taxonomy archives, the homepage and WooCommerce product pages by switching supported caching plugins (LiteSpeed, W3 Total Cache, WP-Optimize, WP Rocket, WP Super Cache) to URL-based purging, so the detection script no longer re-runs on every page load for URLs without a single post-ID.
Version 5.2.8
- Security: Hardened Smart Optimize and local stylesheet processing to prevent a path traversal vulnerability. Props Patchstack.
- Fixed: Muli was renamed to Mooli. This fix provides an alias for it.
Version 5.2.7
- URGENT!: This release patches an exploit currently being actively exploited in the wild.
- Fixed: Neuton and Oxygen didn't receive proper Magic Fallbacks due to missing values in the dataset. This fix provides fallbacks for these cases.
Release notes published by the developer.
How to install
Automatic updates: this item is updated by the Ultrapack Auto Updater. With it installed, the new version shows up in your dashboard like any other WordPress update (how to set it up).
This Pro version is an add-on to the free one. On its own it does not work.
- In the WordPress dashboard, go to Plugins > Add New, search for the plugin by name in the official repository and install the free version. Activate it.
- Download the file
host-google-fonts-pro.zip. - Go to Plugins > Add New > Upload Plugin, select the file
host-google-fonts-pro.zipand click Install Now. - Click Activate. Both versions stay active at the same time.
Requirements: Requires WordPress 6.2 or higher and PHP 7.2 or higher. Tested up to WordPress 7.0.
- Deactivating the free version also disables Pro.
Stuck on a step? Open a ticket telling us which one you stopped at.
