I actually had to disable the plugin to get rid of the data URIs.
“also defer inline JS” uses something similar, replacing inline JS with src=”data:text/javascript;base64,xyz…”, but that does not act on images so for now I’m clueless I’m afraid. Do you have a staging site where you could keep AO active so I can have a look?
I’m not sure what to do. I have a staging site on the same server and am not able to get the same issue. It is a clone of the live site. All the same theme, content, plugins, etc.
There is one plugin that is not activated on the staging site because it only allows one active account connection. But I have tried deactivating it on the live site too and still have the same issue there.
Since I don’t see the issue on the staging site, what do you suggest?
how weird … OK, next step; re-enable AO briefly on the live site and then copy/ paste the HTML source (not in developer tools which shows the “living” DOM but ctrl-U in the browser which shows the HTML as received from the server) into a Github Gist or a pastebin.com paste and provide the link so I can have a look at that, maybe that’ll ring a bell for me?
OK, looks like the root problem is that you’re lazyloading image using Rocket Lazy Load and that lazy loading breaks due to AO JS optimization, so excluding Rocket Lazy Load from JS optimization OR switching to AO lazyload will likely fix this. Can you give that a try?
You Rock!!!
I switched to AO lazy load and all is good.
