Re:Breaking Madden: The Super Bowl, in which the machine ble...
by cllns on Friday January 31, 2014 @05:46PM
(#7159692)
Jeez, firebug shows this site as being 64.7MB for me. And 'onload' occurred after 36 seconds.
[ Parent
| on HN ]
Re:Breaking Madden: The Super Bowl, in which the machine ble...
by schwap on Friday January 31, 2014 @06:01PM
(#7159752)
55MB was the (large) GIFs. Maybe HTML5 video would've been better. Disregarding that, 10MB is still pretty large, though.
Re:Breaking Madden: The Super Bowl, in which the machine ble...
by aw3c2 on Friday January 31, 2014 @06:54PM
(#7160037)
That "maybe" is a definite "definitely". I would not be surprised it using video would make it 5.5MB.
Re:Breaking Madden: The Super Bowl, in which the machine ble...
by dandelany on Friday January 31, 2014 @07:24PM
(#7160213)
Not to mention, they could be lazy loaded since they only play when you mouse over them...
Re:Breaking Madden: The Super Bowl, in which the machine ble...
by YokoZar on Saturday February 01, 2014 @07:17PM
(#7164109)
Gfycat (http://gfycat.com/) is a fantastic solution to this -- it loads HTML5 video or an animated gif depending on what the client supports.
Re:Breaking Madden: The Super Bowl, in which the machine ble...
by mschuster91 on Saturday February 01, 2014 @01:45AM
(#7161073)
If only Chrome had a feature of warning you when a website exceeds a certain size - I'm on 500MB of data a month!