News for hackers. Stuff that matters.
Re:The Website Obesity Crisis (2015) by hallatore on Monday May 09, 2016 @08:41AM (#11659322)
If 1MB is obesity then what is this page? https://www.javapoly.com
Re:The Website Obesity Crisis (2015) by muglug on Monday May 09, 2016 @08:49AM (#11659373)
That's not so much a web page as a web app masquerading as a page.

Something that compiles and runs java applications in pure JS is bound to use up a shit-ton of bandwidth.

Re:The Website Obesity Crisis (2015) by hawkice on Monday May 09, 2016 @08:52AM (#11659398)
Upwards of 30MB and it took two minutes to execute the call to alert. Only for those who actively hate the visitors to their page.
Re:The Website Obesity Crisis (2015) by tobltobs on Monday May 09, 2016 @09:03AM (#11659478)
> then what is this page?

A really bad example to use for bloated pages.

Re:The Website Obesity Crisis (2015) by bbuffone on Monday May 09, 2016 @08:55AM (#11659417)
The website loads in 9 seconds (Chrome 50), the processing of the (peg$parseKeyword) functions takes 4.5 seconds of time during loading which causes the gap in the waterfall.

One look at the function would cause severe ingestion in most people.

Re:The Website Obesity Crisis (2015) by chrismorgan on Monday May 09, 2016 @09:27AM (#11659626)
(You wanted the word “indigestion”. Ingestion means something quite different. Though I suppose if someone was prone to eating when depressed, it could work.)
Re:The Website Obesity Crisis (2015) by ape4 on Monday May 09, 2016 @09:12AM (#11659531)
Its a proof of concept. Common .jars can be cached.