Όλες οι κατηγορίες TV & Home Cinema Computing Τηλεφωνία & Tablets Photo & Video Ήχος Πλοήγηση- GPS Gaming Οικιακές Συσκευές Μικροσυσκευές Προσωπική Φροντίδα Κλιματισμός & Θέρμανση Αξεσουάρ Ψυχαγωγία Mediapedia Είσοδος Εγγραφή Βοήθεια Έξοδος ...

mediamarkt.gr
  • Domain Name
    mediamarkt.gr
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #42511
  • Page Size
    124.2 KB
  • Ip Address
    194.233.193.27
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 0 JPG, 60 PNG

Website Meta Analysis

  • Title
    Αρχική Σελίδα - - Media Markt - Δεν είμαι και χθεσινός
  • Meta Keyword
  • Meta Description
    Όλες οι κατηγορίες TV & Home Cinema Computing Τηλεφωνία & Tablets Photo & Video Ήχος Πλοήγηση- GPS Gaming Οικιακές Συσκευές Μικροσυσκευές Προσωπική Φροντίδα Κλιματισμός & Θέρμανση Αξεσουάρ Ψυχαγωγία Mediapedia Είσοδος Εγγραφή Βοήθεια Έξοδος ...

Technical Analysis

  • Webserver
    IBM_HTTP_Server
  • Ip Address
    194.233.193.27
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from mediamarkt.gr.

HTML Analysis

  • date: Wed, 11 Sep 2013 12:16:57 GMT
  • server: IBM_HTTP_Server
  • pragma: No-cache
  • cache-control: no-cache,no-store,max-age=0
  • expires: Thu, 01 Jan 1970 00:00:00 GMT
  • vary: User-Agent,Accept-Encoding
  • content-encoding: gzip
  • content-type: text/html;charset=UTF-8
  • content-language: el-GR
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for mediamarkt.gr

DNS Analysis


DNS servers
ns.metro.de [164.61.210.4]
ns.metro.info [164.139.12.4]
ns.metro-ag.com [194.156.63.4]


DNS Records

Answer records
mediamarkt.gr SOA
server: ns.metro.de
email: hostmaster@mgi.de
serial: 2006110225
refresh: 10800
retry: 1800
expire: 2592000
minimum ttl: 86400
86400s
mediamarkt.gr NS  ns.metro.info 86400s
mediamarkt.gr NS  ns.metro.de 86400s
mediamarkt.gr NS  ns.metro-ag.com 86400s
mediamarkt.gr A 194.233.193.27 3600s
mediamarkt.gr MX
preference: 500
exchange: infogate12.media-saturn.com
86400s
mediamarkt.gr MX
preference: 600
exchange: infogate13.media-saturn.com
86400s
mediamarkt.gr MX
preference: 100
exchange: infogate.media-saturn.com
86400s
mediamarkt.gr MX
preference: 100
exchange: infogate2.media-saturn.com
86400s
mediamarkt.gr MX
preference: 200
exchange: infogate3.media-saturn.com
86400s
mediamarkt.gr MX
preference: 500
exchange: infogate11.media-saturn.com
86400s

Authority records

Additional records
ns.metro.de A 164.61.210.4 86400s
ns.metro.info A 164.139.12.4 86400s
ns.metro-ag.com A 194.156.63.4 86400s
infogate.media-saturn.com A 194.156.44.2 3600s
infogate2.media-saturn.com A 194.156.44.5 3600s
infogate3.media-saturn.com A 194.156.44.42 3600s
infogate11.media-saturn.com A 194.156.44.27 3600s
infogate12.media-saturn.com A 194.156.44.28 3600s
infogate13.media-saturn.com A 194.156.44.29 3600s

IP 194.233.193.27 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 194.233.193.27

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 144 Errors
  • 130 Warnings
Ratio Text/Html
  • 0.842407282217366
