spele.nl

De nieuwste en leukste spelletjes op 1 website verzameld! Race games, avontuur, behendigheid, puzzel, sport, multiplayer en nog veel meer op ★ Spele.nl ★! ...

Display Widget for this domain on your website. Click Here
This data was last updated from 09-07-2013 06:06:51  (update).

Overview Info

  • Domain Name
    spele.nl
  • Favicon
  • Alexa Rank
    #12743
  • Google Page Rank
    PR 5
  • Ip Address
    190.93.252.112
  • Page Size
    119 KB
  • Images
    0 GIF, 57 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 12 5 0 0 0

Website Meta Analysis



  • Title
    Spele.nl - Spelletjes, games en spellen - Gratis op Spele.nl !
  • Meta Keyword
    Online spellen, gratis spellen, gratis online spellen, kids spellen, kids spellen, kinder spelen, spel, spele, game, funny games, funny spellen, games
  • Meta Description
    De nieuwste en leukste spelletjes op 1 website verzameld! Race games, avontuur, behendigheid, puzzel, sport, multiplayer en nog veel meer op ★ Spele.nl ★!

Technical Analysis



  • Webserver
    cloudflare-nginx
  • Ip Address
    190.93.252.112
  • Domain Age
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: cloudflare-nginx
  • date: Tue, 09 Jul 2013 06:06:43 GMT
  • content-type: text/html
  • connection: keep-alive
  • x-varnish: 1091683635 1091645657
  • age: 1984
  • via: 1.1 varnish
  • x-served-by: spelev3-varnish3
  • x-cache-varnish: HIT
  • x-cache-hits: 599
  • cf-ray: 8b2d4717c3205bb
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
Domain Domain Name: spele.nl
Domain Status: active
Registrar:
MuntInternet Networks B.V.
Oosterdijk 39
8601BP SNEEK
Netherlands

Name Servers:
ns1.muntinternet.net
ns2.muntinternet.net
ns3.muntinternet.net
Registrar: NL Domain Registry
Copyright notice
No part of this publication may be reproduced, published, stored in a
retrieval system, or transmitted, in any form or by any means,
electronic, mechanical, recording, or otherwise, without prior
permission of the Foundation for Internet Domain Registration in the
Netherlands (SIDN).
These restrictions apply equally to registrars, except in that
reproductions and publications are permitted insofar as they are
reasonable, necessary and solely in the context of the registration
activities referred to in the General Terms and Conditions for .nl
Registrars.
Any use of this material for advertising, targeting commercial offers or
similar activities is explicitly forbidden and liable to result in legal
action. Anyone who is aware or suspects that such activities are taking
place is asked to inform the Foundation for Internet Domain Registration
in the Netherlands.
(c) The Foundation for Internet Domain Registration in the Netherlands
(SIDN) Dutch Copyright Act, protection of authors' rights (Section 10,
subsection 1, clause 1).

IP 190.93.252.112 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 16 Errors
  • 7 Warnings
Ratio Text/Html
  • 0.8091723990740589
Message Error
  • Error Line 10, Column 16: there is no attribute "property"
    <meta property="og:title" content="Spele.nl - Spele.nl - Spelletjes, games en s…

    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 21, Column 73: required attribute "type" not specified
    …ript src="//ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min.js"></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>.

  • Error Line 22, Column 78: required attribute "type" not specified
    …src="//ajax.googleapis.com/ajax/libs/jqueryui/1.9.1/jquery-ui.min.js"></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>.

  • Error Line 78, Column 39: document type does not allow element "h4" here
                    ssoLogin        : "<h4>%GAMENAME</h4><p>%GAMEDESC</p>",

    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 78, Column 56: document type does not allow element "p" here
                    ssoLogin        : "<h4>%GAMENAME</h4><p>%GAMEDESC</p>",

    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 170, Column 32: there is no attribute "data-icon"
    <button class="more" data-icon="ui-icon-triangle-1-s">Meer acties</button>

    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.

  • Warning Line 286, Column 108: character "&" is the first character of a delimiter but occurred as data
    …ultiplayer-spellen/" id="topNav_sub_item_605">Bord & Kaart Multiplayer</a></li>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 518, Column 12: there is no attribute "role"
    <form role="search" method="get" id="searchform" class="search searchHeader" da…

    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 518, Column 93: there is no attribute "data-threshold"
    …="searchform" class="search searchHeader" data-threshold="3" action="/search/">

    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 520, Column 20: value of attribute "type" cannot be "search"; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
    <input type="search" placeholder="Zoeken op spele.nl" value="" name="q" id="q"/>

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 520, Column 34: there is no attribute "placeholder"
    <input type="search" placeholder="Zoeken op spele.nl" value="" name="q" id="q"/>

    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 783, Column 110: there is no attribute "data-images"
    …e.nl/meppen-21296-b.jpg)" data-images="http://proxy.spele.nl/meppen-21296-b.jp…

    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.

  • Warning Line 1829, Column 48: cannot generate system identifier for general entity "utm_medium"
    …http://starbie.nl?utm_source=spele.nl&utm_medium=footer_links&utm_campaign=oth…

    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 1829, Column 48: general entity "utm_medium" not defined and no default entity
    …http://starbie.nl?utm_source=spele.nl&utm_medium=footer_links&utm_campaign=oth…

    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.

  • Warning Line 1829, Column 58: reference not terminated by REFC delimiter
    …rbie.nl?utm_source=spele.nl&utm_medium=footer_links&utm_campaign=others" title…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 1829, Column 58: reference to external entity in attribute value
    …rbie.nl?utm_source=spele.nl&utm_medium=footer_links&utm_campaign=others" title…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 1829, Column 58: reference to entity "utm_medium" for which no system identifier could be generated
    …rbie.nl?utm_source=spele.nl&utm_medium=footer_links&utm_campaign=others" title…

    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 1829, Column 47: entity was defined here
    …"http://starbie.nl?utm_source=spele.nl&utm_medium=footer_links&utm_campaign=ot…
  • Warning Line 1829, Column 72: cannot generate system identifier for general entity "utm_campaign"
    …urce=spele.nl&utm_medium=footer_links&utm_campaign=others" title="online meisj…

    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 1829, Column 72: general entity "utm_campaign" not defined and no default entity
    …urce=spele.nl&utm_medium=footer_links&utm_campaign=others" title="online meisj…

    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.

  • Warning Line 1829, Column 84: reference not terminated by REFC delimiter
    …l&utm_medium=footer_links&utm_campaign=others" title="online meisjes spelletje…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 1829, Column 84: reference to external entity in attribute value
    …l&utm_medium=footer_links&utm_campaign=others" title="online meisjes spelletje…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 1829, Column 84: reference to entity "utm_campaign" for which no system identifier could be generated
    …l&utm_medium=footer_links&utm_campaign=others" title="online meisjes spelletje…

    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 1829, Column 71: entity was defined here
    …ource=spele.nl&utm_medium=footer_links&utm_campaign=others" title="online meis…
  • Error Line 1888, Column 168: end tag for "img" omitted, but OMITTAG NO was specified
    …p; c6=imnetworks%2Cgames&amp;cj=1" height="1" width="1" alt="*"></p></noscript>

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

  • Info Line 1888, Column 14: start tag was here
    <noscript><p><img src="http://b.scorecardresearch.com/p? c1=2&amp;c2=11547568&a…

Visitor Analysis

Daily Visitor
  • 13.767 visits

In Page Analysis