IMujer te traerá todas las novedades sobre moda y tendencias, los mejores trucos de belleza y los más prácticos consejos para la mujer actual. ...

imujer.com
  • Domain Name
    imujer.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #37048
  • Page Size
    62.4 KB
  • Ip Address
    94.23.119.31
  • Heading
    H1: 1, H2: 26, H3: 48, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 58 JPG, 1 PNG

Website Meta Analysis

  • Title
    IMujer - Belleza, Consejos y Tendencias
  • Meta Keyword
  • Meta Description
    IMujer te traerá todas las novedades sobre moda y tendencias, los mejores trucos de belleza y los más prácticos consejos para la mujer actual.

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    94.23.119.31
  • Domain Age
    5 Years, 10 Months, 11 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Fri, 01 Mar 2013 03:58:02 GMT
  • content-type: text/html; charset=utf-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-powered-by: PHP/5.2.6-1+lenny13
  • x-drupal-cache: MISS
  • last-modified: Fri, 01 Mar 2013 03:18:11 +0000
  • cache-control: public, max-age=0
  • etag: "1362107891-0"
  • expires: Sun, 11 Mar 1984 12:00:00 GMT
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for imujer.com

IP 94.23.119.31 Analysis

  • Country Code
    ES
  • Country Code3
    ESP
  • Country Name
    Spain
  • City
    EU
  • Continent Code
    40° North
  • Latitude
    4.
  • Longitude
  • No whois ip data for 94.23.119.31

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 18 Errors
  • 9 Warnings
Ratio Text/Html
  • 0.6991345717460367
Message Error
  • Error Line 15, Column 113: end tag for "meta" omitted, but OMITTAG NO was specified
    …, maximum-scale=1, minimum-scale=1, user-scalable=no"><!-- media-queries.js -->

    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 15, Column 1: start tag was here
    <meta name="viewport" content="width=100%, initial-scale=1, maximum-scale=1, mi…
  • Error Line 25, Column 96: end tag for "link" omitted, but OMITTAG NO was specified
    …p://fonts.googleapis.com/css?family=Coustard' rel='stylesheet' type='text/css'>

    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 25, Column 2: start tag was here
    	<link href='http://fonts.googleapis.com/css?family=Coustard' rel='stylesheet' …
  • Error Line 26, Column 105: end tag for "link" omitted, but OMITTAG NO was specified
    ….googleapis.com/css?family=Open+Sans:400,300' rel='stylesheet' type='text/css'>

    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 26, Column 2: start tag was here
    	<link href='http://fonts.googleapis.com/css?family=Open+Sans:400,300' rel='sty…
  • Error Line 315, Column 81: there is no attribute "src"
    …span> en Facebook</h2>    <iframe src="http://www.facebook.com/plugins/likebox…

    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 315, Column 343: there is no attribute "scrolling"
    …&amp;appId=252820748090203" scrolling="no" frameborder="0" style="border:none;…

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

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

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

  • Error Line 315, Column 360: there is no attribute "frameborder"
    …748090203" scrolling="no" frameborder="0" style="border:none; overflow:hidden;…

    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 315, Column 370: there is no attribute "style"
    … scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:292…

    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 315, Column 446: there is no attribute "allowTransparency"
    …w:hidden; width:292px; height:62px;" allowTransparency="true"></iframe>  </div>

    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 315, Column 452: element "iframe" undefined
    …w:hidden; width:292px; height:62px;" allowTransparency="true"></iframe>  </div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 475, Column 14: required attribute "type" not specified
          <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 485, Column 57: cannot generate system identifier for general entity "c2"
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=14306004&cv=2.0&cj=1" />

    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 485, Column 57: general entity "c2" not defined and no default entity
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=14306004&cv=2.0&cj=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.

  • Warning Line 485, Column 59: reference not terminated by REFC delimiter
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=14306004&cv=2.0&cj=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 485, Column 59: reference to external entity in attribute value
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=14306004&cv=2.0&cj=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 485, Column 59: reference to entity "c2" for which no system identifier could be generated
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=14306004&cv=2.0&cj=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 485, Column 56: entity was defined here
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=14306004&cv=2.0&cj=1" />
  • Warning Line 485, Column 69: cannot generate system identifier for general entity "cv"
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=14306004&cv=2.0&cj=1" />

    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 485, Column 69: general entity "cv" not defined and no default entity
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=14306004&cv=2.0&cj=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.

  • Warning Line 485, Column 71: reference not terminated by REFC delimiter
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=14306004&cv=2.0&cj=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 485, Column 71: reference to external entity in attribute value
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=14306004&cv=2.0&cj=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 485, Column 71: reference to entity "cv" for which no system identifier could be generated
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=14306004&cv=2.0&cj=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 485, Column 68: entity was defined here
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=14306004&cv=2.0&cj=1" />
  • Warning Line 485, Column 76: cannot generate system identifier for general entity "cj"
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=14306004&cv=2.0&cj=1" />

    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 485, Column 76: general entity "cj" not defined and no default entity
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=14306004&cv=2.0&cj=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.

  • Warning Line 485, Column 78: reference not terminated by REFC delimiter
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=14306004&cv=2.0&cj=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 485, Column 78: reference to external entity in attribute value
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=14306004&cv=2.0&cj=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 485, Column 78: reference to entity "cj" for which no system identifier could be generated
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=14306004&cv=2.0&cj=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 485, Column 75: entity was defined here
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=14306004&cv=2.0&cj=1" />
  • Error Line 485, Column 83: required attribute "alt" not specified
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=14306004&cv=2.0&cj=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 485, Column 83: 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
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=14306004&cv=2.0&cj=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
  • 4.783 visits
Daily Visitor