I not can look the images in webp format

I havent tested those browsers. But as both Yandex and Vivaldy are blink-based browsers (and thus uses the same motor as Chrome), they should be able to display webp-images.

Beware that the plugin doesn’t redirect jpegs to webp, but it simply serves webp when jpegs are requested. You need to inspect the response header to see whether you actually got a webp or a jpeg back.

Can you test with a Chrome browser?
Can you provide a link to your blog?

Regards,
Bj?rn

I shall test out the Vivaldi browser one of these days…

Hi, this is the link for my blog with the featured image

cazathemes.com/cazathemes-encuentra-tu-theme-wp-favorito/

I am not sure how testing, with another plugins I only download the image or open in another tab and after I open with Irfanview: irfanview show a warning indicating that the image has a .jpeg extension but is an image in webP format

Thanks for support

Good news, It is working just fine ??

When I browse to:
https://cazathemes.com/wp-content/uploads/2018/10/cazathemes-presentacion-web-optim.jpg

And open Web developer in chrome to see the response headers, I get this:

accept-ranges: bytes
alt-svc: quic=”:443″; ma=2592000; v=”35,37,38,39″
cache-control: public, max-age=604800
content-type: image/webp
date: Sun, 28 Oct 2018 07:29:07 GMT
expires: Sun, 04 Nov 2018 07:29:07 GMT
server: LiteSpeed
status: 200
vary: Accept
x-webp-convert-status: Serving existing converted image

Notice the “content-type” header says “image/webp”
Also notice the “x-webp-convert-status”, which is a custom header provided by the plugin.

So, your web server is now serving a webp image for Chromium, when a jpeg is requested. The “content-type” header tells your browser that it is in fact a webp image. The browsers look at the “content-type” header to determine the image format. So even though the image has a jpeg extension, the browser knows it is a webp image. Browsers doesn’t care about the file extensions, only the “content-type” header.

However, if you save the image, and plan to use it for something else, you should change the extension to “webp”. The content type header is not saved along, and image programs such as IrfanView expects the file extension to match the image format.

By the way: In an early development version of the plugin, I had the jpegs *redirect* to a url ending with “webp”. This redirection however costs a bit performance wise, and not needed, as browsers are looking at the content-type header rather than the file extension. So I removed the redirection. If I had kept it, however, you would have had an image with “webp” extension, when you saved a file.

Thanks for support.

I would like some option for verify the images are serving in webp format…

I dont can look the kilobbytes in webp format, I think its a important information

Thanks again

Yeah, good idea. I could provide a test button, which makes a request to an image, and detects if a webp is returned. Actually, I already have this idea on the roadmap: https://github.com/rosell-dk/webp-express/issues/16

I also have statistics on the roadmap. It is nice to know how much you save, and have saved.

Btw, you can add “?debug” to any image url, which will trigger a reconversion AND provide a report. If this works, webp serving also works. Actually, the test-link that is displayed after saving settings gives you such link.

Try it!
Browse to this url:
https://cazathemes.com/wp-content/uploads/2018/10/cazathemes-presentacion-web-optim.jpg?debug

As this displays a report, it is a confirmation that webp serving works. Also note, that the report includes information about the reduces size: “Reduced file size with 41% (went from 96 kb to 57 kb)”

• This reply was modified 6 years ago by rosell.dk.

Ok, thanks for support

Great