See what happens if you use our Lazy Load function alongside the JS WebP method. That’s how we handle CSS background images withe WebP in EWWW IO.
No changes… images are delivered as webp, but not the described div images. I have tested your lazy load function with both webp delivery methods.
the div image way is a common way to deliver images. In this cae this is done by Smart Slider 3 if you like to test it on your site.
Are you able to provide a link to a page where you are using Smart Slider 3?
No public link… However the point is, that the code I sent can’t be changed in webp. This has nothing with Smart Slider 3 to do… this will hapen with all div images
The code you sent should be changed to WebP via our Lazy Loader, because our lazy loader supports any div with an inline style attribute that contains a background image. Additionally, it supports list item, link, span, and section tags.
BUT the code I’m seeing from Smart Slider cannot, because it specifically disables lazy loaders with the ‘data-no-lazy’ attribute and the ‘skip-lazy’ class.
I’ve checked the HTML code for the default tutorial slider, and two other templates that use div & img tags, and all of them disable lazy loading intentionally.
The only way I can see to get WebP with Smart Slider is to use server-based rewriting. If your server doesn’t support it (or you’re using Cloudflare), you can offload the image delivery to our Easy IO system (a CDN): https://ewww.io/plans/
–note that the forum rules don’t allow discussion of paid services, so if you have questions about that, use https://ewww.io/contact-us/
