Start date: 20 October 2008
End date: 26 October 2008
Duration: 7 days
Sub-tests failed | 20 Oct 2008 | 21 Oct 2008 | 22 Oct 2008 | 23 Oct 2008 | 24 Oct 2008 | 25 Oct 2008 | 26 Oct 2008 |
---|---|---|---|---|---|---|---|
mobileOK pages | 13% | 10% | 21% | 24% | 14% | 23% | 24% |
1 sub-test failed | 3% | 3% | 6% | 3% | 5% | 3% | 5% |
2 sub-tests failed | 3% | 7% | 4% | 4% | 3% | 4% | 2% |
3 sub-tests failed | 7% | 8% | 4% | 6% | 5% | 6% | 5% |
4 sub-tests failed | 6% | 5% | 7% | 4% | 6% | 2% | 4% |
5 sub-tests failed | 5% | 7% | 3% | 3% | 4% | 5% | 5% |
6 sub-tests failed | 7% | 7% | 7% | 6% | 7% | 7% | 9% |
7 sub-tests failed | 7% | 5% | 7% | 6% | 8% | 10% | 5% |
8 sub-tests failed | 3% | 4% | 6% | 5% | 4% | 6% | 6% |
9 sub-tests failed | 6% | 9% | 6% | 6% | 9% | 6% | 6% |
10 sub-tests failed | 4% | 6% | 6% | 7% | 5% | 6% | 4% |
11 sub-tests failed | 5% | 7% | 3% | 5% | 5% | 7% | 6% |
12 sub-tests failed | 7% | 6% | 5% | 4% | 6% | 3% | 3% |
13 sub-tests failed | 5% | 5% | 5% | 4% | 4% | 4% | 5% |
14 sub-tests failed | 3% | 3% | 3% | 5% | 5% | 2% | 5% |
15 sub-tests failed | 4% | 6% | 5% | 2% | 3% | 2% | 3% |
16 sub-tests failed | 2% | 2% | <1% | 3% | 2% | 1% | 1% |
17 sub-tests failed | 2% | 2% | 1% | <1% | 3% | 1% | 1% |
18 sub-tests failed | 1% | 1% | 1% | <1% | 1% | 0% | 1% |
19 sub-tests failed | 1% | 1% | 0% | <1% | 0% | 2% | 0% |
20 sub-tests failed | <1% | 1% | <1% | 0% | 0% | 0% | 0% |
21 sub-tests failed | 1% | 0% | <1% | 1% | 1% | 1% | 2% |
22 sub-tests failed | 0% | 1% | 0% | 0% | 0% | 0% | 1% |
23 sub-tests failed | <1% | 0% | 0% | 0% | 0% | 0% | 0% |
24 sub-tests failed | 0% | 0% | 0% | 0% | 0% | 1% | 0% |
Tests performed by the mobileOK checker are defined in the mobileOK Basic Tests 1.0 document. The term sub-test used below refers to an aspect of a given test that may FAIL.
The statistics only take into account the URIs for which the checker could run the tests. The checker typically cannot run the tests when:
A given URI may yield different results in time. When a URI is checked more than once during the period, only the most recent result appears in the statistics. This ensures that statistics are not biased by pages that include a mobileOK logo along with a link to the checker for instance.
Viewing statistics per URI isn't the most representative view one could think of. A better view would be "per website". Unfortunately, there's no automatic way to link pages of a website together. The statistics include a view per domain name, but domain names are often used by many different websites, and thus this view is probably even more misleading than the view per URI. The better view is somewhere between the view per URI and the view per domain name, closer to the view per URI...
No! One must keep in mind that the URIs that were checked come from users that chose to use the mobileOK checker. This does introduces a bias in the sample oriented towards mobile-friendliness. Figures in terms of the number of Mobile Web Best Practices not followed would likely be far worse if the stats were computed from a representative set of URIs. However, these stats do provide a useful view of the most common problems content authors encounter when moving to mobile.
Also keep in mind that the tests only cover a restricted set of the Mobile Web Best Practices. Besides, they sometimes cover only a portion of one given Best Practice. In particular, a few Mobile Web Best Practices that cannot be automatically checked, such as CENTRAL_MEANING, SCROLLING are not covered by the tests, and as such cannot appear in these statistics.
Alternatively, some generic tests are performed that do not match any of the Mobile Web Best Practices and are identified by their internal name within the mobileOK Basic Tests 1.0 document, e.g. HTTP_RESPONSE, META_HTTP_EQUIV.