Frequent Flyers: Boosting Performance on DHTML Pages

Posted: Oct/22/2009 By: pankaj Points:15 Category: HTML/XML - HTML Views:163 Vote Up (0) Vote Down (0)

In previous articles I've shown you how to create exciting, interactive, immersible pages with Dynamic HTML. But how do you make those pages really fast?

As a program manager on the Microsoft Internet Explorer team, one of the ways I spend my days is doing code reviews of DHTML pages created by Microsoft developers. This month, I'll share some of the hard lessons we have learned about speeding the performance of DHTML pages.

To help you do just that, let's look at ways to reduce your download and your working set, and to optimize your script.

View Complete Post

Comments:

Be the first to comment this post.

Post Comment

Please login to post your comment

More Related Resources

Building High Performance HTML Pages

The Internet, intranets, and extranets carry millions of packets of data. Today, many of those packets contain HTML.

The features delivered with Microsoft Internet Explorer 4.0 and later have helped make the Web a compelling space in which to work and to play. The quantity and complexity of pages as well as the number of consumers of those pages has significantly increased the traffic on the Web. For all the merit that the Web brings to application developers, it introduces a host of problems. Among these problems are:

Delivering content across the wire.
Once delivered, getting that content to render quickly.
This article presents some tips on how you can get the most performance out of your pages.

Reuse HTML Components and External Scripts
DEFER Your Scripts
Author Hyperlinks Consistently
Use Fixed-Size Tables
Optimize Your Scripts
Scope Your Object References Wisely
Close Your Tags
Leverage the HTTP Expires Header
Use Cache-Control Extensions
Related Topics

Asynchrony Load Webpage Page: Loved Your Performance

As I first wrote about back in December 1997 (Frequent Flyers: Boosting Performance on DHTML Pages), one way to improve performance is to break your sites up into more-reusable components, such Cascading Style Sheets and include files for commonly used script. Last month, as I looked at all the DHTML sites people sent in, it was clear that including common script via the method is becoming more common.

One problem people seem to be running into is the dreaded asynchrony issue. "Asynchrony"? What's that? For the purposes of HTML, asynchrony means that events do not always occur one after the other in a predictable way.