OMGF parses a page's HTML for stylesheets loading Google Fonts using the Google Fonts API: https://fonts.googleapis.com/css or https://fonts.googleapis.com/css2.
Some themes and/or plugins add Google Fonts using different methods, e.g.
- Using @import and/or @font-face statements in a CSS stylesheet,
- Using @import and/or @font-face statements in inline <style> blocks,
- Using Web Font Loader,
- Using Early Access fonts not available (yet) through the regular Google Fonts API.
This section of OMGF Pro’s user manual zooms in on each of the available options and clarifies how it influences OMGF Pro’s Google Fonts Processing and Detection behavior. Each chapter also includes an example of a scenario when this feature should be used.
To keep things readable, this section of the manual makes a few assumptions:
- You are slightly familiar with the terms: HTML, source code, header, footer, (the not human) body, stylesheet, hyperlink and parsing,
- You know how to open your browser’s Developer Console and lastly,
- You have a general idea of how Google Fonts are loaded into your website.
I’ll do my best to keep things as humanly readable as possible, but please don’t shoot me if things get too technical for you.
Advanced Processing (Pro) options
Let’s take a closer look at each of the available options and find out whether you should enable this option for your WordPress site.
Process Inline Styles
While OMGF scans for
<link> elements, this option scans for inline (wrapped in
@import statements pointing to
@font-face statements pointing to
Should I enable Inline Styles processing?
@import statements are less commonly used to include Google Fonts on pages. I found
@font-face statements to be used more often.
Search your site’s source code for references to
fonts.googleapis.com/css. If you get hits similar to this, you should leave this option enabled:
font-family: 'Open Sans';font-display: swap;
src: url(https://fonts.gstatic.com/s/opensans/v29/memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4taVIGxA.woff2) format('woff2'); }
The values for each of the mentioned attributes will differ and could include other attributes, such as
unicode-range. Like in this example, they might not be defined at all.
Process Local Stylesheets
While Process Inline Styles scans for both
@import statements in your HTML document, Process Local Stylesheets scans for
@import statements inside any stylesheets loaded by your themes and plugins.
Should I enable (in) stylesheet Import processing?
It takes a bit of an advanced approach in your browser’s Developer Tools to check if stylesheets include
@import statements loading Google Fonts.
You’ll want to search through all files for phrases like fonts.googleapis.com and fonts.gstatic.com.
Most browsers (e.g. Firefox and Chrome) include ways to search through files.
– In Chrome, when Developer Tools is opened, press CTRL / CMD + Shift + F in any tab.
– In Firefox, open up the Debugger tab and press CTRL / CMD + Shift + F.
– For other browsers I suggest you use Google and search for something like [browser name] search through files developer tools.
Process WebFont Loader
WebFont Loader is a library created by Google and Typekit which allows asynchronous loading of Google Fonts (and other webfonts.) OMGF Pro handles various ways to detect if this library is being used. Some of which are:
- Check if
webfont.jsis present in the page source,
- Check if WebFont Loader’s configuration is present anywhere, usually called
Should I enable WebFont Loader processing?
The easiest way to find out if WebFont Loader is being used on your WordPress instance is by opening up your browser’s Developer Tools (by pressing F12) and navigating to its Network tab.
Now visit your website in the same browser window and the Network tab will be populated with several requested files.
By filtering the requests by phrases like ‘webfont’ you might find files being loaded, calleg e.g.
If any of these requests are present, you should enable Process WebFont Loader for OMGF Pro to properly detect any Google Fonts (if present)
Process Early Access
Google’s Early Access fonts are openly available beta version of font files.
The usage of these fonts should be considered ‘exotic’. I.e. if your WordPress site is written in a Middle Eastern or Asian language you might be using a beta font.
For English (or any other European language, e.g. Spanish, French or German) it’s probably safe to keep this option disabled.
Should I enable Early Access processing?
Early Access fonts use the same methods as regular Google Fonts.
Follow the methods in the previous chapters to figure out if your site makes requests to files originating from