I recently attended the Trondheim developer Conference and watched a talk titled Managing CSS Projects with ITCSS by Harry Roberts. In his talk he mentioned a method of assessing a websites CSS codebase, specifically the selector specificities. We all know the kinds of specificity issues that often occur on large CSS projects which can then be compunded even further when you add in multiple developers..
TL;DR — Specificity wars.
The idea is for the graph to trend upwards, a graph with a lot of spikes is a clear sign of specificity issues within your codebase, there will always be some anomolies so don’t try to aim for a perfectly flat line. However you should investigate all the major spikes and troughs to see if they can be refactored. The graph is a very crude representation and as such does not contain any units, it’s more of an illustration than anything.
Below the graph you will find a table with all your selectors along with their specificities and whether or not they contain any !importants within their rulesets. While important rulesets do not directly influence a selectors specificity they can, and often do cause havoc when used inappropriately. Which is why I list them within this table.
You can find more about the CSS Specificity Graph here http://csswizardry.com/2014/10/the-specificity-graph/.