For the sake of 11k that is cached on the first page load it seems a little drastic. I do programming work as well as markup and the indentation/formatting of the code is very important in producing readable code. If it was only me looking at the CSS then fine, but in a team situation producing CSS formatted like this could make human reading a lot harder and thus slow production time.
I can understand if you use TopStyle to do this automatically but I just thought a note of caution/consideration to others reading this that may feel it's a thing all good CSS developers must do.
Personally I'd prefer to leave my CSS formatted as is and shave the k's off images used, etc. Then if I need to hand the stylesheets over to someone they are more usable.
Nick
Anyway as for your CSS, you have a lot of fat that can be trimmed from that as well (no need to repeat the font families if ya put them in the body style) You do not need the “;” after the last attribute in each style (You can remove the returns and have your list go horizontal instead of vertical) Once all done remove all spaces between the commas and the semi-colons and remove the rest of the returns and have one LONG line – all of these together will trim A LOT off the size of the stylesheet – mine by itself in a editing state with comments is over 18k but the version I put on line is under 7k. It don’t look as pretty when it is opened and is harder to read by a human, but it is a smaller file and reads faster by a machine.
***************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *****************************************************
