Go to
Result:
This page is mobileOK!
Page Size:
552
document: 480 - stylesheets: 72
Size Type URI
480 document Resource under test
72 stylesheet http://www.w3.org/2009/Talks/01-mobileok-polytechnice/handheld.css
Network:
2 requests
document: 1 - stylesheets: 1
Type URI
document Resource under test
stylesheet http://www.w3.org/2009/Talks/01-mobileok-polytechnice/handheld.css

Check out W3C's training courses for mobile!

Help on the checker is available.

Congratulations

The document located at <http://www.w3.org/2009/Talks/01-mobileok-polytechnice/template4.html> was successfully checked as mobileOK®. This means that the resource in question passed all the tests defined in the W3C mobileOK Basic Tests 1.0 specification.

If you are the author of the Web page, you may wish to identify your content as mobileOK conformant. There is more than one way to claim mobileOK conformance, detailed in the Claiming conformance section of the W3C mobileOK Scheme 1.0 document. Here are two possibilities:

  • Claiming conformance using POWDER

    To enhance discoverability of mobileOK content, you may wish to identify your content as mobileOK conformant using POWDER (the Protocol for Web Description Resources). In a nutshell, simply copy and paste the following POWDER document in a new file on your server and link to it from your mobileOK page using a link element in the head section of the page as described in Linking Resources to Claims using the HTML link Element section of the W3C mobileOK Scheme document. The mobileOK POWDER Generator may be used to generate more complex claims, e.g. to claim that an entire Web site is mobileOK.

    <?xml version="1.0"?>
    <powder xmlns="http://www.w3.org/2007/05/powder#">
     <attribution>
      <issuedby src="http://www.w3.org/data#W3C" />
      <issued>2009-11-25T03:05:38Z</issued>
      <supportedby src="http://validator.w3.org/mobile/" />
     </attribution>
     
     <dr>
      <iriset>
       <includeresources>http://www.w3.org/2009/Talks/01-mobileok-polytechnice/template4.html</includeresources>
      </iriset>
     
      <descriptorset>
       <typeof src="http://www.w3.org/2008/06/mobileOK#Conformant" />
       <displaytext>The page is mobileOK</displaytext>
       <displayicon src="http://www.w3.org/2005/11/MWI-Icons/mobileOK.png" />
      </descriptorset>
     </dr>
    </powder>

    For further reading about POWDER, please refer to the POWDER primer document.

  • Claiming conformance using the mobileOK icon

    You may wish to claim conformance using the mobileOK icon:

    W3C mobileOK Logo

    Please note that the mobileOK icon should not be embedded within the mobileOK representation of the page, as the resulting page would not be mobileOK anymore. The mobileOK icon is rather intended to be used in Web sites that use content adaptation to advertise the existence of a mobileOK representation of a page in e.g. its desktop version.

Detailed report

  1. Style sheets

    The most efficient way to control the layout of a page is to use CSS style sheets. To use them well in a mobile browser, it is important to ensure that the CSS style sheets referenced by a page and the CSS styles directly defined in the page are valid, and e.g. make a good use of the @media rules.

  2. At the HTTP level

    The source of the messages in this category is to be found in the HTTP headers that were sent along with the page. They are most likely due to the Web server configuration for static files, or the way the server-side scripts are written for dynamic content. Making sure that HTTP headers are correctly defined is essential in a mobile context with a usually low bandwidth and high latency.

    • Warning There is an error in the "Last-Modified" header
      Properly handling conditional GET requests based on the Last-Modified header allows browsers to reduce the amount of data to download. When a resource has not been modified since the last retrieval, the server should send back a 304 Not Modified when a request comes with If-Modified-Since.
      See Mark Nottingham's tutorial on caching to learn how to configure a server or adapt a server-side script to handle conditional GET requests.
      Triggered by the resource under test.
      Related best practice:
      [CACHING] Provide caching information in HTTP responses.
    • Warning There is an error in the "ETag" header
      Properly handling conditional GET requests based on the ETag header allows browsers to reduce the amount of data to download. When a resource has not been modified since the last retrieval, the server should send back a 304 Not Modified when a request comes with If-None-Match.
      See Mark Nottingham's tutorial on caching to learn how to configure a server or adapt a server-side script to handle conditional GET requests.
      Triggered by the resource under test.
      Related best practice:
      [CACHING] Provide caching information in HTTP responses.
    • Warning The document is not served as "application/xhtml+xml"
      The recommended media type for serving XHTML is 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.
      See how to properly configure server mime types. If the page under test uses a non-XML version of HTML, you should first consider switching to XHTML. In any case, do not serve a non-XML version of HTML with an application/xhtml+xml media type.
      Beware: some browsers have no support for 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.
      Triggered by the resource under test:
      served as text/html
      Related best practice:
      [CONTENT_FORMAT_SUPPORT] Send content in a format that is known to be supported by the device.

↑ Top