Start date: 23 March 2009
End date: 29 March 2009
Duration: 7 days
A more detailed view of the evolution over the period is also available.
The full list of sub-tests failed is also available.
Best Practice | Fail message | URIs (%) | Domains (%) |
---|---|---|---|
VALID_MARKUP | The document does not validate against XHTML Basic 1.1 or MP 1.2. | 48% | 84% |
MEASURES | A length property uses an absolute unit | 29% | 63% |
IMAGES_SPECIFY_SIZE | Either the height or width attribute is missing | 26% | 56% |
PAGE_SIZE_LIMIT | The total size of the page exceeds 20 kilobytes | 26% | 59% |
CACHING | The document is served without caching information ("Expires" or "Cache-Control" header) | 22% | 43% |
VALID_MARKUP | The document does not contain a DOCTYPE declaration | 22% | 29% |
CHARACTER_ENCODING_USE | The HTTP Content-Type header does not specify a character encoding and no UTF-8 encoding or a non-UTF-8 is specified in the XML declaration | 21% | 42% |
PAGE_SIZE_LIMIT | The size of the document's markup exceeds 10 kilobytes | 16% | 38% |
POP_UPS | A pop-up was detected | 15% | 34% |
TABLES_LAYOUT | Table contains less than two tr elements | 14% | 31% |
The full list of warnings is also available.
Best Practice | Warning message | URIs (%) | Domains (%) |
---|---|---|---|
LINK_TARGET_FORMAT | The linked resource character encoding may not be appropriate for mobile devices | 72% | 72% |
META_HTTP_EQUIV | An HTTP response header that matches the meta http-equiv element exists but their values differ | 64% | 53% |
CONTENT_FORMAT_SUPPORT | The document is not served as "application/xhtml+xml" | 63% | 89% |
META_HTTP_EQUIV | A matching HTTP response header does not exist for the meta http-equiv element | 52% | 27% |
CHARACTER_ENCODING_USE | The resource does not specify UTF-8 as character encoding | 51% | 53% |
STYLE_SHEETS_USE | The CSS Style contains invalid at-rules, properties, or values | 45% | 62% |
CACHING | The document's caching information is not provided in the HTTP headers | 43% | 10% |
STYLE_SHEETS_SUPPORT | The CSS Style sheet contains rules referencing the position, display or float properties | 27% | 54% |
STYLE_SHEETS_USE | The style attribute is used | 26% | 53% |
OBJECTS_OR_SCRIPT | The document uses scripting | 22% | 52% |
The full list of best practices not followed is also available.
Best Practice | Best Practice explained | URIs (%) | Domains (%) |
---|---|---|---|
VALID_MARKUP | Create documents that validate to published formal grammars. | 48% | 85% |
MEASURES | Do not use pixel measures and do not use absolute units in markup language attribute values and style sheet property values. | 29% | 63% |
CHARACTER_ENCODING_USE | Indicate in the response the character encoding being used. | 29% | 53% |
PAGE_SIZE_LIMIT | Ensure that the overall size of page is appropriate to the memory limitations of the device. | 26% | 60% |
IMAGES_SPECIFY_SIZE | Specify the size of images in markup, if they have an intrinsic size. | 26% | 56% |
CACHING | Provide caching information in HTTP responses. | 22% | 43% |
CONTENT_FORMAT_SUPPORT | Send content in a format that is known to be supported by the device. | 19% | 41% |
TABLES_LAYOUT | Do not use tables for layout. | 17% | 38% |
HTTP_RESPONSE | (Not a real best practice) | 16% | 35% |
POP_UPS | Do not cause pop-ups or other windows to appear and do not change the current window without informing the user. | 15% | 34% |
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.