WAIT: EWWW Image Optimizer doesn't output WebP in <main> on pages controlled by Bricks. Can you replicate?

Bugs
1

Hi guys,

I have been trying to figure out what is going on, and it seems to be related to Bricks, though I am not 100% sure.

EWWW is a great image optimizer, and it has worked for me nicely on non-Bricks sites.

But pages created with Bricks do not have WebP in the source. The affected WebP files exist on the server. I can open them in the browser. Strangely, the logos in the header and footer do get output as WebP.

I created a fresh site with only Bricks, EWWW and Wordfence and it is the same. Creating a post with Gutenberg and displaying it without a Bricks template - and the very same WebP files show up (same site, same server).

Switching to another theme (2023, GP) - WebP usually shows up, but not in 100% of the times, which confuses me a little.

Starting a fresh site with GeneratePress on the same server - WebP with EWWW works nicely.

I use Cloudways and redirection to WebP is activated on the app level, but deactivating it doesn’t help. I tested Bricks 1.9 and 1.7. I tested all combinations of WebP delivery in EWWW and even forced WebP output.

The same PNG logo does have WebP markup in the header but not when added as image in <main>. It does seem like a Bricks issue, but I am not 100% sure. Can you guys replicate it?

The WebP Express plugin does work fine in Bricks for me, but EWWW has some nice features, so I would like to stick to it.

2

Hey Tom,

thanks for your report.

Please send some temporary credentials to help@bricksbuilder.io so we can have a look at your setup. Please include a link to this forum thread and let us know where exactly you included the images that are not working as expected.

Best,

André

3

Thanks, André. I sent the login details yesterday.

4

I have found out that disabling lazy loading in Bricks fixes it for normal images, but I still don’t have WebP for background images, which EWWW does support.

1 Like
5

This also just worked for me!