Hi dkddi,
I have tested the BJ Lazy Load / WebP Express combination, but found no problems. The lazy loaded images are loaded with content-type: image/webp in Chrome.
I examined the way BJ Lazy Load works as well:
1: A filter replaces the image tags with image tags that does not have “src” attribute, but which have copied the src value into a “data-lazy-src” attribute.
2: A javascript function sets the “src” attribute to the one set in “data-lazy-src”, when image is to be loaded.
This strategy is perfectly compatible with WebP Express, as the image request to the server will be the same as usual. The request therefore contains the important “accept: webp” header that will trigger WebP Express to serve webp rather than the jpg.
I haven’t tested with gtmetrix and pagespeedinsites… But I would guess that it works there as well, and we need to examine the compatibility with the other plugins you mention
I now installed Fast Velocity Minify along with BJ Lazy Load and WebP Express. Works as well. Using standard settings.
Added WP Fastest Cache to the mix. I checked the “Cache system: enable” checkbox, but left the others off. It still works.
You are very welcome to send me credentials so I can poke around 🙂 – My email is [email protected]
Thread Starter
dkddi
(@dkddi)
Hello again, Bjørn.
Thank you for such a quick response. And thank you for your efforts. I think you are probably correct; that it’s a plugin conflict. I’m satisfied with your testing method and appreciate the tech support. Again, it’s a cool plugin. I will add to this thread once I find the culprit.
Have a great day!
-d