[ehsankia]

It's not, at least for me. If you checked in devtools, that's gzip over the wire size. Hover over the size and it'll show you the actual resource size, still 285k for me.

[jhgg]

I committed a fix, it's now 24k uncompressed! :)

[blitzar]

Congratulations. Don't forget your 11x improvement when it comes to the end of year reviews.

[ajyotirmay]

Yes it is! That should go on your profile. I wonder how much money that simple change is going to save!

[dmurray]

The gzipped size is probably the correct metric to care about, right? Virtually all browsers will support that.

Sure, Discord could do a bit better, but it's not correct to knock them here for costing their users 285KB.

[MrBoomixer]

This is bad math, not researched heavily but in 2020 discord had 300 million users. 285kb goes a long way with wasted energy and bits flowing through the pipes. I agree generally with what your saying though gzipped sizes are what's being sent some CPU usage somewhere to unzip. less bytes == less waste?

[lmm]

PNG basically includes gzip in the file format, so you're not reducing the amount of CPU used, you're just moving where it happens.

[giantrobot]

Includes but doesn't always use. PNG also includes filters which can dramatically decrease sizes, especially when combined with compression.

That's why tools like OptiPng basically brute force all the combination of options. Depending on the image content different combinations of filters and compression will get the best file size.