Frequently Asked Questions

Answers to common questions and troubleshooting steps.

Basic Troubleshooting

Whenever something doesn’t work, the following basic troubleshooting process should be followed:

  1. Identify if you have a cache plugin installed and clear any cache. Alternatively, disable all cache plugins temporarily.
  2. Use the Verify It Works.
  3. If verification process shows it has failed, try to temporarily disable all the plugins and repeat step 1 and 2.
  4. Verification is successful but wrong fonts being used? See below.
  5. Check if you have a font from a 3rd party widget or resource. Automatically loaded embedded Google Maps can cause requests to Google Fonts, however since it’s a remote third-party script, we cannot control it. Usually, for EU GDPR compliance, you will have to hide Google Maps until consent is given using a Cookie plugin like “Cookie Notice for GDPR”.

Once you have performed basic troubleshooting, see the F.A.Q. below if any one of them apply.

If your font has been replaced by the wrong font, first follow basic troubleshooting steps. From there on, it gets technical. You will have to open up your browser Dev Tools console and refresh the page. See if you can find an error like the following:

Access to Font at 'http://yyyyyyyy.com/..../sgf-css/6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7j.woff' from origin 'http://domain.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://domain.com' is therefore not allowed access.

To solve this, follow one of the below:

  • No CDN is used - Normal Web Hosting

    You will have to modify your .htaccess file to add the following:

      <FilesMatch ".(woff|woff2)">
    Header set Access-Control-Allow-Origin "*"
  </FilesMatch>

    If you don’t have an .htaccess or your webhost uses nginx or another server instead of Apache, you will have to contact your webhost to make the equivalent change. For nginx, here’s the equivalent:

      location ~* \.(woff|woff2)$ {
    add_header Access-Control-Allow-Origin *;
  }

  • You use a CDN Provider like MaxCDN, KeyCDN etc.

    If you do use a CDN of some sort, you will have to contact your CDN provider to add the following header to all .woff and .woff2 files:

    Access-Control-Allow-Origin *

    Some CDN providers may have a Headers setting to add your own custom headers but usually you will have to contact them.

Depending on your webhost, this plugin will have a minimal effect on performance after the first run. If you’re on a really slow webhost and have CSS Processing enabled, you should also use a cache plugin.

For simple cache, we recommend the following cache plugins: WP Super Cache (free), WP Rocket (paid).

If you also need minification and other performance features, a combination of WP Super Cache and Autoptimize plugin works well.