4 ms·
Wow. The page source is gold. No kidding. Firefox's inspector tool just crashed (went white and unresponsive) while I was making a list of the worst offenses:
by fbelzile 7y ago
Wow. The page source is gold.
No kidding. Firefox's inspector tool just crashed (went white and unresponsive) while I was making a list of the worst offenses:
- h2, h4, h5 used interchangeably
- embedded wav file loading an image
- loading all JavaScript just below body tag
- tantalor 7y agoWhat's so bad about loading scripts after body?
- adventured 7y agoThey're referring to loading the scripts right after the opening body tag (rather than at the end of the body), which historically would block content loading until the scripts all load.
- josteink 7y agoBack then scripts literally were 1kb at most and not 15mb like today, so it really wasn’t much of a problem.
- eyelidlessness 7y agoBack then it took ten minutes to load 1kb
- josteink 7y agoIt wasn’t that bad. I remember downloading fairly high res JPEGs (so 30-50kb) on a 36k modem back then, and that might have taken a minute.
- eyelidlessness 7y agoHyperbole is lost on 100% of people on the internet.
- trehalose 7y agoWhen I saw "embedded wav file loading an image", I was mystified and curious what that even meant, so I looked, and I didn't see. The only wav file I noticed in the source was on the Biler page, and I didn't see anything that suggested it was loading an image, but I didn't look very closely and I guess I'm not sure what to look for. I didn't read the JavaScript at all really, but I searched for "bgsound" with no results but the bgsound element itself, and it has no id and I don't know how else it could be referenced.