Hi @teintensivo
I am glad you have managed to fix the problem. Anyways I took a quick look on your site, and I think the original problem was caused by a third party plugin, as there are some third party classes on our img elements:
- jetpack-lazy-image
- jetpack-lazy-image–handled
which are indicating that, our images are getting modified by JetPack, probably by their Lazy Load feature.
If you enable our Base64 encoding again you could confirm this problem easily by disabling JetPack, then clear you cache ( if you have any ) and check the results on the frontend if that fixes the problem or not. If it does, then you should exclude our images from the Lazy Loading feature of JetPack, as they are messing up the data image source of base64 images.
According to their documentation:
https://jetpack.com/support/lazy-images/
see “Exclude specific images” section, they should automatically exclude the images with the “skip-lazy” class from their Lazy Loading feature. However our images have that class by default, yet JetPack still Lazy Loads them. So you should probably disable their Image Lazy Load feature:
Or if you would like to continue using it, then I would suggest you to get in touch with JetPack and ask them about why these base64 images with the “skip-lazy” class are not getting excluded from their Lazy Loading.
Of course if you prefer, you can continue using the arrows as images ( by disabling our Base64 option ), but it is good to know that the Lazy Load feature of Jetpack might cause problems for other base64 images as well.
Best regards,
Laszlo.
