MyBB Internal: One or more warnings occured. Please contact your administrator for assistance.
2012 best practice for inlining JS in Head?
Current time: 01-19-2021, 07:40 PM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
2012 best practice for inlining JS in Head?
09-29-2012, 10:23 PM (This post was last modified: 09-29-2012 10:26 PM by jesper_mortensen.)
Post: #1
Question 2012 best practice for inlining JS in Head?
As so many others, we are using Modernizr.js on every page. Modernizr.js must run in the HTML Head (it's a JS library for browser feature detection & HTML5 polyfill & async JS loading).

Our build of this library is about 8 kb before HTTP compression, so the actual download time is negligible.

The classic performance advice from a few years back was to never in-line JS, especially not in the head, as it used to block browser downloads. So scripts which absolutely must execute before initial rendering should be loaded last in Head, and loaded via an external file:
Code:
<script src="modernizr.js"></script>

A quick look at Browserscope.org seems to indicate that most modern browsers don't have the blocking issue anymore, as the "|| CSS + Inline Script" case is green for IE9+. In-lining the JS would save an HTTP request, and for us the time saved by eliminating the first HTTP request for the JS file is greater than the additional download time by in-lining on every page load.

What is the feeling in this community, is it anno 2012 best to load small, fast Head javascripts as external files, or in-line with the HTML? Are there edge cases I didn't think of?
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
2012 best practice for inlining JS in Head? - jesper_mortensen - 09-29-2012 10:23 PM

Forum Jump:


User(s) browsing this thread: 1 Guest(s)