Hai Zheng?

Thanks for the case. We can update the realtime calculation to a manual calculation if the group is a huge number.

Ignoring timeout isn’t a solution.

This is a good point and nice concern. We need to keep wp-options table light weight.

Lets move it to file in the following v5.x versions.

BTW, surprised that you have that many 404 images ??

Thanks for your review:)

Curious why you have that many excludes LQIP data?

You can see threshold: 300, from litespeed-cache/assets/js/lazyload.lib.js L35.

Done in v4.7-rc3. Thanks.

@cbdfactum In v4.7-a20, there is litespeed_guest_off=1 added. You can use this in your query string to bypass guest mode for that link.

Query Monitor is a pretty nice plugin. I noticed that issue as well after upgrade to WP v6. However, after upgraded all the other plugins, that issue is gone.
Have you upgraded other plugins as well? Especially WooCommerce related ones?

You can also consider to use JS to control that css class.

Ref: https://github.com/litespeedtech/lscache_wp/blob/master/readme.txt#L262

You don’t need extra lazyload plugin to suppress WP ones.

In our latest changes, WP lazyload is already auto disabled.

That condition is insufficient. Also need to turn off WP initialized OC.

This is added in v4.7-a11. You can try it via Beta Test.

Thanks.

Done in https://github.com/litespeedtech/lscache_wp/commit/7f0407d9be3395dd05e586c020e5f98001e23e40

You can use Beta Test to try it before v4.7 release.

Yes this is in our todo. Thanks for the feedback.

Confirmed and reproduced. It happens only on PHP v8.1+.

This is fixed in v4.6-a6. You can try via Toolbox: https://github.com/litespeedtech/lscache_wp/commit/3caf1e5c53a9d1f4f044ac4e089cf7eaa967271c

Thanks for the feedback.

Please try https://github.com/litespeedtech/lscache_wp/commit/3abf315ec93561893918187cf2c724e9d373349a v4.6-a4. It will respect your cache settings.