If you're tuning in to this webcast you must care about making web sites faster, just like me. No one likes to sit and wait watching their browser load slow pages. I'll talk about the best practices described in my book and will do a demo of YSlow analyzing some of the top web sites in the world. I'll also hint at what's coming up next. Talk to you soon.

will you be adding to yslow (or other new tool) the ability to ignore or otherwise create a special category for analytics references?

i notice, that yslow always dings my site for google analytics references.
it might be good to know that they are done improperly, but it's actually just telling me that there is no expires header on the the analytics js file.



i'm pretty sure it's not the greatest idea to proxy-cache this myself in order to lower the fetch overhead for my clients, but that is possible.
Do you have thoughts on that?

Woody: This is a hard problem because if Google makes ga.js cacheable and they have to push a change, then they have to get everyone to update to ga2.js - that's not feasible. If it was me I would proxy ga.js on my own server and use that in my page. I would also write a cron job that checked the Last-Modified (or checksum or whatever) of ga.js and alert me whenever it changed so that I could update my own code. I've been thinking that it would be nice to have a service like this: alert me whenever URL X is updated.

-Steve