A fluffy 500-word Medium-style article with 1-2MB of JavaScript serving no apparent purpose and 5-10MB of animated GIFs would be another story.
That sets any stupid article at a 500kB bar.
I have no doubt that a HN engineer can publish a single .txt file and force gzip-9 compression, however that's not an acceptable blog by any standard.
For a fully static fully cachable site, it's the bandwidth.
Your home connection cannot serve Gigabytes of data in a timely fashion.
nginx or varnish can do that (with more or less correct rules).
In practise, I usually disable compression everywhere and let the CDN handles it.
The CDN is configured to compress on the fly and I am very confident that CloudFlare/Akamai are doing that much better than a broken snippet of nginx settings from stack overflow.
I'm not sure if it's still like that, since I'm not using S3 for that right now.