OMGF Pro 3.8.0 – Host Google Fonts Locally for WordPress

Leverage Browser Cache, reduce DNS lookups/requests, reduce Cumulative Layout Shift and make your Google Fonts 100% GDPR compliant with OMGF!

OMGF Pro is written with performance and user-friendliness in mind. It uses the Google Fonts API to automatically cache the fonts your theme and plugins use to minimize DNS requests and speed up your WordPress website.

HOW DOES IT WORK?​

After installing the plugin, OMGF will automatically start looking for Google Fonts whenever a page is requested on your website.

All Google Fonts are listed in the Manage Optimized Fonts section of OMGF’s settings screen. There, you can choose to:

• Preload fonts to reduce Cumulative Layout Shift above the fold,
• Unload fonts that’re not used by you, your theme and/or plugins,
• Set a Fallback Font Stack (OMGF Pro required), to further reduce Cumulative Layout Shift, or
• Replace (OMGF Pro required) font-families with system fonts to speed up loading times!

OTHER FEATURES INCLUDE​

• Variable Fonts support,
• Remove unused subsets to reduce the size of the CSS stylesheet,
• Remove Resource Hints (preload, preconnect, dns-prefetch) pointing to fonts.googleapis.com or fonts.gstatic.com,
• Ensure text remains visible during webfont load by forcing the font-display attribute to your Google Fonts,
• Ensure text remains visible during webfont load by forcing the font-display attribute to all your other fonts! (OMGF Pro required),

ADDITIONAL FEATURES IN OMGF PRO​

• Multisite support,
• “Dig deeper” to find Google Fonts and optimize further. OMGF Pro supports:
  • @font-face and @import statements inside inline <style> blocks,
  • @font-face and @import statements inside local stylesheets loaded by your theme and/or plugins,
  • Web Font Loader (webfont.js),
  • Early Access Google Fonts.
  • Material Icons support.
• Modify your fonts’ src: url() attribute fully integrate with your configuration,
  • Use this to serve fonts and the stylesheets from your CDN, or
  • To serve fonts from an alternative path (e.g. when you’re using Security through Obscurity plugins like WP Hide, etc.), or
  • Set a relative path to easily migrate from development/staging areas to production/live, or
  • Anything you like!