Re: deferring javascript loading in Plone
Laurence Rowe <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <CAOycyLTCEe0A1hk6vNFKafL4NDgwKYb3PVfeQt1bt8ULS20HxA@mail.gmail.com> |
On 8 July 2014 23:09, Yuri <[email protected]> wrote: > http://www.feedthebot.com/pagespeed/defer-loading-javascript.html > > this is a really good article, showing that loading all that javascript > in the head section is bad. Is there any idea about this topic in the > upcoming Plone 5? > I strongly disagree ;) This is a terrible example of optimising a particular page rank metric (that is subject to ongoing refinement) over user experience. You users care about (1) when the page is first rendered and they can start reading your content and (2) when it is fully usable and all the controls work. This SEO trick of defering js loading until onLoad will result in a multi-second delay before point 2 is reached. (On many news sites I often see the content jump around the page for perhaps 30 seconds whilst various javascript fully loads.) 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/ 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