>>110395965
It depends on what the image source is and encoding parameters. Most people don't know this but cwebp, the thing used to make WebP images has a ton of different settings you can adjust.
-alpha_q <int> ......... transparency-compression quality (0..100),
default=100
-preset <string> ....... preset setting, one of:
default, photo, picture,
drawing, icon, text
-segments <int> ........ number of segments to use (1..4), default=4
-sns <int> ............. spatial noise shaping (0:off, 100:max), default=50
-f <int> ............... filter strength (0=off..100), default=60
-sharpness <int> ....... filter sharpness (0:most .. 7:least sharp), default=0
-sharp_yuv ............. use sharper (and slower) RGB->YUV conversion
-partition_limit <int> . limit quality to fit the 512k limit on
the first partition (0=no degradation ... 100=full)
-pass <int> ............ analysis pass number (1..10)
-qrange <min> <max> .... specifies the permissible quality range
(default: 0 100)
-near_lossless <int> ... use near-lossless image preprocessing
(0..100=off), default=100
-hint <string> ......... specify image characteristics hint,
one of: photo, picture or graph
-pre <int> ............. pre-processing filter
These are just some of the settings btw. If you actually want "Compared to the reference JPEG; WebP’s median file size reduction was 31,5%" then you have to mess with these.
That's why JPG is so popular even in 2026. You set the quality slider to 0 and everything looks like shit, set it to 50 and it's okay-ish on phones, set it to 80 and it's okay-ish on computer screens.
No having to deal with all of this.