[ad_1]
I am having an issue with performance only on computers. Google fonts are causing a CLS with litespeed.
I am using a litespeed enterprise server, and their CDN.
Litespeed settings:
Font Display Optimization: Set to swap
CCSS Per URL: On
Load CSS Asynchronously :On
Load Google Fonts Asynchronously: On
Font Display Optimization: Swap
My full settings: [https://easyupload.io/x7hu3s](https://easyupload.io/x7hu3s)
Any input would be greatly appreciated. This seems to be a common issue on their support forum page for the plugin. I opened my second thread for this as the first time, I thought I solved it.
[ad_2]
I recommend checking out my pagespeed guide, should have everything you need for Litespeed Optimization Resources, Elementor Optimization and Font optimization. I’ve dedicated almost 6 years collecting all of the info, and it’s now 170 pages. The table of contents is the document outline, I recommend opening that since it’s content dense.
https://docs.google.com/document/d/1ncQcxnD-CxDk4h01QYyrlOh1lEYDS-DV/edit?usp=sharing&ouid=114514252262811175804&rtpof=true&sd=true
Please let me know if anything is unclear or you need me to expand on something, happy to help.
Edit: As to your CLS issue that is more likely related to images than fonts or LiteSpeed Webserver specifically, I’d imagine that’s either a misattribution or your font files are large and should be compressed and subset.
There are a bunch of other font optimization tools and techniques listed in the guide that at the which at the very least should heavily mitigate the problem if it is related to LiteSpeed itself.
Have you tried turning off the optimizations?
If the layout shift is from the fonts changing size (hard to say for sure without seeing the site) then I’d set the font display to block rather than swap.
[https://pagespeed.web.dev/analysis/https-koschsrealestatephotography-com/uhwxkj8r3e?form_factor=desktop](https://pagespeed.web.dev/analysis/https-koschsrealestatephotography-com/uhwxkj8r3e?form_factor=desktop)
Funnily enough, you’re getting 100 on desktop and mobile – likely because your first slider image isn’t loading properly.