Inconsistent interpretation of Google fonts

[ja...@idiomgenerator.com]

For performance reasons, I decided to implement Google and Material icons fonts asynchronously, using the following code:

 <script>
 WebFontConfig = {
 google: { families: [ 'Material+Icons', 'Roboto:100,300,300i,400,500:latin' ] }
 };
 
 (function(d) {
 var wf = d.createElement('script'), s = d.scripts[0];
 wf.src = 'https://ajax.googleapis.com/ajax/libs/webfont/1.6.16/webfont.js';
 s.parentNode.insertBefore(wf, s);
 })(document);
 </script>

This code is, however, interpreted differently on different pages:

• On one page (https://www.idiomgenerator.com/essentials) PageSpeed Insights states that it is a render-blocking CSS resource, giving me a horrible score as a result.
  
• One another page (https://www.idiomgenerator.com) PageSpeed Insights says that the same exact code is okay, not even mentioning it under the "Optimize CSS Delivery of the following:" heading.

The code on both pages for asynchronous implementation of the fonts is exactly the same. But the interpretation of it is vastly different.

Any ideas on why is that?