I see several images that use an “owl lazy load”, which is not one that we support. It looks like that is from your theme, so they can either implement the WebP themselves, or you can just turn off that lazy loader.
Hi
I’ve already disabled the lazyload option on the theme settings
but the background images (e.g flip box module/section) are still showing jpg and not the webp version
Unfortunately, those are not background images originally. They are added to the page as ‘data-frontfullimage’ attributes on a ‘flipbox’ div element. Nothing we can do about those, since it is completely JS driven. You’d have to ask that plugin/page builder for WebP support (or find out if they have a way we can hook into their JS image loading process).
Hi
I’ve tried to create a test page and added normal background images on rows
https://erjjio.globalgoodawards.co.uk/test-page/
for the first background image it has the 2x retina version (Using WP Retina 2x Pro)
while on the second image it has the normal one (without 2x), but still both background images still not showing the webP versions
I’m seeing this on the page:
https://erjjio.globalgoodawards.co.uk/wp-content/plugins/litespeed-cache/assets/js/lazyload.min.js
It’s possible the Litespeed plugin is interfering a bit, can you make sure their lazyload option is disabled please?
Otherwise, those div elements look like perfect candidates for lazy load & webp to me, so we should do some debugging. We’ll need to take this into email support though, as the logs can get a bit large for posting here: https://ewww.io/contact-us/
