> Your total UNCOMPRESSED web resources must not exceed 512KB.

I would be interested to know how they define web resources. HN would only fit this description if we don't count every possible REST resource you could request, but instead just the images (3 svgs), CSS (news.css), and JS (hn.js).

The second you count any possible response to `https://news.ycombinator.com/item?...` in the total, we've blown the cap on 512kb... and that's where the actual useful content lays.

Feels like regular ol' REST-and-forms webapps aren't quite the target of this list though, so who knows.

▲

genezeta 2 days ago | parent [-]

> I would be interested to know how they define web resources.

They explain things in the FAQ. You're supposed to do a "Cloudflare URL Scan" and read the "Total bytes". For HN this is 47kB [1], which, yes, is just the 6 requests needed for / and nothing more.

[1] https://radar.cloudflare.com/scan/4c2b759c-b690-44f0-b108-b9...

▲

NooneAtAll3 2 days ago | parent [-]

> Cloudflare URL Scan

> Cloudflare

any chance for a non-monopoly version?

	▲	moebrowne 2 days ago \| parent \| next [-]
		There is some movement on using a headless browser instead of Cloudflare. See https://github.com/kevquirk/512kb.club/issues/1187 and https://github.com/kevquirk/512kb.club/pull/1830
	▲	genezeta 2 days ago \| parent \| prev [-]
		While you might not get the exact same numbers (^1), you can get a very similar result in your browser's devtools, in the network tab, by doing a clean reload of the page. It will give you a total (both compressed/transferred bytes, and uncompressed). --- (^1) If the page, as HN does, has some headers or additional content for logged in visitors, the numbers will generally be a bit different. But the difference will usually be small.