You have the latest version installed? Because Manual and Automatic optimization mode were merged into the free version as a hybridized optimization mode.
Anyway, try this guide. In most cases just using the Preload feature properly takes care of CLS caused by Google Fonts.
Let me know if you have any other questions!
I have whatever version is available from the wp plugins page for your plugin.
I think I figured it out and thanks for the link.
Update: when checking my page speed insights again it is telling me this file is a render blocking issue:
wp-content/uploads/omgf/shapla-fonts/shapla-fonts.css?ver=1649559414
Is that supposed to happen?
-
This reply was modified 3 years, 12 months ago by
nootkan.
when checking my page speed insights again it is telling me this file is a render blocking issue:
Yes. Stylesheets that’re critical for the proper rendering of your page should remain render blocking. Otherwise they’ll cause Cumulative Layout Shift.
Actually once I emptied your plugin cache my performance increased to an acceptable level (98) with 0 CLS.
So I guess I didn’t need to deal with the google fonts after all.
However, I noticed when I deactivated your plugin the performance score dropped and when I activated it again it went back to its original acceptable score previously.
Must be something else your plugin does other than deal with google fonts.
-
This reply was modified 3 years, 11 months ago by
nootkan.
I wouldn’t be able to answer that question without an actual URL to look at.
You can easily compare performance with OMGF enabled/disabled:
– You can either enable Test Mode (so OMGF is only enabled for logged-in administrators) and append the ?omgf=1 parameter to the URL when running it thru PageSpeed Insights. This will load results with OMGF enabled. The run it again without the parameter and results will be loaded with OMGF disabled.
– You can also keep Test Mode disabled (so OMGF is enabled for everyone) and append ?nomgf=1 to the URL when running it thru PageSpeed Insights. This will load results with OMGF disabled. Then run it again without the parameter and results will be loaded with OMGF enabled.
Whatever suits you better 🙂