This suggestion has been closed automatically because it did not receive enough votes over an extended period of time. If you wish to see this, please search for an open suggestion and, if you don't find any, post a new one.
Not all scripts produce these issue, Google Analytics uses asynchronous loading. I believe async can be implemented. Whilst it'll make the page load faster, some components of the page will not work until the JS has finished loading.
JS on top - nothing after the javascript can load without first loading the javascript
JS on bottom - the entire html of the page loads so the user can start looking at content then when the js loads then can the javascript features be used.
That page is designed to take 10 seconds to load.
JS on top - 8 seconds for js then the other 2 for content
JS on bottom - 2 secs for content first then 8 seconds for JS
JS on top - nothing after the javascript can load without first loading the javascript
JS on bottom - the entire html of the page loads so the user can start looking at content then when the js loads then can the javascript features be used.
That page is designed to take 10 seconds to load.
JS on top - 8 seconds for js then the other 2 for content
JS on bottom - 2 secs for content first then 8 seconds for JS
There are many ways to load javascript without blocking the contents of the page. Here are some from a book i bought "High Performance Websites". I'm guessing async load is equal to the first one "XHR Eval" since it's loading javascript via ajax.
• XHR Eval
• XHR Injection
• Script in Iframe
• Script DOM Element
• Script Defer
• document.write Script Tag
There are many ways to load javascript without blocking the contents of the page. Here are some from a book i bought "High Performance Websites". I'm guessing async load is equal to the first one "XHR Eval" since it's loading javascript via ajax.
• XHR Eval
• XHR Injection
• Script in Iframe
• Script DOM Element
• Script Defer
• document.write Script Tag
Yep, and I seem to have a moderate issue. Load up the following page in Firebug: http://www.radonsystems.net/home and see the net tab. You'll see what I mean.
UI preload methods should simply go to the top, libraries can be at the top, but preferred to be on a cdn.
And everything that's asynchronous can be at the top. everything that compliments the page and can be called post-loading the layout, and isn't asyn. should in my opinion be thrown at the bottom.
Load the page in timeline on Safari, and you will see there's currently no issue with the way things are loaded.