Kruidvat - Bestel online mooie producten en bekijk de folder! ...

kruidvat.nl
  • Domain Name
    kruidvat.nl
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #38890
  • Page Size
    116.1 KB
  • Ip Address
    213.247.48.238
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 2
  • Images
    71 GIF, 39 JPG, 4 PNG

Website Meta Analysis

  • Title
    Kruidvat - De voordelige drogist, ook online!
  • Meta Keyword
  • Meta Description
    Kruidvat - Bestel online mooie producten en bekijk de folder!

Technical Analysis

  • Webserver
    Microsoft-IIS/6.0
  • Ip Address
    213.247.48.238
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from kruidvat.nl.

HTML Analysis

  • date: Wed, 13 Feb 2013 02:53:21 GMT
  • server: Microsoft-IIS/6.0
  • x-powered-by: ASP.NET
  • x-aspnet-version: 4.0.30319
  • cache-control: private
  • content-type: text/html; charset=utf-8
  • content-length: 131389
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for kruidvat.nl

DNS Analysis


DNS servers
ns2.ism.nl [213.247.48.8]
ns.ism.nl [178.248.168.162]


DNS Records

Answer records
kruidvat.nl A 213.247.48.238 3600s
kruidvat.nl SOA
server: ns.ism.nl
email: hostmaster@ism.nl
serial: 2013011600
refresh: 28800
retry: 1800
expire: 604800
minimum ttl: 3600
3600s
kruidvat.nl NS  ns.ism.nl 3600s
kruidvat.nl NS  ns2.ism.nl 3600s
kruidvat.nl MX
preference: 200
exchange: smtp2.uk.aswatson.com
3600s
kruidvat.nl MX
preference: 100
exchange: smtp1.uk.aswatson.com
3600s

Authority records

Additional records
ns.ism.nl A 178.248.168.162 10800s
ns2.ism.nl A 213.247.48.8 10800s

IP 213.247.48.238 Analysis

  • Country Code
    NL
  • Country Code3
    NLD
  • Country Name
    Netherlands
  • City
    EU
  • Continent Code
    52.5° North
  • Latitude
    5.75
  • Longitude
  • No whois ip data for 213.247.48.238

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 116 Errors
  • 29 Warnings
Ratio Text/Html
  • 0.8253498136290587
