Developer priorities by diagnostic Whistles
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 20 Jan 2015 at 07:30 looking at http://www.whistles.co.uk/.
125 pages
None found
None found
None found
None found
Five slowest URLs by time to first byte
Top five accessibility issues
Occurrences | What We Checked | |
---|---|---|
999+ | H30 : Providing link text that describes the purpose of a link for anchor elements | |
650 | 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 | |
446 | F70 : Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup | |
400 | F77 : Failure of Success Criterion 4.1.1 due to duplicate values of type ID | |
400 | H93 : Ensuring that id attributes are unique on a Web page |
Top five code quality issues
Occurrences | What We Checked | |
---|---|---|
400 | Invalid attribute value | |
252 | Invalid attribute name | |
166 | A redundant close tag was found | |
148 | A "301 Moved Permanently" response was received | |
125 | A tag has been assigned the same attribute more than once |