W3C mobileOK Checker
Is your Web site mobile-friendly?
| Size | Type | URI | incl. redirects |
|---|---|---|---|
| 31.6KB | stylesheet | https://auth.gfx.ms/14.500.21835.00/R3WinLive1033.css | 0 |
| 10.7KB | document | Resource under test | 669B |
| 5.1KB | image | https://auth.gfx.ms/14.500.21835.00/controls.png | 0 |
| Type | URI | Redirects |
|---|---|---|
| document | Resource under test | 3 |
| image | https://auth.gfx.ms/14.500.21835.00/controls.png | 0 |
| image (*) | https://auth.gfx.ms/14.500.21835.00/hig/img/controls.png | 0 |
| stylesheet | https://auth.gfx.ms/14.500.21835.00/R3WinLive1033.css | 0 |
The label of each of the following failure messages contains its severity, its category, and a short description of the failure completed by the underlying best practice that triggered the failure.
@media attribute.
em or percentage based values in CSS.
… width: 16px… height: 16px… width: 8px… height: 8px… width: 7px… height: 4px… width: 61px… height: 61px… width: 46px… height: 46pxscreen and handheld media types so that only relevant CSS styles are downloaded by most devices.
… <script type="text/javascript">var PROOF = {};PROO… <script type="text/javascript">if (top != self){ t… <script type="text/javascript">var g_iSRSFailed=0,… <script type="text/javascript">var ServerData = {u… <script src="https://auth.gfx.ms/14.500.21835.00/Login_Strings_JS1033.js" type="text/javascript" />… <script src="https://auth.gfx.ms/14.500.21835.00/Login_Core.js" type="text/javascript" />… <script type="text/javascript">_DY("__Login_String… <script type="text/javascript">_DY("__Login_String… position: relative… position: absolute… position: relative… position: absolute… position:absolute… position:absolute… position:absolute… float:left… display:none… float:right… display:noneno-cache (or max-age=0) directive prevents browsers from caching the content, and thus requires them to retrieve it through the network every time.
Last-Modified and/or ETag HTTP headers to limit the complete retrieval of the resource to the cases where the resource has changed. See Mark Nottingham's tutorial on caching to learn more about these techniques.
Expires date set in the past prevents browsers from caching the content, and thus requires them to retrieve it through the network
every time.
Last-Modified and/or ETag HTTP headers to limit the complete retrieval of the resource to the cases where the resource has changed. See Mark Nottingham's tutorial on caching to learn more about these techniques.
application/xhtml+xml. More browsers are likely to support that media type, and optimize the rendering for it. application/vnd.wap.xhtml+xml is widely used and supported in mobile networks as well but is unlikely to be supported by non-mobile browsers.
application/xhtml+xml media type.
application/xhtml+xml (e.g. Internet Explorer) and prompt users to download pages served as such. You should not serve XHTML content to browsers
that do not support it. Use Content Negotiation to match the browser's capabilities. See the XHTML Media Types - Second Edition W3C note for more information and in particular the Compatibility Guidelines to follow to have XHTML documents rendered on both XHTML-aware and HTML-only user agents.
Content-Type HTTP header
@media attribute.
The W3C mobileOK Checker follows the W3C mobileOK Basic Tests 1.0 standard and uses specific HTTP headers to retrieve resources as if it were a mobile device. As a result, tests may not be run against the content one may see when the resource is viewed on a regular desktop browser.
This is the W3C mobileOK Checker v1.4.2
This work is part of the MobiWeb 2.0 project supported by the European Union's 7th Research Framework Programme (FP7).
The checker is based on the open source mobileOK checker library developed by the Mobile Web Best Practices working group.
Copyright © 1994-2010 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.