Hello @jocoweb
I am sorry about the issue you are having with render-blocking fonts.googleapis.com and I am happy to assist you with this.
fonts.googleapis.com is an external (3rd party) resource and therefore can not be handled by W3 Total Cache or any other plugin for that matter.
To dynamically access these fonts, Google offers an API service so that developers building a theme, plugin or any other services can use an API call to download the required font families from Google’s domains.
When a page uses Google fonts, the browser will try to download all relevant font files to the browser’s cache before rendering the page content. It is essential for the browser so that the text can be displayed in the proper font. Browsers need these fonts for the first time and after the initial download browser will cache the fonts to avoid downloading the same fonts each time thus improving the page loading speed.
This being said this is a “first load” issue, and every time you test the page it’s a “first load”.
I hope this helps!
thank you for your answer, but I didn’t understand the solution, you could explain in a simpler way, thanks and good work.
Hello.
g.
Hello @jocoweb
Sorry if I was not clear. W3 Total Cache can not handle external resources such as fonts.googleapis.com. In the previous message, I tried to explain how fonts.googleapis.com works.
Some plugins and themes may use stylesheets to call Google fonts. If you do not want this you should avoid those plugins and themes and use the theme which uses generic fonts and not dynamically calling Google fonts and download and deliver the required Google fonts locally.
I hope this helps!
