LocalFonts

Yes. LocalFonts works at two levels: it filters WordPress-enqueued stylesheets (via the style_loader_src hook) and also processes the full HTML output to catch hardcoded Google Font references from any theme or plugin. Whether your theme uses wp_enqueue_style, hardcoded link tags, or CSS @import rules to load fonts from fonts.googleapis.com, LocalFonts will intercept and self-host the font files.

When active and working correctly, LocalFonts ensures zero connections are made to Google's servers — no font file loading from fonts.gstatic.com, no DNS prefetch, and no preconnect hints to fonts.googleapis.com. This directly addresses the core GDPR (General Data Protection Regulation) and DSGVO (Datenschutz-Grundverordnung) concern of transmitting visitor IP addresses to third-party servers without consent.

Yes, fully supported. The plugin intercepts both fonts.googleapis.com/css (regular Google Fonts) and fonts.googleapis.com/icon (Google Material Design Icons and Material Symbols) endpoints, downloading and serving all icon font files locally.

Yes. Any Google Fonts that appear in the page HTML — whether added by Elementor, Beaver Builder, Divi Builder, WPBakery Page Builder, Brizy, Oxygen Builder, Bricks Builder, or any other page builder — will be intercepted and served from your local server.

The plugin requests fonts as a modern browser (Chrome user agent), so Google serves WOFF2 files — the smallest and fastest web font format with broad browser support including Chrome, Firefox, Safari, Edge, and Opera.

In wp-content/uploads/lgfl-fonts/. Each unique Google Font URL gets its own subdirectory containing the rewritten CSS file and the individual WOFF2 font files.

No — it makes your site faster. By eliminating external DNS lookups and connections to fonts.googleapis.com and fonts.gstatic.com, page load times decrease. The very first page load after activation may be marginally slower as fonts are downloaded in the background via WP-Cron, but all subsequent page loads serve fonts from your local server cache instantly.

The plugin gracefully falls back to the original Google Font URL so fonts still load for your visitors. Failed downloads are logged in the Activity Logs on the settings page so you can investigate and retry.

All downloaded font files are automatically deleted from your server to keep things clean. Google Fonts will then load from Google's servers again as they did before activation.

Yes. LocalFonts is compatible with all major caching plugins including WP Super Cache, W3 Total Cache, LiteSpeed Cache, WP Rocket, WP Fastest Cache, and others. After fonts are downloaded locally, clear your page cache so the updated local font URLs are reflected in cached pages.

Yes. Self-hosting Google Fonts eliminates third-party font requests, which can improve your PageSpeed Insights, GTmetrix, and Lighthouse performance scores. It resolves common audit warnings including "Reduce the impact of third-party code," "Eliminate render-blocking resources" (from external font CSS), and "Preconnect to required origins."

LocalFonts is designed to be the only plugin managing your Google Fonts hosting. Using it alongside other Google Fonts optimization or local font plugins may cause conflicts. If you are switching from another solution, deactivate the previous plugin first before activating LocalFonts.

Yes. LocalFonts catches Google Fonts loaded by WooCommerce, WooCommerce themes, and WooCommerce extensions. Any font request to fonts.googleapis.com — regardless of which plugin or theme triggers it — will be intercepted and served locally.