The purpose of putting javascript at the bottom was to make sure the document was loaded before letting javascript interact with the web page. Performance had little if anything to do with it.

HTTP/2 has nothing to do with inlined javascript anyway unless you mean you were placing your loading script at the bottom, meaning <script src=""></script>. In that case, you are actually losing performance by not letting the browser jump on downloading the script right away by putting it in the <head>.

10% popularity Vote Up Vote Down

Feed

: Placing javascripts at the page's bottom and HTTP/2 Does the placement of javascripts at the bottom of html document still gives any loadtime wins, if the site runs on HTTP/2?

More posts by @Eichhorn148

: Is there a benefit to using AMP on already fast mobile sites? I have a blog that scores 100/100 on page speed insights mobile. It seems like I already follow most of what AMP does like inlining

: Rule out third party scraping, but allow Google crawling How to make scraping of own content through wget, httrack etc. impossible, but allow crawling through googlebot? This should be done without

: Website Blog Hacked. Solution Required The blog section of my website is currently hacked. When I do a site: I can find a lot of new pages with Japanese text(randomly creating directories) that

: Remote document root being overwritten with local Today an interesting problem has arisen. A piece of code that relies on the Server Document Root suddenly stopped working on only my browsers.

Login to post a comment!

1 Comments

Back to top | Use Dark Theme