If you'd like to collect similar stats for your own code base, check out parker[1] and stylestats[2]. At my company, we aggregate certain numbers from both tools and send them to Graphite to monitor over time, as inspired by this talk from GitHub[3][4].
Cool, thanks. Those are some pretty big numbers. What kind of a site is it?
It is really interesting to see the variance, btw. Twitter, KickStarter and Bootstrap running at thousands of rules, Google and Wikipedia at under 200. And a whole bunch in the 500-1000 range, such as Facebook, Amazon and Mozilla. I'm actually surprised at the relatively low rule-count for Facebook and Amazon as both those sites always gave me the impression (perhaps mistakenly) of having more CSS rules than I could read in a lifetime. Conversely, Github and Stack Overflow have more rules than I would have expected.
I guess that just goes to show that CSS complexity and visual clutter do not necessarily correlate.
Pretty sure the Facebook one is just checking their logged-out page, which is much more straightforward than the logged-in view. Logged-in I count ~144kb of CSS, which still isn't bad, but isn't as mind-bogglingly low.
Amazon is definitely impressive though!
(As are Stripe, Apple, and Airbnb, in basically that order.)
That site specifically was a porn site. Our 3.0 upgrade of the site involved a lot "get this working, NEXT!" so the CSS is kind of a mess. I've got a nice stat page to show me just how much of a mess now though!
It looks like we have a bug and that we're not grabbing all of amazons css - just the first referenced stylesheet. Opening an issue on github. Thanks for the heads up.
This was happening to me too. I could see the output from node that said it figured out there were multiple stylesheets, but it didn't seem to care, and just went about its business showing the first one.
Kudo's for the devs; it really was as simple as downloading the zip from github and issuing a install && start :) Pulled in phantomjs, etc. and just worked out of the gate :)
It still has some issues with style detection (as noticed in other comments), but once that gets fixed, I'll be sure to check back :) Nice project!
It almost seems like an on boarding tool for 3rd party CSS but you can't construct or derive style rules from any of the presented formats, just raw colors/sizes.
Because CSS rules are applied by specificity (http://specificity.keegan.st/) first and source order second, any property overwrites later in the document require equal or greater specificity than rules in the middle. A chart with a mountain in the middle today will probably develop more mountains on the right over time - it's a leading indicator of poor maintainability. Pairing this tool with one that tells you the line number of offenders would help in identifying areas in need of refactor.
Total vs Unique declarations reveals opportunities for reusable OOCSS-type classes (which itself can be difficult to do in a stylesheet full of specificity mountains).
The colors aren't terribly useful without a histogram and some of the other stats do seem a bit superfluous, but they may just need someone more experienced than I to draw the right conclusions.
Amazon might not be the best example - loading http://cssstats.com/stats?url=http%3A%2F%2Famazon.com#specif... multiple times has generated multiple, very different graphs. I wonder if the CSSStats bot has been thrown into more than one A/B experiments.
