Hello Pedro,
Thank you for your kind reply and for clarifying the possible inconsistencies. I have to emphasize that I only know the Shortpixel plugin and how it works to a very limited extent. So I can only follow logic and very limited methods for image conversion. It should also be noted that neither you nor I can know the actual situation on @ben72’s server. This inevitably leads to the wrong conclusions being drawn if one does not know the exact situation on the affected server. This does not necessarily make it easier to investigate errors and causes.
If @ben72 now says that he deactivated the webp replacement function in the LiteSpeed cache plugin, then the cache plugin logically has nothing to do with the occasional display of webp images. Then, in case of doubt, only the cache can play a role. However, this only applies if the shortpixel plugin changes the source of the tag and the file extension at the same time, depending on the browser support for webp images. If that were the case, then the Short Pixel plugin would be incompatible with the LScache plugin because it would require additional and differentiated cache vary in the .htaccess.
However, you say that the webp images would not even be written to the file system. There is actually no logical explanation for this, especially since the cache plugin has no influence on the wp-content directory. However, it does affect the loading of Javascript or AJAX requests. Therefore one (you) would have to clarify whether the AJAX process you mentioned actually only runs in the backend.
If we can’t find a solution, the plugin support would have to deal with it. I’m only an authorized LiteSpeed Support Partner.
[ Signature deleted ]