Getting to the Bottom of JavaScript Includes

Posted by: AspNetResources.com articles, news and updates, on 17 Jun 2009 | View original | Bookmarked: 0 time(s)

I get frustrated when an outside vendor insists that I include their JavaScript file all the way up in my pages. Usually they want it right in the <head>. I have a couple of issues with that. I have no control over the responsiveness of your environment Historically, when your browser encountered a JavaScript include, it would suspend rendering, parse and execute it. Thus every single include slows down rendering and affects the overall perception of responsiveness. Yahoo’s Best Practices...

Advertisement
Free Agile Project Management Tool from Telerik
TeamPulse Community Edition helps your team effectively capture requirements, manage project plans, assign and track work, and most importantly, be continually connected with each other.
Category: JavaScript | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 717 | Hits: 45

Similar Posts

  • Are Master Pages too complex? more
  • The .NET/Java architect training program more
  • Orcas and JavaScript IntelliSense more
  • Taking a look at Nikhil's Script# more
  • Browser/Scripting Wish List more
  • IJavaScriptObject in the new version more
  • PRS 312: ASP.NET: Future Directions Developing Rich Applications with "Atlas" (Part 1) more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD