Wordpress LScache Plugin: WordPress 5.5 lazy-loading API compatibility?
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi, seems like WordPress 5.5 is going to introduce lazy-loading API for media and other elements. LiteSpeed Cache already implemented the lazy-loading. How can we prepare to WordPress 5.5 native lazy-loading? If I install LiteSpeed Cache now for WordPress 5.4, can I safely upgrade later to WordPress 5.5? Hi, Well , there is no way to know for sure about compatibility until it is released and we checked. We will check when WP 5.5 is out for this matter. can I safely upgrade later to WordPress 5.5? Yes, of course , and if in any case , any thing went wrong for lazy load , you can just simple turn it off for the time being Best regards, Now I use WordPress 5.5 and by default image lazy loading is turned on in WordPress core. I see the loading=lazy attribute in the source code for the img elements. On the LiteSpeed Cache Page Optimization ? [4] Media Settings ? Lazy Load Images is turned OFF for me (plugin version 3.4.2). Question: should I continue using the default WordPress image lazy loading, or is the LiteSpeed Cache lazy loading feature better than the built-in lazy loading in WordPress 5.5? Or is it just a legacy feature for those users who still run older WordPress versions? Hi, If I were you , I would keep LSCWPs lazy enabled , WPs lazyload may not work well with some older version of browser , at least thats what I heard so far, didnt test myself though. Best regards, According to this: https://caniuse.com/loading-lazy-attr The loading attribute which WordPress core uses has a global support of 74%. I see that LiteSpeed Cache uses the data-lazyloaded=1 attribute. But I couldnt find the global browser support for this data-lazyloaded=1 attribute. Is it better supported than the loading attribute? The loading attribute is not supported by Safari and Safari iOS. I see that even after enabling the LiteSpeed Cache lazy loading feature, the WordPress core still inserts the loading=lazy attributes for img elements, isnt it a problem? No, that data-lazyloaded=1 is LSCWPs own attr with its lazyload JS to lazyload images, not native browser function. loading is not working on Safari , thats probably one of the major set-back. no , thats not exactly a problem , well , maybe adding few bytes in size is a problem , there is some code snippet in internet to disable WP5.5 lazyload And is the LiteSpeed Cache plugins lazy loading feature working even on Safari and Safari iOS? yes
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference