Developer priorities by diagnostic JPMorgan Chase
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 Feb 2015 at 21:04 looking at http://www.jpmorganchase.com/.
125 pages
1,805 pages in 93 documents
4 documents
None found
4 documents
Five slowest URLs by time to first byte
Top five accessibility issues
Occurrences | What We Checked | |
---|---|---|
999+ | H74 : Ensuring that opening and closing tags are used according to specification | |
999+ | F70 : Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup | |
591 | 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 | |
533 | H93 : Ensuring that id attributes are unique on a Web page | |
533 | F77 : Failure of Success Criterion 4.1.1 due to duplicate values of type ID |
Top five code quality issues
Occurrences | What We Checked | |
---|---|---|
999+ | Invalid attribute name | |
999+ | A "301 Moved Permanently" response was received | |
536 | Invalid attribute value | |
369 | A start or end tag was found which was unrecognised | |
73 | A start tag is missing required attributes |