@nicklasdenmark12 I checked the score of your website and the only suggestion I noticed from Google PageSpeed Insights regarding “Preload key requests” (https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fwatching.dk%2F&tab=mobile) is for preloading the following font file /wp-content/themes/webify/assets/fonts/circular-regular.ttf
To do that, you can just go to “Settings” -> “Local Fonts” -> “Preload Local Font Files” and add in the textarea /wp-content/themes/webify/assets/fonts/circular-regular.ttf. If you have any caching plugin or one offered by your hosting company, clear the caching and re-test the PageSpeed score. That notice should be gone.
Let me know if it helps!
Hey!
Thank you very much. It went away! But it diddnt necessarily improve my site speed, which i still think is a problem. As you can see in the following picture, this is the next thing, it tells me to take care of.
https://ibb.co/LJrcwzj
and this has something to do with javascribt. Can it be fixed with the javascribt incline, on your pro version? Becuase if you can exlain to me, how to fix this, so i get a faster site, i would like to contribute to your help!
Regards Nicklas
@nicklasdenmark12 based on the report you provided (I’ve also checked it out on Google PageSpeed), you can remove some of the render-blocking CSS by using Critical CSS and async load the rest of the CSS. Or, you can also use “Preload (async)”, but if the CSS that is deferred has CSS that is needed above the fold, the loading of the page will be with a flash of unstyled content (FOUC): https://en.wikipedia.org/wiki/Flash_of_unstyled_content
At the moment, critical CSS can be implemented through Asset CleanUp, but it requires editing the child theme (e.g. functions.php) or via a custom plugin. If you check the following post, you will understand what I mean: https://assetcleanup.com/docs/critical-css-how-to-implement-it-to-completely-reduce-render-blocking-stylesheets/
