brw.com.pl

Black Red White - najchętniej kupowane meble w Polsce - Pokój dzienny, Biuro i gabinet, Jadalnia, Przedpokój, Kuchnia, Pokój młodzieżowy, Sypialnia. ...

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

Overview Info

  • Domain Name
    brw.com.pl
  • Favicon
  • Alexa Rank
    #48080
  • Google Page Rank
    PR 5
  • Ip Address
    79.133.202.149
  • Page Size
    66.2 KB
  • Images
    0 GIF, 4 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 27 0 0 0 3

Website Meta Analysis



  • Title
    Black Red White - najchętniej kupowane meble w polsce
  • Meta Keyword
    meble, tanie meble, meble Black Red White, meble dziecięce, łóżka, pokój młodzieżowy,
  • Meta Description
    Black Red White - najchętniej kupowane meble w Polsce - Pokój dzienny, Biuro i gabinet, Jadalnia, Przedpokój, Kuchnia, Pokój młodzieżowy, Sypialnia.

Technical Analysis



  • Webserver
    nginx/1.2.1
  • Ip Address
    79.133.202.149
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/1.2.1
  • date: Tue, 09 Jul 2013 04:10:49 GMT
  • content-type: text/html; charset=utf-8
  • connection: keep-alive
  • x-powered-by: PHP/5.3.3-7+squeeze14
  • pragma: no-cache
  • cache-control: no-store, no-cache, max-age=0, must-revalidate
  • last-modified: Tue, 09 Jul 2013 04:10:49 GMT
  • expires: Mon, 26 Jul 1997 05:00:00 GMT
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for brw.com.pl

IP 79.133.202.149 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 29 Errors
  • 18 Warnings
Ratio Text/Html
  • 0.6447762515307554
