Re: JavaScript Compression

[Nathan Andelin <nandelin@xxxxxxxxxxxx>]

> Walden H. Leverich wrote:
> Performance tab is cool, but the more interesting question isn't
> what's downloaded on the initial visit it's what's downloaded on
> clicks 2+.  You've got to figure that a lot of the overhead
> (.js, .css, .jpg, etc.) should occur on the first request. It's 
> subsequent
> requests that you want to optimize.

It's interesting that you bring this up.  I looked at www.microsoft.com 
and the initial hit was about 500kb, but that included a lot of what you 
might call predictive fetching, so that traffic on subsequent clicks was 
quite low.

> Have you played with the break-point options yet? You can grab the
> response after you get it, but before the browser gets it (remember,
> fiddler is a proxy) and change it. All sorts of fun from the useful to
> the hacking (changing session ids to do session hijacking, for 
> example).

I haven't tried it yet.  But thanks for the tip.

It's more clear to me that a tool like Fiddler gives a lot of 
information that people can use to improve their Web sites, and 
applications.  When MC Press changed their site, my gut feel was that it 
was overly bloated.  A tool like Fliddler enables a site designer to 
quantify it, easily.  Oh, on a dial-up connection it will take my home 
page 110 seconds to be loaded.

Nathan.