As per step 3 (gzipping files) add
<FilesMatch "\.(js|css)$">
SetOutputFilter DEFLATE
</FilesMatch>
to your htaccess file (assuming apache). Now your server will handle compression instead of calling php, which is faster (especially if your sever is not using fastcgi php), and much less resource intensive for the server.
There's ways of having apache automatically cache the gzipped content if server cpu usage is a concern.
My server is lightly loaded (cpu and bandwidth wise), but regardless making some of the above tweaks (set expires on certain files, js/css gziping) has made it much more usable.
If anyone is interested, I was considering writing a ie specific background cacher (similiar to adding mozilla pre-cache tags, but done via js in a hidden div). If there's any interest, I'll go ahead with it. User experience is more important to me than server utilization.