Developer priorities by diagnostic BM Savings
Developer priorities allow you to review the important aspects of your assessment from a technical view point. Typically, these priorities relate to changes that cannot be addressed by content editors easily.
Assessment completed on 06 Oct 2015 at 16:01 looking at http://www.birminghammidshires.co.uk/.
125 pages
20 pages in 4 documents
None found
None found
None found
Five slowest URLs by time to first byte
Top five accessibility issues
Occurrences | What We Checked | |
---|---|---|
610 | F17 : Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine one-to-one relationships (e.g., between labels with same id) in HTML | |
396 | F70 : Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup | |
396 | H74 : Ensuring that opening and closing tags are used according to specification | |
48 | G134 : Validating Web pages | |
48 | G192 : Fully conforming to specifications |
Top five code quality issues
Occurrences | What We Checked | |
---|---|---|
131 | A "301 Moved Permanently" response was received | |
127 | Image file size or dimensions do not match | |
70 | A redundant close tag was found | |
17 | Fragment identifier not found | |
4 | Invalid attribute name |