xtronics Posted March 18, 2015 Posted March 18, 2015 A lot of folks should have gotten the bit from the Google webmaster tools team by now. This thread should be about Render-Blocking (there should be another on viewport and mobile issues). They want us to move the Java script bits out of the header and just before the </body> tag. I'm not sure this is that good of an idea(shouldn't it be the job of the browser?), but I'm not going to fight Google - they own us. So before I start moving things around - anyone else out there dealing with this? ------------------------------------------------------------------------ The first panacea for a mismanaged nation is inflation of the currency; the second is war. Both bring atemporary prosperity; both bring permanent ruin.Ernest Hemingway------------------------------------------------------------------------
MrPhil Posted March 18, 2015 Posted March 18, 2015 Consider instead adding the async term to <script> tags. I can understand the 800 pound Googlrilla not wanting to have to wait for JS (and CSS) files to load, or to be interpreted before the DOM can be built, but forcing <script> tags out of the <head> is silly. Nevertheless, if you move your JS or use async, be careful about being dependent on the order that JS is executed in.
New 
Recommended Posts
Archived
This topic is now archived and is closed to further replies.