Back to Community
Home / Community / General

Why OMGF Might Not Detect All Your Google Fonts (And How To Fix It)

24 threads Sep 10, 2025

Content

If you're using the 'OMGF | GDPR/DSGVO Compliant, Faster Google Fonts. Easy.' plugin, you might occasionally run into a situation where it doesn't seem to detect or optimize all the Google Fonts on your site. This can be confusing, especially when you're expecting a performance boost. Let's break down the common reasons this happens and the steps you can take to resolve it.

Why OMGF Can't Detect Certain Fonts

Based on community discussions and support threads, OMGF operates by scanning your site's pages for specific requests to Google's servers. It primarily looks for resources coming from domains like fonts.googleapis.com. If a font is loaded from a different source or through a different method, OMGF won't be able to process it. Here are the most common scenarios:

  • Fonts Already Hosted Locally: If another plugin (like WPBakery's built-in feature) or your theme is already serving fonts from your server, OMGF will not detect them. It specifically targets external requests to Google's domains.
  • Dynamically Loaded Fonts: Fonts loaded asynchronously by third-party scripts, such as those from Tawk.to chat widgets or Google reCAPTCHA, often load in an iframe or after OMGF has done its initial processing. Since these are not part of the initial page source, OMGF cannot intercept them.
  • Manual Font Selection in Older Versions: Some users reported that after updating from older versions (e.g., pre-v3.0), the method for manually adding fonts changed. The previous one-by-one search feature was removed to improve stability, which required users to adapt to the new interface.

How to Troubleshoot and Fix Detection Issues

  1. Identify the Source: Use your browser's developer tools (Network tab) to check all network requests. Look for any font-related requests (.css, .woff2) that are still going to fonts.googleapis.com or other external domains. This will help you identify which fonts are being missed.
  2. Check for Conflicting Plugins/Themes: Deactivate any other optimization or font-related plugins temporarily. Some themes also have built-in options to locally host Google Fonts. Ensure these are disabled so OMGF can handle the optimization without interference.
  3. Review Your OMGF Settings: Navigate to OMGF > Settings in your WordPress admin dashboard. If you are using the manual detection mode, ensure you have added all the necessary font families and subsets (e.g., latin-ext) that your site requires. The automatic detection feature may not always catch every variant, especially in complex setups.
  4. Consider Subsets and Unicode Ranges: If your site uses special characters (e.g., letters with accents), the issue might be a missing subset. Earlier versions of OMGF did not automatically handle all subsets. Ensure the required subset (like latin-ext) is selected for your fonts in the OMGF configuration.
  5. Understand the Limitations: Accept that some fonts are beyond OMGF's control. Fonts loaded in iframes (like Google reCAPTCHA) or by aggressive third-party JavaScript cannot be optimized by this or any similar plugin.

By systematically working through these points, you should be able to identify why certain fonts are not being detected and take the appropriate action. The 'OMGF | GDPR/DSGVO Compliant, Faster Google Fonts. Easy.' plugin is a powerful tool for most use cases, but understanding its scope is key to achieving optimal results.

Related Support Threads Support