Message Error
  • Error Line 2, Column 1: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <html>

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

  • Error Line 157, Column 17: end tag for "br" omitted, but OMITTAG NO was specified
                <br><br>

    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 157, Column 13: start tag was here
                <br><br>
  • Error Line 157, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
                <br><br>

    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 157, Column 17: start tag was here
                <br><br>
  • Error Line 165, Column 129: there is no attribute "align"
    …/www.brw.com.pl/swf/kuchniebezvat.swf" width="980" height="285" align="middle">

    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 201, Column 85: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …nd_lin0" href="http://www.basic.brw.com.pl/"><div class="column-top"></div></a>

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

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

  • Error Line 208, Column 88: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …lin0" href="http://www.brw.com.pl/pl/optima"><div class="column-top"></div></a>

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

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

  • Error Line 216, Column 80: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …s="land_lin0" href="http://www.salonybrw.pl"><div class="column-top"></div></a>

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

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

  • Warning Line 348, Column 72: cannot generate system identifier for general entity "partnerID"
    ….invitemedia.com/pixel?pixelID=126454&partnerID=482&clientID=9576&key=segment&…

    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 348, Column 72: general entity "partnerID" not defined and no default entity
    ….invitemedia.com/pixel?pixelID=126454&partnerID=482&clientID=9576&key=segment&…

    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 348, Column 81: reference not terminated by REFC delimiter
    …dia.com/pixel?pixelID=126454&partnerID=482&clientID=9576&key=segment&returnTyp…

    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 348, Column 81: reference to external entity in attribute value
    …dia.com/pixel?pixelID=126454&partnerID=482&clientID=9576&key=segment&returnTyp…

    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 348, Column 81: reference to entity "partnerID" for which no system identifier could be generated
    …dia.com/pixel?pixelID=126454&partnerID=482&clientID=9576&key=segment&returnTyp…

    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 348, Column 71: entity was defined here
    …l.invitemedia.com/pixel?pixelID=126454&partnerID=482&clientID=9576&key=segment…
  • Warning Line 348, Column 86: cannot generate system identifier for general entity "clientID"
    …om/pixel?pixelID=126454&partnerID=482&clientID=9576&key=segment&returnType=js"…

    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 348, Column 86: general entity "clientID" not defined and no default entity
    …om/pixel?pixelID=126454&partnerID=482&clientID=9576&key=segment&returnType=js"…

    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 348, Column 94: reference not terminated by REFC delimiter
    …?pixelID=126454&partnerID=482&clientID=9576&key=segment&returnType=js"></scrip…

    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 348, Column 94: reference to external entity in attribute value
    …?pixelID=126454&partnerID=482&clientID=9576&key=segment&returnType=js"></scrip…

    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 348, Column 94: reference to entity "clientID" for which no system identifier could be generated
    …?pixelID=126454&partnerID=482&clientID=9576&key=segment&returnType=js"></scrip…

    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 348, Column 85: entity was defined here
    …com/pixel?pixelID=126454&partnerID=482&clientID=9576&key=segment&returnType=js…
  • Warning Line 348, Column 100: cannot generate system identifier for general entity "key"
    …pixelID=126454&partnerID=482&clientID=9576&key=segment&returnType=js"></script>

    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 348, Column 100: general entity "key" not defined and no default entity
    …pixelID=126454&partnerID=482&clientID=9576&key=segment&returnType=js"></script>

    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 348, Column 103: reference not terminated by REFC delimiter
    …pixelID=126454&partnerID=482&clientID=9576&key=segment&returnType=js"></script>

    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 348, Column 103: reference to external entity in attribute value
    …pixelID=126454&partnerID=482&clientID=9576&key=segment&returnType=js"></script>

    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 348, Column 103: reference to entity "key" for which no system identifier could be generated
    …pixelID=126454&partnerID=482&clientID=9576&key=segment&returnType=js"></script>

    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 348, Column 99: entity was defined here
    …pixelID=126454&partnerID=482&clientID=9576&key=segment&returnType=js"></script>
  • Warning Line 348, Column 112: cannot generate system identifier for general entity "returnType"
    …pixelID=126454&partnerID=482&clientID=9576&key=segment&returnType=js"></script>

    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 348, Column 112: general entity "returnType" not defined and no default entity
    …pixelID=126454&partnerID=482&clientID=9576&key=segment&returnType=js"></script>

    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 348, Column 122: reference not terminated by REFC delimiter
    …pixelID=126454&partnerID=482&clientID=9576&key=segment&returnType=js"></script>

    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 348, Column 122: reference to external entity in attribute value
    …pixelID=126454&partnerID=482&clientID=9576&key=segment&returnType=js"></script>

    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 348, Column 122: reference to entity "returnType" for which no system identifier could be generated
    …pixelID=126454&partnerID=482&clientID=9576&key=segment&returnType=js"></script>

    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 348, Column 111: entity was defined here
    …pixelID=126454&partnerID=482&clientID=9576&key=segment&returnType=js"></script>
  • Error Line 348, Column 126: required attribute "type" not specified
    …pixelID=126454&partnerID=482&clientID=9576&key=segment&returnType=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>.

  • Warning Line 350, Column 78: reference not terminated by REFC delimiter
    …dia.com/pixel?pixelID=126454&partnerID=482&clientID=9576&key=segment" width="1…

    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 350, Column 78: reference to external entity in attribute value
    …dia.com/pixel?pixelID=126454&partnerID=482&clientID=9576&key=segment" width="1…

    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 350, Column 78: reference to entity "partnerID" for which no system identifier could be generated
    …dia.com/pixel?pixelID=126454&partnerID=482&clientID=9576&key=segment" width="1…

    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 348, Column 71: entity was defined here
    …l.invitemedia.com/pixel?pixelID=126454&partnerID=482&clientID=9576&key=segment…
  • Warning Line 350, Column 91: reference not terminated by REFC delimiter
    …?pixelID=126454&partnerID=482&clientID=9576&key=segment" width="1" height="1" …

    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 350, Column 91: reference to external entity in attribute value
    …?pixelID=126454&partnerID=482&clientID=9576&key=segment" width="1" height="1" …

    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 350, Column 91: reference to entity "clientID" for which no system identifier could be generated
    …?pixelID=126454&partnerID=482&clientID=9576&key=segment" width="1" height="1" …

    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 348, Column 85: entity was defined here
    …com/pixel?pixelID=126454&partnerID=482&clientID=9576&key=segment&returnType=js…
  • Warning Line 350, Column 100: reference not terminated by REFC delimiter
    …pixelID=126454&partnerID=482&clientID=9576&key=segment" width="1" height="1" />

    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 350, Column 100: reference to external entity in attribute value
    …pixelID=126454&partnerID=482&clientID=9576&key=segment" width="1" height="1" />

    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 350, Column 100: reference to entity "key" for which no system identifier could be generated
    …pixelID=126454&partnerID=482&clientID=9576&key=segment" width="1" height="1" />

    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 348, Column 99: entity was defined here
    …pixelID=126454&partnerID=482&clientID=9576&key=segment&returnType=js"></script>
  • Error Line 350, Column 132: required attribute "alt" not specified
    …pixelID=126454&partnerID=482&clientID=9576&key=segment" width="1" height="1" />

    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 350, Column 132: document type does not allow element "img" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "address", "fieldset", "ins", "del" start-tag
    …pixelID=126454&partnerID=482&clientID=9576&key=segment" width="1" height="1" />

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

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

Visitor Analysis

Daily Visitor
  • 3.267 visits

In Page Analysis