I read through this a few times to see what it does. It helps find inconsistencies in your webpage design. It does that by reporting the frequency of properties and the frequency of property values in your CSS. You then evaluate that report for potential problems. For instance, shades of blue that are meant to be the same but slightly off. Or font-sizes that are 14px somewhere and 16px somewhere else.
I'd love some horizontal featurette sections on this site that zoomed in on the UI of what this does -- it was very hard to approach with the site as-is.
This is pretty much a non-argument, you could just as well say you don't really need a debugger if you keep your programs minimal. Certain problems have inherent complexity and no abstraction can remove that intrinsic property. You can run a 20-line CSS file for your personal blog where every page looks the same, but you will need more for complex applications with a number of different views, layouts, etc.