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

[WordPress Trac]

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

Comment (by azaozz):

 Replying to [comment:135 spacedmonkey]:

 > “It appears you are using images that are not optimised, would you like
 to optimise them?”
 > ...
 > Then add a check setting to “optimise all images by default”.

 I think I understand where you're coming from, but how many people would
 choose to not optimize their images? We're talking about the great
 majority of users that probably haven't heart about WebP or what
 advantages and disadvantages it has. Imho doing this optimization by
 default for newly uploaded images is the right choice here. Of course
 there should be an easy way to disable it from a plugin, either globally
 or per image.

 > For what it is worth, I think the server space issue is a little over
 blown. Lots of popular plug-ins add image sizes that create more files and
 no one talks about that.

 I see few people already replied that adding larger storage requirements
 by a plugin is acceptable as the site owner can make an informed decision
 about it. Yes, generally server disk space is cheaper than bandwidth when
 an image is used somewhat frequently (SSD prices have come down but still
 not that cheap).

 It becomes more expensive for rarely used images, and eventually can
 become "wasted space" for images that are used very rarely or almost
 never. (The actual calculation depends on several factors, but 2-3 sub-
 sizes would be enough for rarely used images. If there isn't a good match
 in the `srcset` the requested image size will likely be larger, and the
 bandwidth will increase a bit. However that image will be loaded only few
 times per year. Chances are the increased bandwidth cost will be less than
 the storage cost.)

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