CSS Audits: Take back control of your CSS

CSS Audits: Take back control of your CSS

We dive deep into the nuts and bolts of how to audit your existing CSS. By understanding the reasons for doing it as well as how you can learn, as your auditing, how to keep your CSS lean and mean in the future. You'll leave with tools and ideas for how to do an audit, as well as what to do with the information once you’ve got it. Your audit can even be a springboard to create CSS guidelines and even a style guide.


Susan Robertson

June 03, 2015


  1. 13.


  2. 14.
  3. 15.
  4. 28.
  5. 34.
  6. 43.

    Document your CSS Comments? Spaces or tabs? Empty lines between

    rule set? Space between property and value? Is nesting OK at all, if so how deep? Break up CSS into one style sheet per module or not? Build process if using a preprocessor? Do you commit and track generated files?
  7. 44.

    Where will docs live? Easily accessible & convenient for entire

    team Best online, either privately or publicly
  8. 45.

    How will it maintained? • Schedule when to go back

    to audit & review • Base schedule on the rate of your application changing. • Monthly, Quarterly, Yearly?
  9. 46.

    Time estimate Imagine you could devote time to just this?

    How long would it take? By section or the entire thing?
  10. 51.
  11. 53.

    Thank you A note of thanks to Ethan Marcotte, Rob

    Brackett, Jason Grigsby, Max Fenton and Jonathan Snook for early feedback on this talk. Also, thanks to Flickr users and their creative commons photos. @susanjrobertson susanjeanrobertson.com