Message Error
  • Warning Line 16, Column 105: NET-enabling start-tag requires SHORTTAG YES
    …="text/css" href="http://www.kruidvat.nl/domains/kruidvat/styles/general.css"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 17, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …/css" href="http://www.kruidvat.nl/domains/kruidvat/styles/myEnvironment.css"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 17, Column 111: document type does not allow element "LINK" here
    …/css" href="http://www.kruidvat.nl/domains/kruidvat/styles/myEnvironment.css"/>

    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).

  • Warning Line 18, Column 119: NET-enabling start-tag requires SHORTTAG YES
    …ef="http://www.kruidvat.nl/domains/kruidvat/styles/jquery.fancybox-1.3.4.css"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 18, Column 119: document type does not allow element "LINK" here
    …ef="http://www.kruidvat.nl/domains/kruidvat/styles/jquery.fancybox-1.3.4.css"/>

    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).

  • Warning Line 28, Column 125: NET-enabling start-tag requires SHORTTAG YES
    …t.nl/domains/kruidvat/styles/sIFR-screen.css" type="text/css" media="screen" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 28, Column 125: document type does not allow element "LINK" here
    …t.nl/domains/kruidvat/styles/sIFR-screen.css" type="text/css" media="screen" />

    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).

  • Warning Line 29, Column 123: NET-enabling start-tag requires SHORTTAG YES
    …vat.nl/domains/kruidvat/styles/sIFR-print.css" type="text/css" media="print" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 29, Column 123: document type does not allow element "LINK" here
    …vat.nl/domains/kruidvat/styles/sIFR-print.css" type="text/css" media="print" />

    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).

  • Warning Line 39, Column 62: NET-enabling start-tag requires SHORTTAG YES
    <meta name="author" content="ISM eCompany: http://www.ism.nl"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 39, Column 62: document type does not allow element "META" here
    <meta name="author" content="ISM eCompany: http://www.ism.nl"/>

    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).

  • Warning Line 40, Column 54: NET-enabling start-tag requires SHORTTAG YES
    <meta name="generator" content="SANA Framework 5.2.2"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 40, Column 54: document type does not allow element "META" here
    <meta name="generator" content="SANA Framework 5.2.2"/>

    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).

  • Warning Line 42, Column 93: NET-enabling start-tag requires SHORTTAG YES
    …gle-site-verification" content="oArnmzTWlys-JUBEZ6RnxRKqdR1DTNIarIUglkF6AgY" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 42, Column 93: document type does not allow element "META" here
    …gle-site-verification" content="oArnmzTWlys-JUBEZ6RnxRKqdR1DTNIarIUglkF6AgY" />

    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).

  • Warning Line 57, Column 93: NET-enabling start-tag requires SHORTTAG YES
    …gle-site-verification" content="Ghcjq91W2us6v3we05HrVk_bbOYqOdp-bgRcZhoQ6dE" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 57, Column 93: document type does not allow element "META" here
    …gle-site-verification" content="Ghcjq91W2us6v3we05HrVk_bbOYqOdp-bgRcZhoQ6dE" />

    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).

  • Warning Line 141, Column 114: NET-enabling start-tag requires SHORTTAG YES
    …://www.kruidvat.nl/domains/kruidvat/content/favicon.ico" type="image/x-icon" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 141, Column 114: document type does not allow element "LINK" here
    …://www.kruidvat.nl/domains/kruidvat/content/favicon.ico" type="image/x-icon" />

    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).

  • Warning Line 142, Column 109: NET-enabling start-tag requires SHORTTAG YES
    …://www.kruidvat.nl/domains/kruidvat/content/favicon.ico" type="image/x-icon" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 142, Column 109: document type does not allow element "LINK" here
    …://www.kruidvat.nl/domains/kruidvat/content/favicon.ico" type="image/x-icon" />

    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 148, Column 129: document type does not allow element "LINK" here
    …"http://www.kruidvat.nl/domains/kruidvat/content/magazine/styles/magazine.css">

    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 150, Column 23: document type does not allow element "STYLE" here
    <style type="text/css">

    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 161, Column 7: end tag for element "HEAD" which is not open
    </head>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

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

    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).

  • Warning Line 209, Column 156: cannot generate system identifier for general entity "guid"
    …com/pagead/conversion/1069308753/?label=3R4tCO_ioAIQ0bbx_QM&guid=ON&script=0"/>

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 209, Column 156: general entity "guid" not defined and no default entity
    …com/pagead/conversion/1069308753/?label=3R4tCO_ioAIQ0bbx_QM&guid=ON&script=0"/>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Error Line 209, Column 160: reference to entity "guid" for which no system identifier could be generated
    …com/pagead/conversion/1069308753/?label=3R4tCO_ioAIQ0bbx_QM&guid=ON&script=0"/>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 209, Column 155: entity was defined here
    …com/pagead/conversion/1069308753/?label=3R4tCO_ioAIQ0bbx_QM&guid=ON&script=0"/>
  • Warning Line 209, Column 164: cannot generate system identifier for general entity "script"
    …com/pagead/conversion/1069308753/?label=3R4tCO_ioAIQ0bbx_QM&guid=ON&script=0"/>

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 209, Column 164: general entity "script" not defined and no default entity
    …com/pagead/conversion/1069308753/?label=3R4tCO_ioAIQ0bbx_QM&guid=ON&script=0"/>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Error Line 209, Column 170: reference to entity "script" for which no system identifier could be generated
    …com/pagead/conversion/1069308753/?label=3R4tCO_ioAIQ0bbx_QM&guid=ON&script=0"/>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 209, Column 163: entity was defined here
    …com/pagead/conversion/1069308753/?label=3R4tCO_ioAIQ0bbx_QM&guid=ON&script=0"/>
  • Warning Line 209, Column 173: NET-enabling start-tag requires SHORTTAG YES
    …com/pagead/conversion/1069308753/?label=3R4tCO_ioAIQ0bbx_QM&guid=ON&script=0"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 220, Column 170: required attribute "ACTION" not specified
    …rch(null);fillPostalCodeTextBox(document.getElementById('searchfield').value)">

    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 269, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 279, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 293, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 305, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 317, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 325, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 346, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 368, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 403, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 436, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 468, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 508, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 554, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 573, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 607, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 624, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 660, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 709, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 738, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 765, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 785, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 807, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 823, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 839, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 869, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 882, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 905, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 919, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 943, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 962, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 988, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1012, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1041, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1060, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1073, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1101, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1125, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1135, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1172, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1206, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1239, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1264, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1295, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1314, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1332, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1351, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1364, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1375, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1385, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1412, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1455, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1467, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1495, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1539, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1574, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1592, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1621, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1631, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1645, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1655, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1667, Column 127: required attribute "ALT" not specified
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/submenu_arrow.gif">

    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 1680, Column 277: there is no attribute "HEIGHT"
    …v><TABLE id=Tabel_01 border=0 cellSpacing=0 cellPadding=0 width=180 height=313>

    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 1683, Column 139: character "?" not allowed in attribute specification list
    …-carnval/magazine.html" target=_blank ?><IMG border=0 src="http://www.kruidvat…
  • Error Line 1683, Column 253: required attribute "ALT" not specified
    …s/kruidvat/content//banners/2013-07/home/2013-07-home-A1_01.jpg"></A></TD></TR>

    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 1685, Column 219: required attribute "ALT" not specified
    …s/2013-06/home/2013-06-home-A1_02.jpg"></A></TD></TR></TBODY></TABLE><!-- End …

    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 1685, Column 493: ID "TABEL_01" already defined
    …GE/witvlak.jpg"></div></div><TABLE id=Tabel_01 border=0 cellSpacing=0 cellPadd…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1680, Column 214: ID "TABEL_01" first defined here
    …GE/witvlak.jpg"></div></div><TABLE id=Tabel_01 border=0 cellSpacing=0 cellPadd…
  • Error Line 1712, Column 54: ID "IMGLINK13010000031447" already defined
    …lockImage"><IMG alt="" border="0" id="imgLink13010000031447" src="http://www.k…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1680, Column 71: ID "IMGLINK13010000031447" first defined here
    …lockImage"><IMG alt="" border="0" id="imgLink13010000031447" src="http://www.k…
  • Warning Line 1713, Column 211: NET-enabling start-tag requires SHORTTAG YES
    …kruidvat/content/banners/2013-07/home/A2_1_Valentijn_001.jpg" border="0" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1713, Column 211: required attribute "ALT" not specified
    …kruidvat/content/banners/2013-07/home/A2_1_Valentijn_001.jpg" border="0" /></a>

    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 1725, Column 247: ID "IMGLINK13010000031448" already defined
    …lockImage"><IMG alt="" border="0" id="imgLink13010000031448" src="http://www.k…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1685, Column 350: ID "IMGLINK13010000031448" first defined here
    …lockImage"><IMG alt="" border="0" id="imgLink13010000031448" src="http://www.k…
  • Error Line 1725, Column 531: required attribute "ALT" not specified
    …at.nl/domains/kruidvat/content//banners/2013-07/home/C0_treinkaartje.jpg"></A> 

    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 1726, Column 11: ID "TABEL_01" already defined
    <TABLE id=Tabel_01 border=0 cellSpacing=0 cellPadding=0 width=560 height=670>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1680, Column 214: ID "TABEL_01" first defined here
    …GE/witvlak.jpg"></div></div><TABLE id=Tabel_01 border=0 cellSpacing=0 cellPadd…
  • Error Line 1729, Column 187: required attribute "ALT" not specified
    …domains/kruidvat/content//banners/2013-07/home/2013-07-home-C_06.jpg"></A></TD>

    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 1730, Column 187: required attribute "ALT" not specified
    …domains/kruidvat/content//banners/2013-07/home/2013-07-home-C_07.jpg"></A></TD>

    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 1731, Column 254: required attribute "ALT" not specified
    …ns/kruidvat/content//banners/2013-07/home/2013-07-home-C_08.jpg"></A></TD></TR>

    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 1733, Column 244: required attribute "ALT" not specified
    …domains/kruidvat/content//banners/2013-07/home/2013-07-home-C_09.jpg"></A></TD>

    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 1734, Column 243: required attribute "ALT" not specified
    …domains/kruidvat/content//banners/2013-07/home/2013-07-home-C_10.jpg"></A></TD>

    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 1735, Column 258: required attribute "ALT" not specified
    …ns/kruidvat/content//banners/2013-07/home/2013-07-home-C_11.jpg"></A></TD></TR>

    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 1737, Column 159: required attribute "ALT" not specified
    …domains/kruidvat/content//banners/2013-07/home/2013-07-home-C_12.jpg"></A></TD>

    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 1738, Column 159: required attribute "ALT" not specified
    …domains/kruidvat/content//banners/2013-07/home/2013-07-home-C_13.jpg"></A></TD>

    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 1739, Column 169: required attribute "ALT" not specified
    …ns/kruidvat/content//banners/2013-07/home/2013-07-home-C_14.jpg"></A></TD></TR>

    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 1741, Column 259: required attribute "ALT" not specified
    …domains/kruidvat/content//banners/2013-07/home/2013-07-home-C_15.jpg"></A></TD>

    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 1742, Column 155: required attribute "ALT" not specified
    …domains/kruidvat/content//banners/2013-07/home/2013-07-home-C_16.jpg"></A></TD>

    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 1743, Column 221: required attribute "ALT" not specified
    …ns/kruidvat/content//banners/2013-07/home/2013-07-home-C_17.jpg"></A></TD></TR>

    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>.

  • Warning Line 1751, Column 401: NET-enabling start-tag requires SHORTTAG YES
    …ains/kruidvat/content/banners/2013-07/home/B1-Testpannel.jpg" border="0" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1751, Column 401: required attribute "ALT" not specified
    …ains/kruidvat/content/banners/2013-07/home/B1-Testpannel.jpg" border="0" /></a>

    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>.

  • Warning Line 1769, Column 204: cannot generate system identifier for general entity "contentcode"
    …ntent=12980000001174_2_12980000200036&contentcode=yourextraadvantagebetweensys…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 1769, Column 204: general entity "contentcode" not defined and no default entity
    …ntent=12980000001174_2_12980000200036&contentcode=yourextraadvantagebetweensys…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Error Line 1769, Column 215: reference to entity "contentcode" for which no system identifier could be generated
    …000001174_2_12980000200036&contentcode=yourextraadvantagebetweensystempage&nav…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 1769, Column 203: entity was defined here
    …ontent=12980000001174_2_12980000200036&contentcode=yourextraadvantagebetweensy…
  • Warning Line 1769, Column 252: cannot generate system identifier for general entity "navigationid"
    …e=yourextraadvantagebetweensystempage&navigationid=12980000000319&parentid=129…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 1769, Column 252: general entity "navigationid" not defined and no default entity
    …e=yourextraadvantagebetweensystempage&navigationid=12980000000319&parentid=129…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Error Line 1769, Column 264: reference to entity "navigationid" for which no system identifier could be generated
    …dvantagebetweensystempage&navigationid=12980000000319&parentid=12980000000278&…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 1769, Column 251: entity was defined here
    …de=yourextraadvantagebetweensystempage&navigationid=12980000000319&parentid=12…
  • Warning Line 1769, Column 280: cannot generate system identifier for general entity "parentid"
    …ystempage&navigationid=12980000000319&parentid=12980000000278&redirecturl=refe…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 1769, Column 280: general entity "parentid" not defined and no default entity
    …ystempage&navigationid=12980000000319&parentid=12980000000278&redirecturl=refe…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Error Line 1769, Column 288: reference to entity "parentid" for which no system identifier could be generated
    …page&navigationid=12980000000319&parentid=12980000000278&redirecturl=referer" >

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 1769, Column 279: entity was defined here
    …systempage&navigationid=12980000000319&parentid=12980000000278&redirecturl=ref…
  • Warning Line 1769, Column 304: cannot generate system identifier for general entity "redirecturl"
    …page&navigationid=12980000000319&parentid=12980000000278&redirecturl=referer" >

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 1769, Column 304: general entity "redirecturl" not defined and no default entity
    …page&navigationid=12980000000319&parentid=12980000000278&redirecturl=referer" >

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Error Line 1769, Column 315: reference to entity "redirecturl" for which no system identifier could be generated
    …page&navigationid=12980000000319&parentid=12980000000278&redirecturl=referer" >

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 1769, Column 303: entity was defined here
    …page&navigationid=12980000000319&parentid=12980000000278&redirecturl=referer" >
  • Error Line 1773, Column 184: duplicate specification of attribute "TYPE"
    …wordFocus(this, 'mkv_loginpassword')" value="" type="password" name="password">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Warning Line 1778, Column 227: NET-enabling start-tag requires SHORTTAG YES
    …ruidvat.nl/domains/kruidvat/content/layout_images/btnLogin.png" type="image" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 1781, Column 86: NET-enabling start-tag requires SHORTTAG YES
    …<input type="hidden" name="hidToMyAdvantage" value="0" id="hidToMyAdvantage" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 1782, Column 59: NET-enabling start-tag requires SHORTTAG YES
            <input value="1" type="hidden" name="loginposted" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 1783, Column 89: NET-enabling start-tag requires SHORTTAG YES
    …put value="http://www.kruidvat.nl/Default.aspx" type="hidden" name="nexturl" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 1823, Column 125: NET-enabling start-tag requires SHORTTAG YES
    …://www.kruidvat.nl/domains/kruidvat/content/layout_images/btnToMyProfid.png" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 1826, Column 116: NET-enabling start-tag requires SHORTTAG YES
    …tp://www.kruidvat.nl/domains/kruidvat/content/layout_images/btnRegister.png" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1833, Column 325: required attribute "ALT" not specified
    …8/nieuwe homepage/2011-38-home-A6.jpg"><div class="block"><div class="blockIma…

    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 1833, Column 1053: required attribute "ALT" not specified
    …homepage/2011-38-home-A8.jpg" border=0></A> <div class="block"><div class="blo…

    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 1833, Column 1525: required attribute "ALT" not specified
    …dvat/content//banners/2013-04/home/skyscraper_voices_klik-hier.png"></A>&nbsp; 

    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 1847, Column 30: required attribute "TYPE" not specified
    <script language="javascript">setSelectedMenu();</script>

    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>.

  • Warning Line 223, Column 166: reference to non-existent ID "SEARCHIN-ARTICLE"
    …nmouseup()" class="searchRadio selected" for="searchIn-article">Artikel</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 227, Column 162: reference to non-existent ID "SEARCHIN-STORE"
    …onmouseup()" class="searchRadio unselected" for="searchIn-store">Winkel</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

Visitor Analysis

Daily Visitor
  • 5.133 visits
Daily Visitor