> Putting your js at the bottom of the page is essentially the same as
> putting it in jQuery(function() {}), or .ready. The Yslow plugin
> doesn't take into account that you are using jQuery and are
> implementing the ready event. I have run a couple of tests for theActually, YUI has quite an advanced document.ready event model, and YUI developers use it a lot. I'd only assume YSlow not only knows about ready events, but *assumes* you're using them. As I understand it, "JS at the bottom" is recommended because it allows for faster HTML, CSS and image rendering - making pages *look* faster - which research purports is important for the user experience. - Combining all javascripts into as few HTTP requests as possible helps. (a lot!) - Employing a lightweight library (yay jQuery!) and slim javascript modules helps. - Using the document.ready event helps. - HTTP caching helps. - Placing javascripts at the bottom helps too. It's just one of many factors - and probably not the single biggest one - especially if all the others are taken care of. There are a few tricks available to suppress the "flash of web 1.0 content and ui". One that I perfer, is to load a tiny <script> from the <head> of the page, that injects a <style> tag with CSS rules that hide unwanted elements, and then remove the <style>sheet as soon as all the heavy scripts at the bottom have loaded and executed. -- Már Örlygsson --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
