From: Laurence R. <l...@lr...> - 2014-07-09 09:07:51
|
On 9 July 2014 01:54, Laurence Rowe <l...@lr...> wrote: > > It is worth periodically reconsidering the optimal way to load resources. > We always used to place css above javascript in the head, but inline > scripts (e.g. analytics setup, script loaders, html5 createElement shims) > block waiting for already referenced CSS to download and in turn block > rendering. > https://www.igvita.com/2014/05/20/script-injected-async-scripts-considered-harmful/ > I slightly misstated the effect here with "and in turn block rendering". CSS blocking execution of inline script elements is mainly a problem when that script loads other resources, e.g. the standard google analytics setup or other script loaders as the requests for the other resources are not made until the CSS is loaded. Rendering always blocks on CSS. Laurence |