ms100

The theme I’m using is Astra. Images get lazy loaded very well, except the WooCommerce blocks background images.
(I think these are the ones with class=”wc-block-featured-category__background-image”.)

So possibly the Woo blocks could be coded in a way that the native lazy load picks up the images and adds the loading=”lazy” attribute automatically.

Or I could maybe add loading=”lazy” manually in the Woo blocks page code.

Or maybe a PHP snippet (like the example in the thread link you gave) could achieve it, something like:

Function set attribute loading=”lazy” IF class=”wc-block-featured-category__background-image”

Thanks again.

P.S. The Storefront theme does not seem to lazy load the Woo blocks background images either

Thanks for the reply. I found one phantom draft in the database and carefully deleted it. It is fixed now, thanks for the suggestions! 🙂

Hi!

Thanks for the suggestions.
I have tried both, but still it says there is a draft.
I deactivated all other plugins, but the draft stays there.
It is not an urgent issue, but it does seem like there is something wrong.
Have you got any other ideas that I can try?
Thanks again.

My Litespeed server loads the web pages in Brotli, until I turn on the caching functionality of the plugin.

Caching is for static content, right? So I don’t understand why these cache-enabled static content pages are loaded GZIP as soon as I activate the caching functionality of the plugin.

I would expect that if a server supports GZIP and Brotli, the plugin would choose Brotli for page caching. So the plugin is not programmed to choose Brotli if both are supported? Then I would have to turn off GZIP at the server level.

I think the best would be if a user could have GZIP and Brotli enabled on the server level, and the plugin would choose Brotli for the static content page caching.

I hope I explained my thoughts well enough.

Thanks again.