Message Error
  • Error Line 219, Column 248: document type does not allow element "div" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    …Selection(); }</script></span> <div xmlns:v="http://rdf.data-vocabulary.org/#">

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 220, Column 15: there is no attribute "typeof"
    	<span typeof="v:Breadcrumb"><a property="v:title" rel="v:url" href="http://www…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 220, Column 42: there is no attribute "property"
    …pan typeof="v:Breadcrumb"><a property="v:title" rel="v:url" href="http://www.m…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 375, Column 61: there is no attribute "target"
    …p/7_02_2013_int.html" title="" target="_self"><img src="http://pics.redblue.de…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 386, Column 13: there is no attribute "src"
    <iframe src="//www.facebook.com/plugins/likebox.php?href=https%3A%2F%2Fwww.face…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 386, Column 236: there is no attribute "scrolling"
    …ream=false&amp;header=true" scrolling="no" frameborder="0" style="border:none;…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 386, Column 253: there is no attribute "frameborder"
    …ader=true" scrolling="no" frameborder="0" style="border:none; padding:1px; ove…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 386, Column 263: there is no attribute "style"
    … scrolling="no" frameborder="0" style="border:none; padding:1px; overflow:hidd…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 386, Column 352: there is no attribute "allowTransparency"
    … overflow:hidden; width:193px; height:323px" allowTransparency="true"></iframe>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 386, Column 358: element "iframe" undefined
    … overflow:hidden; width:193px; height:323px" allowTransparency="true"></iframe>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 398, Column 32: document type does not allow element "style" here
    <style type="text/css" media=""> @import url("/media/client_media/flashstage/fl…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 399, Column 3: "DOCTYPE" declaration not allowed in instance
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.o…
  • Error Line 400, Column 6: document type does not allow element "html" here
    <html>

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 400, Column 1: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <html>

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 410, Column 43: there is no attribute "border"
    …<a href="/mcs/shop/top10.html" border="0" style="border:0px"><img src="http://…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 461, Column 30: there is no attribute "onClick"
    <div class="prTe_ar" onClick="window.location.href = 'http://www.mediamarkt.gr/…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 472, Column 154: end tag for "img" omitted, but OMITTAG NO was specified
    …ixelboxx-51162264/cms_product_teaser_middle_png" alt="" class="mcpngfix"></div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 472, Column 32: start tag was here
    <div class="prTe_destorber_ar"><img src="http://pics.redblue.de/doi/pbdmz-pixel…
  • Error Line 489, Column 111: required attribute "alt" not specified
    …//pics.redblue.de/doi/pbdmz-pixelboxx-52173512/cms_product_teaser_middle_png"/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 497, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …"" src="http://pics.redblue.de/doi/pixelboxx-mss-8946491/cms_manufacturer_png">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 497, Column 1: start tag was here
    <img alt="" src="http://pics.redblue.de/doi/pixelboxx-mss-8946491/cms_manufactu…
  • Error Line 530, Column 15: there is no attribute "onClick"
    <span onClick="event.cancelBubble=true;"><span onClick="event.cancelBubble=true…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 558, Column 305: there is no attribute "onMouseDown"
    …gId=-18&amp;referrer=CMS" onMouseDown="multiChannel.etracker.clickEvent('Baske…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 567, Column 18: there is no attribute "language"
    <script language="javascript" type="text/javascript">

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 655, Column 155: end tag for "img" omitted, but OMITTAG NO was specified
    …xelboxx-51162264/cms_product_teaser_squared_png" alt="" class="mcpngfix"></div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 655, Column 32: start tag was here
    <div class="prTe_destorber_ar"><img src="http://pics.redblue.de/doi/pbdmz-pixel…
  • Error Line 670, Column 112: required attribute "alt" not specified
    …/pics.redblue.de/doi/pbdmz-pixelboxx-52173503/cms_product_teaser_squared_png"/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 744, Column 155: end tag for "img" omitted, but OMITTAG NO was specified
    …xelboxx-51832128/cms_product_teaser_squared_png" alt="" class="mcpngfix"></div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 744, Column 32: start tag was here
    <div class="prTe_destorber_ar"><img src="http://pics.redblue.de/doi/pbdmz-pixel…
  • Error Line 759, Column 110: required attribute "alt" not specified
    …://pics.redblue.de/doi/pixelboxx-mss-54764523/cms_product_teaser_squared_png"/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 891, Column 155: end tag for "img" omitted, but OMITTAG NO was specified
    …xelboxx-51162264/cms_product_teaser_squared_png" alt="" class="mcpngfix"></div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 891, Column 32: start tag was here
    <div class="prTe_destorber_ar"><img src="http://pics.redblue.de/doi/pbdmz-pixel…
  • Error Line 906, Column 112: required attribute "alt" not specified
    …/pics.redblue.de/doi/pbdmz-pixelboxx-51986621/cms_product_teaser_squared_png"/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 982, Column 155: end tag for "img" omitted, but OMITTAG NO was specified
    …xelboxx-51832128/cms_product_teaser_squared_png" alt="" class="mcpngfix"></div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 982, Column 32: start tag was here
    <div class="prTe_destorber_ar"><img src="http://pics.redblue.de/doi/pbdmz-pixel…
  • Error Line 997, Column 110: required attribute "alt" not specified
    …://pics.redblue.de/doi/pixelboxx-mss-53036963/cms_product_teaser_squared_png"/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1127, Column 155: end tag for "img" omitted, but OMITTAG NO was specified
    …xelboxx-51162264/cms_product_teaser_squared_png" alt="" class="mcpngfix"></div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1127, Column 32: start tag was here
    <div class="prTe_destorber_ar"><img src="http://pics.redblue.de/doi/pbdmz-pixel…
  • Error Line 1142, Column 112: required attribute "alt" not specified
    …/pics.redblue.de/doi/pbdmz-pixelboxx-52000579/cms_product_teaser_squared_png"/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1216, Column 155: end tag for "img" omitted, but OMITTAG NO was specified
    …xelboxx-51832128/cms_product_teaser_squared_png" alt="" class="mcpngfix"></div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1216, Column 32: start tag was here
    <div class="prTe_destorber_ar"><img src="http://pics.redblue.de/doi/pbdmz-pixel…
  • Error Line 1231, Column 110: required attribute "alt" not specified
    …://pics.redblue.de/doi/pixelboxx-mss-42493914/cms_product_teaser_squared_png"/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1316, Column 6: document type does not allow element "html" here
    <html>

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 1316, Column 1: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <html>

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 1318, Column 7: required attribute "type" not specified
    <style>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1357, Column 7: end tag for "head" which is not finished
    </head>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 1363, Column 152: end tag for "span" omitted, but OMITTAG NO was specified
    …eeshipping">Δωρεάν Παράδoση <br/><span>Για προϊόντα αξίας ανω των 85€ </a></li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1363, Column 112: start tag was here
    …ml#freeshipping">Δωρεάν Παράδoση <br/><span>Για προϊόντα αξίας ανω των 85€ </a…
  • Error Line 1376, Column 6: document type does not allow element "html" here
    <html>

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 1376, Column 1: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <html>

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 1387, Column 15: end tag for "head" which is not finished
    </style></head>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 1389, Column 33: document type does not allow element "object" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
    <object width="228" height="378">

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1390, Column 13: there is no attribute "type"
    <embed type="application/x-shockwave-flash" src="http://pics.redblue.de/doi/pbd…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 1390, Column 49: there is no attribute "src"
    …e="application/x-shockwave-flash" src="http://pics.redblue.de/doi/pbdmz-pixelb…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 1390, Column 109: there is no attribute "width"
    …e/doi/pbdmz-pixelboxx-44219938" width="228" height="378" wmode="opaque" allows…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 1390, Column 122: there is no attribute "height"
    …ixelboxx-44219938" width="228" height="378" wmode="opaque" allowscriptaccess="…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 1390, Column 134: there is no attribute "wmode"
    …19938" width="228" height="378" wmode="opaque" allowscriptaccess="always" qual…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 1390, Column 161: there is no attribute "allowscriptaccess"
    …378" wmode="opaque" allowscriptaccess="always" quality="high" pluginspage="htt…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 1390, Column 178: there is no attribute "quality"
    …e" allowscriptaccess="always" quality="high" pluginspage="http://www.macromedi…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 1390, Column 197: there is no attribute "pluginspage"
    …s="always" quality="high" pluginspage="http://www.macromedia.com/go/getflashpl…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 1390, Column 242: element "embed" undefined
    …ality="high" pluginspage="http://www.macromedia.com/go/getflashplayer"></embed>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1462, Column 14: character "&" is the first character of a delimiter but occurred as data
    				if(!done && (!this.readyState || this.readyState == "loaded" || this.readyS…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1462, Column 15: character "&" is the first character of a delimiter but occurred as data
    				if(!done && (!this.readyState || this.readyState == "loaded" || this.readyS…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1471, Column 49: character "&" is the first character of a delimiter but occurred as data
    …Channel.etracker.domainKey.length > 0 && multiChannel.etracker.masterKey.lengt…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1471, Column 50: character "&" is the first character of a delimiter but occurred as data
    …hannel.etracker.domainKey.length > 0 && multiChannel.etracker.masterKey.length…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.

Visitor Analysis

Daily Visitor
  • 4.433 visits