Re: deferring javascript loading in Plone
Laurence Rowe <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <CAOycyLQ9rhnaErr2x0L3wTQdWJYL7FWO+rgUvwH8mhiMu+8u_g@mail.gmail.com> |
On 9 July 2014 01:54, Laurence Rowe <[email protected]> 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 ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Plone-developers mailing list Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org https://lists.sourceforge.net/lists/listinfo/plone-developers