4.3
Developer priorities by diagnostic Hobbs
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 18 Jan 2015 at 18:43 looking at http://www.hobbs.co.uk/.
125 pages
1 page in 1 document
None found
None found
None found
Five slowest URLs by time to first byte
Top five accessibility issues
| Occurrences | What We Checked | |
|---|---|---|
| 999+ | G141 : Organizing a page using headings | |
| 999+ | G92 : Providing long description for non-text content that serves the same purpose and presents the same information | |
| 999+ | H30 : Providing link text that describes the purpose of a link for anchor elements | |
| 338 | 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 | |
| 247 | H93 : Ensuring that id attributes are unique on a Web page | |
Top five code quality issues
| Occurrences | What We Checked | |
|---|---|---|
| 999+ | Invalid attribute name | |
| 541 | A "301 Moved Permanently" response was received | |
| 305 | Fragment identifier not found | |
| 270 | Image file size or dimensions do not match | |
| 249 | Invalid attribute value | |