A technical site audit is often the first step when a development team takes on an existing build. It can also be a stand-alone project to get expert advice for re-orienting technical efforts.
A good audit looks everywhere and sees everything. A bad audit is mostly just a report using a template from a previous audit or relies primarily on only automated methods.
Auditing is not just an explicit exercise, but a frame of mind you can use throughout projects to keep standards high and focus on the longterm quality of work.
In this session I'll walk you through how I do an audit, covering themes of performance, security, maintainability, and usability, and looking at everything from server, code, configuration, workflow, and IA.
Even if you're not planning to do a site audit, developers and site builders will find this talk to be chock full of tips that improve your game.