Serwis Nr 1 w Polsce dla osób szukających niani lub opiekunki do dziecka. Niania.pl to również miejsce dla każdej opiekunki szukającej pracy. Zarejestruj się za darmo. ...

niania.pl
  • Domain Name
    niania.pl
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #127481
  • Page Size
    22.2 KB
  • Ip Address
    188.165.21.177
  • Heading
    H1: 1, H2: 2, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 1 JPG, 1 PNG

Website Meta Analysis

  • Title
    Niania, Opiekunka do dziecka dla Ciebie - Niania.pl
  • Meta Keyword
    Niania, opiekunka, oferty pracy, super niania, opiekunka, opiekunki, nianie, dzieci, dziecka, Warszawa, Kraków, Wrocław, Poznań, Gdańsk
  • Meta Description
    Serwis Nr 1 w Polsce dla osób szukających niani lub opiekunki do dziecka. Niania.pl to również miejsce dla każdej opiekunki szukającej pracy. Zarejestruj się za darmo.

Technical Analysis

  • Webserver
    nginx/0.7.67
  • Ip Address
    188.165.21.177
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from niania.pl.

HTML Analysis

  • server: nginx/0.7.67
  • date: Thu, 28 Feb 2013 19:08:28 GMT
  • content-type: text/html
  • connection: keep-alive
  • x-powered-by: PHP/5.3.3-7+squeeze14
  • cache-control: no-cache
  • pragma: no-cache
  • expires: Wed, 27 Feb 2013 19:08:28 GMT
  • last-modified: Wed, 27 Feb 2013 19:08:28 GMT
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for niania.pl

IP 188.165.21.177 Analysis

  • Country Code
    PL
  • Country Code3
    POL
  • Country Name
    Poland
  • City
    EU
  • Continent Code
    52° North
  • Latitude
    20.
  • Longitude
  • No whois ip data for 188.165.21.177

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 14 Errors
  • 12 Warnings
Ratio Text/Html
  • 0.7096617932006342
Message Error
  • Warning Line 48, Column 17: cannot generate system identifier for general entity "serviceType"
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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 "&" (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 æ 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 48, Column 17: general entity "serviceType" not defined and no default entity
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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 48, Column 28: reference not terminated by REFC delimiter
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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.

  • Error Line 48, Column 28: reference to entity "serviceType" for which no system identifier could be generated
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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 48, Column 16: entity was defined here
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";
  • Warning Line 48, Column 32: cannot generate system identifier for general entity "birth"
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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 "&" (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 æ 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 48, Column 32: general entity "birth" not defined and no default entity
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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 48, Column 37: reference not terminated by REFC delimiter
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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.

  • Error Line 48, Column 37: reference to entity "birth" for which no system identifier could be generated
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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 48, Column 31: entity was defined here
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";
  • Warning Line 48, Column 39: cannot generate system identifier for general entity "gender"
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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 "&" (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 æ 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 48, Column 39: general entity "gender" not defined and no default entity
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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 48, Column 45: reference not terminated by REFC delimiter
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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.

  • Error Line 48, Column 45: reference to entity "gender" for which no system identifier could be generated
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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 48, Column 38: entity was defined here
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";
  • Warning Line 48, Column 48: cannot generate system identifier for general entity "childAge"
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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 "&" (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 æ 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 48, Column 48: general entity "childAge" not defined and no default entity
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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 48, Column 56: reference not terminated by REFC delimiter
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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.

  • Error Line 48, Column 56: reference to entity "childAge" for which no system identifier could be generated
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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 48, Column 47: entity was defined here
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";
  • Warning Line 48, Column 58: cannot generate system identifier for general entity "latitude"
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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 "&" (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 æ 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 48, Column 58: general entity "latitude" not defined and no default entity
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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 48, Column 66: reference not terminated by REFC delimiter
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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.

  • Error Line 48, Column 66: reference to entity "latitude" for which no system identifier could be generated
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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 48, Column 57: entity was defined here
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";
  • Warning Line 48, Column 68: cannot generate system identifier for general entity "longtitude"
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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 "&" (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 æ 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 48, Column 68: general entity "longtitude" not defined and no default entity
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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 48, Column 78: reference not terminated by REFC delimiter
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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.

  • Error Line 48, Column 78: reference to entity "longtitude" for which no system identifier could be generated
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";

    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 48, Column 67: entity was defined here
    	var myVars = "&serviceType=-1&birth=&gender=0&childAge=&latitude=&longtitude=";
  • Error Line 100, Column 96: required attribute "alt" not specified
    …/www.niania.pl/System/gfx/front_baners/niania_baner1.jpg" class="main-baner" />

    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 323, Column 139: duplicate specification of attribute "class"
    …nia/Statute.html?" id="popover" class="popover" name="880x440xscroll" rel="nof…

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

Visitor Analysis

Daily Visitor
  • 1.365 visits
Daily Visitor