[wp-trac] [WordPress Trac] #55443: Create WebP sub-sizes and use for output
WordPress Trac
noreply at wordpress.org
Wed Aug 31 16:43:05 UTC 2022
#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 2nd-opinion needs- | performance
testing changes-requested |
-------------------------------------------------+-------------------------
Comment (by eatingrules):
Replying to [comment:154 adamsilverstein]:
> I think your concerns about storage are exaggerated.
With all due respect, I'm not exaggerating one bit. I'm basing these
concerns on having worked through image optimization (via Shortpixel and
Imagify) on literally hundreds of sites. Sites with anywhere from 3,000
to 40,000+ images in the library. Often there are hundreds of thousands of
thumbnail files, and, in some cases, the numbers reach into the millions.
As I've mentioned before, on a near-daily basis we have clients running
out of disk space on their hosts because of thumbnails. In our situation,
it's often the backups from Shortpixel or Imagify... and that roughly
tracks with the same amount of disk space that we're talking about with
the WebP Conversion (should all the thumbs be duplicated). The savings is
roughly 30-50%, depending on the original images, but these plugins keep
the originals so, overall, the uploads folder's disk space usage can grow
by 30-50% or more.
These aren't "extreme" outliers -- they are simply active, reasonably
successful blogs (most are food/recipe blogs, but we work with a variety
of other publishers and e-commerce sites).
Moreover,
[https://docs.google.com/document/d/1_si5UPkjC9R5yPPL6FPWfx7jahB8GPb2lrxGpdigYDM/edit
your own research indicated that up to 14% of sites] could run into
hosting space issues!
So no, I don't think I'm exaggerating or overreacting here. You're
proposing something that will absolutely cause issues on a significant
percentage of sites over time -- possibly up to 14%, far far above the
threshold that should be considered acceptable.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/55443#comment:155>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list