There's currently no way to quickly identify which classes have the worst coverage or complexity - you have to drill down into each package to see branch & coverage details of classes (and line coverage, while present, cannot be sorted). I suggest amending frame-sourcefiles.html so that it includes a sortable table with line, branch and complexity.
I have added patch 3290509 to implement this.