Back to Community
Home / Community / General

Why Are My Fonts Still Loading From Google? Troubleshooting OMGF

31 threads Sep 16, 2025

Content

If you've installed the 'OMGF | GDPR/DSGVO Compliant, Faster Google Fonts. Easy.' plugin but notice your website is still making requests to fonts.googleapis.com or fonts.gstatic.com, you're not alone. This is a common point of confusion. This guide will walk you through the most likely reasons and how to resolve them.

Why This Happens

The OMGF plugin is specifically designed to handle Google Fonts. Its process involves detecting these font requests, downloading the font files to your server, generating a local stylesheet, and then removing the original requests to Google's servers. However, this process can be interrupted by several factors, leading to external requests persisting.

Common Causes and Solutions

1. The 'Remove Google Fonts' Option is Not Enabled

This is the first setting to check. OMGF has an experimental feature to actively remove the Google Fonts requests it finds.

  • Solution: In your WordPress dashboard, navigate to OMGF > Advanced Settings. Locate the 'Remove Google Fonts' option and ensure it is checked. Save your changes and clear all your caching layers (plugin, server, and browser) before testing again.

2. Auto-Detection Missed Some Fonts

The auto-detect feature may not catch every single Google Font, especially if they are enqueued in an unconventional way by your theme or another plugin.

  • Solution: Go to OMGF > Help & Support and use the 'Run Test' button. This will provide a detailed list of all fonts it detects. If a font you know is used is missing from this list, you may need to manually add it under the OMGF > Settings tab.

3. Caching Issues

Caching is the most frequent culprit. Your page might be serving an old, cached version of the HTML that still contains the original Google Fonts links.

  • Solution: Thoroughly clear all cache. This includes your WordPress caching plugin (e.g., WP Rocket, W3 Total Cache, LSCache), any server-level cache (like Varnish), and your CDN's cache (like Cloudflare). Finally, clear your own browser cache or test in a private/incognito window.

4. Non-Google Fonts or Third-Party Scripts

OMGF cannot localize fonts that are not from Google Fonts. Furthermore, many third-party scripts and plugins (e.g., Google reCAPTCHA, embedded YouTube videos, advertising scripts, chat widgets) load their own fonts directly from Google, which is outside the control of OMGF.

  • Solution: Use your browser's Developer Tools (F12) to inspect the network requests. Identify which script or element is loading the font from Google. If it's from a critical feature like reCAPTCHA, this is expected behavior and cannot be changed by OMGF.

5. Theme or Plugin Compatibility

Some themes or plugins might enqueue fonts with unusual handles or using asynchronous methods that can interfere with OMGF's detection.

  • Solution: As a test, temporarily switch to a default WordPress theme (like Twenty Twenty-One) and disable all plugins except OMGF. If the Google Font requests disappear, reactivate your plugins and theme one-by-one to identify the conflict. You can then reach out to the developer of that specific software for further assistance.

Need More Help?

If you've worked through all these steps and the issue persists, the best course of action is to provide a detailed report. Note your theme, active plugins, and the exact URLs where the problem occurs. This information is vital for troubleshooting more complex, unique scenarios.

Related Support Threads Support