Go to
Result:
This page is mobileOK!
Page Size:
13KB
document: 6.7KB - images: 6.3KB
Size Type URI
6.7KB document Resource under test
3.4KB image http://mobil.tagesschau.de/;m=is;f=gif87a;h=26;k=IKNePO[...]UaK8QHYPgWA6oxUdw.gif
1.3KB image http://mobil.tagesschau.de/;m=is;f=jpg;h=38;k=7condmLOj[...]Ig59oNcAFMhUGB-5A.jpg
549 image http://mobil.tagesschau.de/;m=is;f=jpg;h=27;k=n-AweDmlW[...]db_ScBtwr7Bfa64rQ.jpg
532 image http://mobil.tagesschau.de/;m=is;f=jpg;h=27;k=XMByTQHqk[...]Zeu2uWDrTNl7IVRxA.jpg
450 image http://mobil.tagesschau.de/;m=is;f=jpg;h=27;k=f1wHR3izC[...]7546Aylny81Lj11mg.jpg
50 image http://mobil.tagesschau.de/;m=is;f=gif87a;h=11;k=SoUUaM[...]LtPESheffTyM4lOYQ.gif
50 image http://mobil.tagesschau.de/;m=is;f=gif87a;h=11;k=fVGRQK[...]sMVLq53xuepqZkJWA.gif
Network:
8 requests
document: 1 - images: 7
Type URI
document Resource under test
image http://mobil.tagesschau.de/;m=is;f=gif87a;h=11;k=SoUUaM[...]LtPESheffTyM4lOYQ.gif
image http://mobil.tagesschau.de/;m=is;f=gif87a;h=11;k=fVGRQK[...]sMVLq53xuepqZkJWA.gif
image http://mobil.tagesschau.de/;m=is;f=gif87a;h=26;k=IKNePO[...]UaK8QHYPgWA6oxUdw.gif
image http://mobil.tagesschau.de/;m=is;f=jpg;h=27;k=XMByTQHqk[...]Zeu2uWDrTNl7IVRxA.jpg
image http://mobil.tagesschau.de/;m=is;f=jpg;h=27;k=f1wHR3izC[...]7546Aylny81Lj11mg.jpg
image http://mobil.tagesschau.de/;m=is;f=jpg;h=27;k=n-AweDmlW[...]db_ScBtwr7Bfa64rQ.jpg
image http://mobil.tagesschau.de/;m=is;f=jpg;h=38;k=7condmLOj[...]Ig59oNcAFMhUGB-5A.jpg

Check out W3C's training courses for mobile!

Help on the checker is available.

Congratulations

The document located at <http://mobil.tagesschau.de/> 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-24T18:20:57Z</issued>
      <supportedby src="http://validator.w3.org/mobile/" />
     </attribution>
     
     <dr>
      <iriset>
       <includeresources>http://mobil.tagesschau.de/</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. 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 A matching HTTP response header does not exist for the meta http-equiv element
      The mobile HTTP delivery chains usually involve more intermediaries than typical desktop chains (e.g. mobile operator gateways). The intermediaries will stick to the HTTP level, and won't dig in the content of the page to check for meta http-equiv elements. For the value not to be ignored, a matching HTTP header should be defined in the HTTP response.
      Triggered by the resource under test:
      http-equiv=content-language

↑ Top