The problem is my main page is the heaviest of the pages...it carries a large Flash graphic (although that would soon go away...). One thing I've decided on is that the user downloading a separate stylesheet for each page is no good... I have always maintained individual CSS files to avoid the one large file...possibly assembling this dynamically at the start would solve this problem. Are there any negatives to a client downloading a 10-12K stylesheet right away? Perhaps the answer is to give them the minimum on the main page, but on any other page serve them the full CSS...
Alex Mike Dougherty wrote: > If your main page is lighter on images than the other pages, you might > consider putting all of your styles into a single document (the sizes > you're talking about are pretty small) - then you pay the download > cost initially, but every other page on the site has the styles > already cached. > > The reason to split the CSS files into a static/sitewide and > dynamic/perpage is not about reducing the overhead to the client as > much as the overhead to the developer. The extra 2-3 packets of data > on the internet pales in consideration with the time spent scrolling > through a monolithic stylesheet during development/maintenance. > > that's just my $0.02 ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
