Wordpress LScache Plugin: CSS Lazy Load Feature Request?
Last Updated on: Wed, 15 Apr 2026 00:00:02 I came across this video on YouTube about a new CSS attribute (sort of) that allows content to be auto-hidden or auto-revealed when a user is within or outside the viewport. I have tried to manually test it and it works great. Is it possible to have the same implemented on LiteSpeed Cache? Also, if it possible to include some sort of lazy load easing (manually adjustable using percentage) such that it reveals or hides content based on how close a user is within or away from the view port. More sources about its benefits: https://web.dev/content-visibility/ https://css-tricks.com/almanac/properties/c/content-visibility/ Users should be able to manually insert the CSS classes that they wish to lazy load. This topic was modified 7 months, 3 weeks ago by essaund. I think there is similar option the HTML lazyload does this content-visibility has only advantages with really large sites and it should (must) be adjusted for each single site. Otherwise content shifting happens. @CacheCrawler I initially tried it using this documentation but it failed to work. I checked out this post here about it not working and I ignored testing it using the full CSS Selector code. But I also did it wrongly. For example I had set example-code instead of .example-code. I have since corrected it and it works exactly as described here. Thanks so much for such a wonderful feature. @CacheCrawler thanks man. Actually, as explained here introducing contain-intrinsic-size: rule it prevents layout shifts and stuttering when elements on a web page auto-reveal and hide when scrolling. Im so excited to find LiteSpeed Cache has fully implemented it. This feature is exemptional as it has reduced the rendering by over 200% on my webpages from highs of 450ms to approx 150ms now. Yes, that is why said it must be adjusted, but didnt notified with what?., sorry. Not necessarily as you say because the standard 1000px viewport is huge and more than adequate to be honest. No, you are wrong. contain-intrinsic-size defines the area under the fold, not above the fold (viewport). Thats how I understand it, isnt it? Okay youre right but It has a positive effect on the viewport. So far theres no CLS issues when using contain-intrinsic-size without it loading and scrolling on pages is annoying. For reference, Im getting a CLS of 0 when using it, something that I did not have before.
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference