[wp-trac] [WordPress Trac] #55443: Create WebP sub-sizes and use for output

WordPress Trac noreply at wordpress.org
Thu Jun 16 23:24:23 UTC 2022

#55443: Create WebP sub-sizes and use for output
 Reporter:  adamsilverstein                      |       Owner:
                                                 |  adamsilverstein
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Media                                |     Version:  6.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  testing needs-dev-note needs-docs needs-user-  |  performance
  docs                                           |

Comment (by studiolxv):

 @adamsilverstein, First of all thank you so much to everyone here for
 helping bring webp (and hopefully .jxl upon global adoption) to WordPress.

 That said, after installing **Performance-Lab** and running a few upload
 tests I've run into a dilemma where the 'full' size .webp is larger (201
 KB) than my original pre-upload imagick converted .jpg (1920x1280 126KB
 using `-quality 25`). Even the new .jpg '1536x1536' size came out larger
 at (262 KB).

 In the mogrify or magick tests I've run locally with `-quality 80` or
 higher the results do not seem to offer the amount of compression to make
 the automatic conversion to .webp warranted upon upload.  When I use
 imagick locally pre-upload I tend to compress to `-quality <25-45>` which
 seems to get the file size and quality in the range I'm pleased with.

 Maybe I've missed something, but I have searched through the
 **Performance-Lab** plugin, I'm not finding where you set the quality...
 Will there be a filter for developers to adjust this conversion `-quality
 <int>` value for the 'Full' size and the other core or theme-set $subsize
 .webp output images? Is this a "one `-quality` size fits all $subsizes"
 scenario? Something to think about and I would love to hear your take on

 It would be great if developers could adjust the quality per $subsize. As
 larger dimensions require lower `-quality <int>` and smaller dimensions
 require higher `-quality <int>` to safeguard against visible quality

Ticket URL: <https://core.trac.wordpress.org/ticket/55443#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

More information about the wp-trac mailing list