adamewww

With that, my guess is it’s loading in an iframe, yes? Can you try adding “iframe” without the quotes in the lazy load exclusion box.

I apologize, as I noticed that I don’t think I posted my response to this! I’m sorry for the delay.

I think at this point in order to see what is going on we would need to have you generate a debug log. You can do this by:

1. Go to the support tab of the EWWW IO plugin settings and check the box for Debugging and save.
2. Go back to the support tab and click on the ‘Clear Log’ option.
3. Upload an image and wait about 30 seconds to a minute.
4. Go back to the support tab and click on the ‘Download Log’ button.
5. Uncheck Debugging and save.
6. Send the log and the name of the image you uploaded directly to us: https://ewww.io/contact-us/

Hi @haman251

I think I am seeing that you want it to be on a higher up element in the DOM but unfortunately, the class has to be on the image itself in order to skip lazy loading. Could you perhaps put a common naming scheme on the image names and put that in the lazy load exclusion box? Or in other words, is there a way to reference the specific images, as the exclusion box could then be used?

Hi @dylandawg

The compression in the free version of the plugin utilizes the tools that are available on your server to optimize those images. Those tools are great, but aren’t going to be as effective as something like photoshop. I did upload one of your images (the 2.3MB one) to a site with our premium compression and it brought it down to 146KB.

Hrm. Is it possible that the import process isn’t running wp_generate_attachment_metadata like a normal upload (as that is how EWWW IO normally hooks into the process)?

Otherwise, I think we might need to generate a debug log to see if we can see what’s going on. To do that:

1. Go to the support tab of the plugin settings and check the box for debugging and save
2. Go back to the support tab and select the option “Clear log” so we have a clean slate
3. Import an image via the process that is having the issue and give it about 10 seconds.
4. Go back to the support tab and click on “Download Log” to save the debug log
5. Send the name of the image you imported along with the debug log over to us: https://ewww.io/contact-us/
6. Uncheck the box for debugging and save so it doesn’t keep running.

Hi @kimikaze

Have you tried different images? It is possible that the WebP versions aren’t being created because they are larger than the original (thumbnails). Our plugin won’t generate a WebP if it’s larger than the image it’s creating a WebP for (as that’s the point of using WebP). Otherwise, I believe it should work, though I don’t know that I understand why you are wanting to disable async?

Yes, the WebP file that is generated sits next to the original JPG, so if it doesn’t have permission to create that file there or if the file is removed, then it won’t work.

I’m going to resolve this thread, however, if you have further questions, please feel free to open a new one.

I’m going to resolve this thread however if you have further questions, please feel free to open a new one.

Hi @jukkasalm

As we haven’t heard anything about this in a while, I’m going to resolve this thread. However, if you have further questions, please feel free to open a new one.

Hi @henrybaum

I’m going to resolve this thread as we took it to personal emails. I hope things got resolved as I haven’t heard anything in a while. If you have further questions, please feel free to open another thread.

Hi @schleewoon

From what I can see on your site, it looks like you also have WP Rocket’s lazy loader running. It’s possible that it was a lazy load conflict since turning it off in EWWW seemed to fix it. However, some of the exclusions you tried should also have worked (like the last one). Did you clear your cache after trying them? Or you could try excluding an image by filename, so Porto-Carras-Grand-Resort-1024×434.jpg, for example.

Otherwise, I would probably need to see it in action to see what’s going on.

For WebP when using WP Offload Media, really, you will want to use JS WebP delivery method with the only specific instructions having to do with whether or not you have local copies of your images. If not, you will want to use Force WebP (and maybe WebP URLs): https://docs.ewww.io/article/121-webp-urls-and-force-webp

Hi @mysuel

Other than the standard requirements that are mentioned on the plugin page here: https://www.ads-software.com/plugins/ewww-image-optimizer/ , it is recommended that you have exec() enabled. https://docs.ewww.io/article/29-what-is-exec-and-why-do-i-need-it

Great, I’m glad you were able to get it cleared!