labjs

I am wanting to load javascript and css files via a resource loader. I was originally using LabJs but I found YepNope more elegant and easier to work with in my scenario. However I am finding it devastatingly slow, which is odd as apparently it is comparable to LabJs in speed on most things. One thing I do have are Etags which I am sure will slow everything down as its still requesting from the server rather than just working off the client cache. Anyway there isnt much outside of the main YepNope site, and they havent released a new version with the fixes on their issues list in a while, so I

I am sure I don't fully understand this problem, but it seems that we are seeing strange behavior on IE9 on my project, somehow related to out-of-order execution of JavaScript that has been injected via calls to document.write , e.g.: document.write('<scr'+'ipt type="text/javascript" src="'+file1+'"></src'+'ipt>'); document.write('<scr'+'ipt type="text/javascript" src="'+file2+'"></src'+'ipt>'); document.write('<scr'+'ipt type="text/javascript" src="'+file3+'"></src'+'ipt>'); My limited Google research suggests that IE9 will execute scripts injected in this manner in a different order from

I made a few tests with lab js in one of the sites I've developed and got a reduction of 200ms in the page load time. The total time spent now after backend processing is around 1.5 seconds. I was wandering if its worth the trouble. Is 200ms a huge gain? A ridiculous one? I know that page load times affect page ranking, but 200ms will make such a big difference? Quoting Milliseconds are Money: How Much Performance Matters in the Cloud : 5) The Proof That Milliseconds Matter … The big guys in the cloud industry have really dug deep and proved that those milliseconds matter: For every 100ms

I use dynamic script loading to reduce the duration of the initial page load. To ensure that the functions and objects defined by a script are accessible, I need to ensure that the script has been fully loaded. I have developed my own Javascript library to this end, and thus did quite a lot of research on the subject, studying how it's done in different libraries. During a discussion related to this issue, Kyle Simpson, the author of LABjs , stated that: LABjs (and many other loaders) set both "onload" and "onreadystatechange" on all script elements, knowing that some browsers will fire one,