Felix Arntz

Thanks for the report. I will have a look at this soon to see whether it can be fixed from within this plugin. For the time being, you might be able to manually skip that iframe from being lazy-loaded by adding a skip-lazy class to it – in case Gravity Forms allows you to modify that iframe accordingly.

Hi, there might be multiple reasons for this. First of all, I’m not entirely sure how PSI assesses whether lazy-loading is available or not, and whether it checks for the loading attribute yet, since that is still rather new.

Regarding the score having dropped, this may be because of the fallback script that is being loaded for browsers that do not yet support the loading attribute.

I’ll reach out to the folks from PSI to get more information on this, but for now I’d say don’t worry too much about this. You know you have a lazy-loading plugin, and I’m happy to hear that it made your site faster. ??

Sorry for the late reply, I’m happy to help and figure out the issue. Can you provide me with some more context on what happened for you? Can you see any error messages being logged in your browser’s developer console?

When I visit your page, it appears to work. Are you still using the plugin or did you try something else?

Hi, this message appears because that image likely doesn’t have width and height attributes specified. Providing these attributes allows for a better user experience and performance on your site as the layout of your page will be clear from the initial HTML load, even before the image is loaded.

It’s recommended to add these attributes to every image.

Hi, the way that Chrome uses lazy-loading with the loading attribute depends on various factors, among them your network connection, how many images are on the page, where they appear, etc.

If you have the plugin active and your images are showing, you can rest assured the plugin works as expected.

You can add this code to either a custom plugin file you create, or alternatively your theme’s functions.php file.

Thanks for the report. Can you provide me with some more context on what happened for you? Can you see any error messages being logged in your browser’s developer console?

Can you see any error messages being logged in your browser’s developer console? I wonder if it’s a conflict with another plugin or potentially how Divi adds that homepage image to the page.

Which browser and version of it are you using? When using the plugin, can you see any error messages being logged in your browser’s developer console?

Hi Molly, can you provide me with some more context on what happened for you? Can you see any error messages being logged in your browser’s developer console? The plugin only deals with images, so I’m curious how it messed up your structured data. What kind of structure data error did you receive?

I’m happy to help and figure out the issue. Can you provide me with some more context on what happened for you? Can you see any error messages being logged in your browser’s developer console? Do you use any other plugin that handles/optimizes images? Maybe there is a conflict.

I’m happy to help and figure out the issue. Can you provide me with some more context on what happened for you? Can you see any error messages being logged in your browser’s developer console?

The native attribute only works in Chrome, that is because no other browser supports it yet. However the fallback script from this plugin should also cater for other browsers. Can you provide me with some more context on what happened for you? Can you see any error messages being logged in your browser’s developer console?

Hi Nic, I’m sorry for the inconveniences. We just released a new version that resolves a few issues related to IE and Edge, would you be willing to try again?

If it still doesn’t work, I’m happy to dig up the root of the issue, if you can provide me a bit more context on the error. Could you open your browser’s development console and let me know if there are any error messages being logged?

Thanks for the report. The plugin relies on the default content rendering mechanisms WordPress core provides, so if a page builder or theme uses an entirely different mechanism, that might be tricky.

If you could send me a link to the site, that might be a good start though so that I can inspect the HTML markup generated.