At the optipic service, I recently noticed a new functionality in which all of this is already in the box. And the original image must also be optimized/compressed – so that even for browsers without WebP support, images will be optimized (lighter in weight) – this is the third! version of the file. And give the right version depending on the browser. ![]() Webp (for WebP-enabled browsers) and original image. Therefore, you must always store at least two versions of each image. For example, iOS Safari, regular Safari, IE – do not support WebP. WebP has such a nuance – not all browsers support it. Then when the LiteSpeed Cache plugin reports that all your images have been optimised, I suggest purging the LiteSpeed cache to make sure all pages show optimised images as they should. So early on you’ll probably have to keep an eye on things and send another couple of optimisation requests once each level completes. Here’s how many images you can send for processing at each level: When enough of the first batch of images have been sent, optimised and pulled back to your host successfully you can click Send Optimisation Request again and each time you’ll be upgraded to another level, allowing you to send more images for optimisation each time.Īutomatic chron optimisation requests can only start to be sent when recovered credits have reached 1200 or more. Don’t worry though, it’s all completely free. The process starts gently to make sure both servers talk nicely to each other before establishing a more intimate friendship, and this is managed through credits. Give it a couple of minutes to do its thing before refreshing and hopefully you’ll start to see reports of optimised images being successfully pulled back onto your hosting. This will send a batch of up to 100 images to LiteSpeed’s image optimisation server. Download and install it now, it’s a pretty banging tool. We’ll be using the Litespeed Cache WordPress plugin, the official WordPress caching companion plugin for servers running LiteSpeed. Update: Since MacOS Big Sur Safari now supports the WebP file format.īut not to worry, this method adds a rule to the website’s htaccess file that makes sure WebP images are only served to browsers that can handle them. As the ever useful website details, although the web image format has broad compatibility, crucially Apple’s Safari browser has been slow to adopt it, putting them in the same bracket as Internet Explorer. Will WebP be served to incompatible browsers? A 30% reduction is a good expectation for the average conversion to WebP. ![]() Images with less detail receive the biggest cut in file sizes. * %1\.(jpe?g|png).webp Ĭan somebody shed some light into this? I am a beginner on htaccess and I know I am not using the correct syntax on this to make it work.In my test of the method of WebP compression that I describe below file sizes were cut down by anything between 21% and 93% of their original sizes. I tried changing the RewriteRule line to this but it didn't work: RewriteRule. I think the problem is in the RewriteRule. Header append Vary Accept env=REDIRECT_accept Instead of changing the extension, my converter added the new extension to the full name of the picture. The snippet is not working because of the name of my webp pictures. I am trying to show webp pictures on my website where there is a jpeg or png picture using LiteSpeed Web Server and an htaccess file.
0 Comments
Leave a Reply. |