Start date: 13 October 2008
End date: 19 October 2008
Duration: 7 days
Number of BPs failed | URIs (%) | Domains (%) |
---|---|---|
mobileOK pages | 13% | 7% |
1 BP failed | 4% | 5% |
2 BPs failed | 6% | 6% |
3 BPs failed | 8% | 10% |
4 BPs failed | 8% | 9% |
5 BPs failed | 9% | 11% |
6 BPs failed | 9% | 11% |
7 BPs failed | 8% | 10% |
8 BPs failed | 7% | 9% |
9 BPs failed | 7% | 8% |
10 BPs failed | 8% | 9% |
11 BPs failed | 5% | 6% |
12 BPs failed | 3% | 4% |
13 BPs failed | 2% | 2% |
14 BPs failed | 1% | 2% |
15 BPs failed | 1% | 1% |
16 BPs failed | <1% | 1% |
17 BPs failed | <1% | <1% |
18 BPs failed | <1% | <1% |
Best Practice | Best Practice explained | URIs (%) | Domains (%) |
---|---|---|---|
VALID_MARKUP | Create documents that validate to published formal grammars. | 78% | 87% |
MEASURES | Do not use pixel measures and do not use absolute units in markup language attribute values and style sheet property values. | 54% | 61% |
PAGE_SIZE_LIMIT | Ensure that the overall size of page is appropriate to the memory limitations of the device. | 49% | 57% |
IMAGES_SPECIFY_SIZE | Specify the size of images in markup, if they have an intrinsic size. | 46% | 54% |
CHARACTER_ENCODING_USE | Indicate in the response the character encoding being used. | 42% | 47% |
TABLES_LAYOUT | Do not use tables for layout. | 35% | 39% |
CACHING | Provide caching information in HTTP responses. | 32% | 36% |
CONTENT_FORMAT_SUPPORT | Send content in a format that is known to be supported by the device. | 32% | 38% |
POP_UPS | Do not cause pop-ups or other windows to appear and do not change the current window without informing the user. | 27% | 31% |
TABLES_NESTED | Do not use nested tables. | 26% | 29% |
STYLE_SHEETS_USE | Use style sheets to control layout and presentation, unless the device is known not to support them. | 25% | 27% |
NON-TEXT_ALTERNATIVES | Provide a text equivalent for every non-text element. | 25% | 30% |
HTTP_RESPONSE | (Not a real best practice) | 23% | 28% |
CHARACTER_ENCODING_SUPPORT | Ensure that content is encoded using a character encoding that is known to be supported by the device. | 19% | 22% |
PAGE_TITLE | Provide a short but descriptive page title. | 17% | 17% |
IMAGES_RESIZING | Resize images at the server, if they have an intrinsic size. | 13% | 16% |
EXTERNAL_RESOURCES | Keep the number of externally linked resources to a minimum. | 13% | 17% |
IMAGE_MAPS | Do not use image maps unless you know the device supports them effectively. | 10% | 12% |
OBJECTS_OR_SCRIPT | Do not rely on embedded objects or script. | 6% | 7% |
NO_FRAMES | Do not use frames. | 5% | 6% |
MINIMIZE | Use terse, efficient markup. | 4% | 5% |
REDIRECTION | Do not use markup to redirect pages automatically. Instead, configure the server to perform redirects by means of HTTP 3xx codes. | 2% | 3% |
GRAPHICS_FOR_SPACING | Do not use graphics for spacing. | 2% | 2% |
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.