What is happening on the frontend? Horror!!!
The amount of CSS files involved is absurt.
Please check the screenshot attached. Did you realize this amount of css files was involved??
| Comment | File | Size | Author |
|---|---|---|---|
| Schermafbeelding 2012-03-31 om 23.18.05.png | 144.23 KB | Argus |
Comments
Comment #1
Argus commentedMeh I realize my request is not easy fixable due to the nature of current theming layer, involved contrib and the fact that each layout has it's own css file...
Marking as will not fix :)
Comment #2
pkej commentedOn 5.x and 6.x I used some on the fly minifiers together with the boost-module. The main point is that the minified files were sewn together as one big file and cached by boost as a file.
I see that not all have made it to 7.x, but I recently saw http://drupal.org/project/speedy in my feeds. I have yet to test it, but it do require you to minify before hand.
I have neither had the opportunity to test out http://drupal.org/project/boost, or http://drupal.org/project/cdn on 7.x, but at least they are there for your optimization needs.
Furthermore, I usually download the pressflow version of Drupal, and then just move installation profiles into it when needed, if they are distributed with normal Drupal. I haven't taken the time to check out the speed differences in 7.x between those two, but on 6.x it was quite a noticeable difference in serving time.
I also guess you know about sprites, and other methods of speeding up your site, which aren't that different from consolidating the css (and js) into larger files for faster serving.
Comment #3
David_Rothstein commentedAt the risk of stating the obvious, you folks know that Drupal core has CSS aggregation built in, right?
Just go to admin/config/development/performance and choose "Aggregate and compress CSS files" to turn it on, and regardless of how many CSS files ship with the profile, that will get you down to about 3 or 4 CSS files actually rendered on the page (optimized nicely to improve performance for both first-time and repeat visitors).
So, "won't fix" definitely seems like the right status here :)