JavaScript on the bottom of the page?

21
votes

I've read that it is better to keep all of your JavaScript files on the bottom of the webpage. The HTML5 Boilerplate template seems to agree: http://html5boilerplate.com/

And seems to be widely used.

My question is: first, does this have any real basis? I've done testing in Firebug and it seems to have some small effect, but is it trivial? Images and other sources don't seem to start loading until CSS files and script files have loaded, but sticking them on the bottom doesn't seem to make much difference in this at all.

4
javascriptjqueryhtmlhtml5boilerplate
Most scripts require the DOM loaded which is not guaranteed if you have them on the top of the page. There are exceptions to this though, for some reason modenizer.js needs to be added to the top of the page as it needs to execute before the DOM is fully loaded. When using jQuery document ready for example it triggers when the DOM is fully loaded but before the images. However, when using window ready it triggers after the images are loaded too. – Nope
Good rationale on JavaScript location in the page at robertnyman.com/2008/04/23/…. – Jaime Hablutzel

4 Answers

28
votes

It is very important for best practice reasons.

When you have scripts loading in your header, they stop other downloads from taking place! This includes your styling, and will also stop your images from downloading until the script has finished.

This is because JavaScript files load synchronously.

Also note that you will get a flash of unstyled content (FOUT) during loading if you do not move your JavaScript files to the bottom of your page. This is because your CSS will not download until the script has finished loading.

Here is an excerpt from Yahoo performance rule 6.

The second problem caused by scripts is blocking parallel downloads. The HTTP/1.1 specification suggests that browsers download no more than two components in parallel per hostname. If you serve your images from multiple hostnames, you can get more than two downloads to occur in parallel. (I've gotten Internet Explorer to download over 100 images in parallel.) While a script is downloading, however, the browser won’t start any other downloads, even on different hostnames.

References

http://developer.yahoo.com/performance/rules.html/

Especially note rule 6.

16
votes

We recently had this debate at the office. I wrote a lengthy post where I lay down my opinion on the subject. The short answer is that it really depends on what you're making. For content oriented web pages, bottom placement seems to work best. However when one is creating web applications where functionality is the main priority, placement at the top has it's advantages.

3
votes

JavaScripts load synchronously. Pair that with generally larger file sizes, and you have content that is being delayed in loading because of the synchronous JavaScript loading. If you put the JavaScripts at the bottom of the page, then everything else is loaded first and the JavaScript loading can't block anything.

1
votes

Basically, when the browser hits a <script> tag, it stops loading the rest of the document until that <script> is loaded and executed.