serpentdriver

Add this to the very top of the .htaccess outside of LiteSpeed markers. This is magic code…. 🙂

<IfModule LiteSpeed>
RewriteCond %{HTTP_ACCEPT} “image/webp” 
RewriteCond %{REQUEST_FILENAME}.webp -f 
RewriteRule ^(.*).(jpg|jpeg|png|gif) $1.$2.webp [T=image/webp,L]
</IfModule>

And this code is still in use:

<IfModule LiteSpeed>
RewriteCond %{HTTP_ACCEPT} “image/webp” 
RewriteCond %{REQUEST_FILENAME}.webp -f 
RewriteRule ^(.*).(jpg|jpeg|png|gif) $1.$2.webp [T=image/webp,L]
</IfModule>

Purge browser cache and the LiteSpeed server cache.

Is there a way to make the guestmode have less of a visual impact on loading the elementor header of the site?

No.

Ok, so we have identified the problem.

There is and never was a problem.

Is there anything the Litespeed plugin can do in this case?

No.

What would you recommend if I want to ensure that those images are also changed?

Loading images via Javascript is generally not a good idea. So the recommendation is to find an alternative way to load these images normally. But that’s your job.

You have the Guestmode enabled. The Guestmode loads the page twice at the initial request. If the Guestmode is enabled the code for the initial request is max optimzed to load the first request as fast as possible. This method may cause display glitches, but only for a very brief moment until the page is reloaded. However, this effect only occurs if your pages are still uncached. You should therefore use the cache crawler regularly so that your cache is warmed up.

Even the imaginary thought of using another plugin as an option is out of the question. I can only tell you that the webp replacement of the LiteSpeed cache plugin works without any problems. Otherwise, other users would have complained about a problem with it several times. If it doesn’t work for you, there must be reasons, because a problem doesn’t arise without a reason. A not uncommon problem is that plugin programmers do not pay attention to the fact that not all files and changes are completely removed when deactivating or uninstalling a plugin. This is the typical problem with 9 out of 10 plugins and therefore regularly causes conflicts and problems. This circumstance makes it difficult to find out the cause of the problems in problem cases like yours.

Formatting using CSS is irrelevant and therefore has no influence on whether webp images are displayed. However, the LiteSpeed cache plugin requires the correct file extension, because the webp replacement in the HTML code changes the file extension from e.g. image.jpg to image.jpg.webp. If a plugin for providing webp images only changes the MIME type via .htaccess, then this plugin is incompatible with the webp replacement function of the LiteSpeed cache plugin.

In order for a plugin from a 3rd party provider to work together successfully, it must first be ensured that it has a corresponding filter function that works in the same way as the filter of the cache plugin. In addition, this plugin must also be able to change the file extension in the HTML code. And finally, the correct cache vary must also be able to be set in the .htaccess. According to my findings, the WebP Express plugin does not meet these requirements, which is also the reason for the problems. You should therefore only use the webp replacement function of the LiteSPeed cache plugin. Any other support when using another plugin for webp use cannot be guaranteed.