OMGF (Pro) — Troubleshooting
First, if you’re using a CSS minification/combination plugin that also has an option to optimize Google Fonts, e.g. Autoptimize, WP Rocket or Asset Cleanup, try disabling that option. It might be interfering with OMGF (Pro). Make sure to flush its cache after changing the setting.
If that doesn’t work, check the list of Compatible Themes to see if your version of OMGF is tested with your theme and or plugins. If an upgrade is required, click here to purchase OMGF Pro. Is your theme not listed there? No worries. Just shoot me a message including your site’s URL and your theme and I’ll see what we can do about it.
OMGF Pro uses a HTML5 DOM validator to scan for existing Google Fonts, because this is much more efficient than using regular expressions. However, when your site’s DOM contains invalid HTML code, e.g. a paragraph-element inside a header-element, the validator will attempt to fix this and this might break your styling.
OMGF Pro contains the option to remove any resource hints pointing to fonts.googleapis.com or fonts.gstatic.com. If you’re a OMGF Free user, upgrade to Pro.
Review your settings on the Advanced Settings tab. If you’re using a CDN, make sure it’s URL contains the protocol (e.g. https://)
When Optimization Mode is set to Automatic, OMGF (Pro) sends any requests to fonts.googleapis.com through its Download API the first time it captures them. Downloading all the font files and generating the stylesheet takes a while. Every consequent pageload will serve the stylesheet immediately, i.e. the stylesheet will be served fast, like any other file.
OMGF Pro serves as an add-on for OMGF. Make sure OMGF is installed when activating OMGF Pro.