Self-Hosted Google Fonts doesn’t work with Litespeed plugin

Hi,

Could you please provide the report number ?

you can get it in toolbox -> report -> click “send to LiteSpeed”

Best regards,

Hello @qtwrk

Here’s the report number GYTVXCHY

Hi,

Please try disable

CSS Combine External and Inline

save and purge

best regards,

Thanks for your reply.

Now it’s calling the self-hosted fonts alongside dialing them up from Google’s repository.

Hi,

okay , please try disable all options in CSS optimizion , save and purge , see how it goes

Best regards,

If I disable CSS options it works great. No dialing up of Google fonts. However, now my CSS won’t be optimized. Should I use it alongside other cache plugins?

I have noticed that Autoptimize doesn’t dial up the fonts from Google. It calls them from the theme. But now, I’m not sure if the plugins will conflict each other if I use them both.

Hi,

okay , this indicates one of the options was causing it

now please try enable them back one by one to locate which one was it

Best regards,

I have decided to add preloading for the fonts, which has greatly reduced the call up time and render blocking to 50ms<

I think I can work with it as it is.

Maybe it would be better if lscache can add an option to store all the google stuff locally and preload the used fonts on the related pages.

@webhostercloud true. Litespeed Cache sends so many requests for Google fonts and the render blocking of the requests is so enormous.

I can see debate about adding preload and caching local fonts dating back from 2018. I wonder what’s taking them long to implement the feature.