tinify
[Feature request] webp conversion
As the Tinify API now supports converting images to webp, it would be nice to also have that in the plugin.
As a first step converting the images would be sufficient, for my workflow simply generating webp files with every optimized file would be perfect and all that is needed. A checkbox in the settings: Generate webp and if checked here we go:
Lets say i use png images, a file called image.png should be optimized and saved as usual, after that we can simply add a conversion step call the API and generate image.png.webp
The serving of the file can be done via rewrite rules in .htaccess or nginx config as a first step.
That would be wonderful for all of us currently struggling with other optimization plugins which will never reach the quality of the tiny panda :-) I would be glad to also code parts of it, if needed.
Also for the WordPress-plugin, i noticed that the compression is far as good as the web-based. Picture A on web Compression: -89% Picture A on wordpress Compression: -32%
Why is it such a big difference?
Hi there,
Thanks for reaching out!
The compression using the plugin or using the web interface is the same one. But I just entered to WordPress and I think I understood where is the confusion.
In the next image you see that the total savings are 18%. But it is in total, taking into account the sizes that have been compressed and the ones that did not.
In this other image (clicking on Details) you can see that the original size has been compressed to almost 50%, even if the combined compression is around 18%.
I hope this helps. Have a nice day.
Kind regards, Pablo Pérez de Ciriza
We made it even easier to speed up your website! Curious? Sign up now for a free CDN trial at tinify.com/cdn ( https://tinify.com/cdn ).
tinify/wordpress-plugin on April 14, 2024 at 8:48pm wrote:
Also for the WordPress-plugin, i noticed that the compression is far as good as the web-based.
Picture A on web
Compression: -89%
Picture A on wordpress
Compression: -32%
Why is it such a big difference?
— Reply to this email directly, view it on GitHub ( https://github.com/tinify/wordpress-plugin/issues/26#issuecomment-2054152198 ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AFK24QBKNN4Q2QYNOEIMY5LY5LFN5AVCNFSM6AAAAAAR4YENO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJUGE2TEMJZHA ) . You are receiving this because you are subscribed to this thread.Message ID: @.***>
tinify/wordpress-plugin on March 17, 2023 at 6:07pm wrote:
+1
— Reply to this email directly, view it on GitHub ( https://github.com/tinify/wordpress-plugin/issues/26#issuecomment-1474144753 ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AFK24QFU2MYZM5WDYLBHG3DW4SK4VANCNFSM6AAAAAAR4YENO4 ) . You are receiving this because you are subscribed to this thread.Message ID: @.***>
tinify/wordpress-plugin on November 10, 2022 at 5:43pm wrote:
As the Tinify API now supports converting images to webp, it would be nice to also have that in the plugin.
As a first step converting the images would be sufficient, for my workflow simply generating webp files with every optimized file would be perfect and all that is needed. A checkbox in the settings: Generate webp and if checked here we go:
Lets say i use png images, a file called image.png should be optimized and saved as usual, after that we can simply add a conversion step call the API and generate image.png.webp
The serving of the file can be done via rewrite rules in .htaccess or nginx config as a first step.
That would be wonderful for all of us currently struggling with other optimization plugins which will never reach the quality of the tiny panda :-) I would be glad to also code parts of it, if needed.
— Reply to this email directly, view it on GitHub ( https://github.com/tinify/wordpress-plugin/issues/26 ), or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AFK24QBDPEL5UBLCFDTAGLTWHUQ4FANCNFSM6AAAAAAR4YENO4 ) . You are receiving this because you are subscribed to this thread.Message ID: @.***>
We have released conversion in 3.6.0! Currently, it only supports picture elements. Server side .htaccess or nginx configuration is in the works!
