دانلود جدیدترین آهنگ ها، دانلود موسیقی، دانلود ویدئو ها، دانلود موزیک ویدئو و دانلود فیلم و دانلود سریال خارجی با لینک مستقیم Download Music, Music video , Download Movie , TV Show ...

farskids316.com
  • Domain Name
    farskids316.com
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #56939
  • Page Size
    32.2 KB
  • Ip Address
    198.144.158.167
  • Heading
    H1: 1, H2: 1, H3: 1, H4: 8, H5: 0, H6: 0
  • Images
    1 GIF, 3 JPG, 5 PNG

Website Meta Analysis

  • Title
    فارس کیدذ | مرجع دانلود موزیک و فیلم
  • Meta Keyword
    دانلود آهنگ ، دانلود آهنگ جدید ، دانلود موزیک ویدئو ، دانلود وبدیو , دانلود موزیک , دانلود موزیک جدید , جدیدترین آهنگ ها , دانلود آلبوم جدید , دانلود آهنگ زیبا , فارس کیدذ , music , video , Download music , persian music , download persian music , download farsi music , download itunes music , music video , new music , دانلود موزیک , دانلودویدئو , دانلود فیلم , فیلم لینک مستقیم , آهنگ لینک مستقیم , موزیک ویدئو , آهنگ لوس آنجلسی , موزیک ویدئو جدید , آهنگ خارجی , دانلود موزیک ویدئو , دانلود آهنگ خارجی , دانلود فیلم هالیوود , دانلود فیلم , دانلود سریال , فیلم لینک مستقیم , سریال لینک مستقیم , فارس کیدذ , farskids , farskids new address , faskids music , فارس کیدز
  • Meta Description
    دانلود جدیدترین آهنگ ها، دانلود موسیقی، دانلود ویدئو ها، دانلود موزیک ویدئو و دانلود فیلم و دانلود سریال خارجی با لینک مستقیم Download Music, Music video , Download Movie , TV Show

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    198.144.158.167
  • Domain Age
    11 Months, 17 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Tue, 08 Oct 2013 08:37:22 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • x-powered-by: PHP/5.2.17
  • x-pingback: http://www.farskids421.com/xmlrpc.php
  • link: ; rel=shortlink
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: FARSKIDS316.COM

Registration Date: 26-Oct-2012
Expiration Date: 26-Oct-2013

Status:LOCKED



Name Servers:
ns1.parand.in
ns2.parand.in


Registrant Contact Details:
Alex
Alex Diamo ( email )
Usa Florida Orlando Spring 564 NO 352
Orlando
spring,65454
US
Tel. +1.447654654
Fax. +1.447654654

Administrative Contact Details:
Alex
Alex Diamo ( email )
Usa Florida Orlando Spring 564 NO 352
Orlando
spring,65454
US
Tel. +1.447654654
Fax. +1.447654654

Technical Contact Details:
Alex
Alex Diamo ( email )
Usa Florida Orlando Spring 564 NO 352
Orlando
spring,65454
US
Tel. +1.447654654
Fax. +1.447654654

Billing Contact Details:
Alex
Alex Diamo ( email )
Usa Florida Orlando Spring 564 NO 352
Orlando
spring,65454
US
Tel. +1.447654654
Fax. +1.447654654

DNS Analysis


DNS servers
ns1.parand.in [198.144.158.167]
ns2.parand.in [198.144.158.155]


DNS Records

Answer records
farskids316.com TXT v=spf1 +a +mx +ip4:198.144.158.155 ?all 14400s
farskids316.com MX
preference: 0
exchange: farskids316.com
14400s
farskids316.com SOA
server: ns1.parand.in
email: farskids@gmail.com
serial: 2012122305
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
farskids316.com NS  ns1.parand.in 86400s
farskids316.com NS  ns2.parand.in 86400s
farskids316.com A 198.144.158.167 14400s

Authority records

Additional records
farskids316.com A 198.144.158.167 14400s
ns1.parand.in A 198.144.158.167 14400s
ns2.parand.in A 198.144.158.155 14400s

IP 198.144.158.167 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 134 Errors
  • 26 Warnings
Ratio Text/Html
  • 0.6010844541378892
Message Error
  • Warning Line 4, Column 2: character "<" is the first character of a delimiter but occurred as data
    	<!  SEO by : SEO TECH   WWW.SEOTECH.IR  >

    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 4, Column 2: character data is not allowed here
    	<!  SEO by : SEO TECH   WWW.SEOTECH.IR  >

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 5, Column 13: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<meta name=robots content="index, follow">
  • Error Line 5, Column 44: end tag for "meta" omitted, but OMITTAG NO was specified
    	<meta name=robots content="index, follow">

    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 5, Column 2: start tag was here
    	<meta name=robots content="index, follow">
  • Error Line 6, Column 49: end tag for "meta" omitted, but OMITTAG NO was specified
    	<meta name="googlebot" content="index, follow">

    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 6, Column 2: start tag was here
    	<meta name="googlebot" content="index, follow">
  • Error Line 77, Column 17: there is no attribute "property"
    	<meta property="og:site_name" content="فارس کیدذ | مرجع دانلود موزیک و فیلم"/>

    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 138, Column 38: character ";" not allowed in attribute specification list
    function wpsrload(){ for(var i=0;i<wc;i++){wpsrasync(wu[i]);} }
  • Error Line 138, Column 38: element "wc" undefined
    function wpsrload(){ for(var i=0;i<wc;i++){wpsrasync(wu[i]);} }

    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 140, Column 9: end tag for "wc" omitted, but OMITTAG NO was specified
    </script>

    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 138, Column 35: start tag was here
    function wpsrload(){ for(var i=0;i<wc;i++){wpsrasync(wu[i]);} }
  • Error Line 185, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 204, Column 61: cannot generate system identifier for general entity "m"
      <img src="http://opi.yahoo.com/online?u=farskids7@att.net&m=g&t=0" border=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 204, Column 61: general entity "m" not defined and no default entity
      <img src="http://opi.yahoo.com/online?u=farskids7@att.net&m=g&t=0" border=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.

  • Warning Line 204, Column 62: reference not terminated by REFC delimiter
      <img src="http://opi.yahoo.com/online?u=farskids7@att.net&m=g&t=0" border=0 />

    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 204, Column 62: reference to external entity in attribute value
      <img src="http://opi.yahoo.com/online?u=farskids7@att.net&m=g&t=0" border=0 />

    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 204, Column 62: reference to entity "m" for which no system identifier could be generated
      <img src="http://opi.yahoo.com/online?u=farskids7@att.net&m=g&t=0" border=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 204, Column 60: entity was defined here
      <img src="http://opi.yahoo.com/online?u=farskids7@att.net&m=g&t=0" border=0 />
  • Warning Line 204, Column 65: cannot generate system identifier for general entity "t"
      <img src="http://opi.yahoo.com/online?u=farskids7@att.net&m=g&t=0" border=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 204, Column 65: general entity "t" not defined and no default entity
      <img src="http://opi.yahoo.com/online?u=farskids7@att.net&m=g&t=0" border=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.

  • Warning Line 204, Column 66: reference not terminated by REFC delimiter
      <img src="http://opi.yahoo.com/online?u=farskids7@att.net&m=g&t=0" border=0 />

    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 204, Column 66: reference to external entity in attribute value
      <img src="http://opi.yahoo.com/online?u=farskids7@att.net&m=g&t=0" border=0 />

    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 204, Column 66: reference to entity "t" for which no system identifier could be generated
      <img src="http://opi.yahoo.com/online?u=farskids7@att.net&m=g&t=0" border=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 204, Column 64: entity was defined here
      <img src="http://opi.yahoo.com/online?u=farskids7@att.net&m=g&t=0" border=0 />
  • Error Line 204, Column 77: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <img src="http://opi.yahoo.com/online?u=farskids7@att.net&m=g&t=0" border=0 />
  • Error Line 204, Column 80: required attribute "alt" not specified
      <img src="http://opi.yahoo.com/online?u=farskids7@att.net&m=g&t=0" border=0 />

    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 211, Column 59: reference not terminated by REFC delimiter
      <img src="http://opi.yahoo.com/online?u=farskids_devil&m=g&t=0" border=0 />

    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 211, Column 59: reference to external entity in attribute value
      <img src="http://opi.yahoo.com/online?u=farskids_devil&m=g&t=0" border=0 />

    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 211, Column 59: reference to entity "m" for which no system identifier could be generated
      <img src="http://opi.yahoo.com/online?u=farskids_devil&m=g&t=0" border=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 204, Column 60: entity was defined here
      <img src="http://opi.yahoo.com/online?u=farskids7@att.net&m=g&t=0" border=0 />
  • Warning Line 211, Column 63: reference not terminated by REFC delimiter
      <img src="http://opi.yahoo.com/online?u=farskids_devil&m=g&t=0" border=0 />

    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 211, Column 63: reference to external entity in attribute value
      <img src="http://opi.yahoo.com/online?u=farskids_devil&m=g&t=0" border=0 />

    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 211, Column 63: reference to entity "t" for which no system identifier could be generated
      <img src="http://opi.yahoo.com/online?u=farskids_devil&m=g&t=0" border=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 204, Column 64: entity was defined here
      <img src="http://opi.yahoo.com/online?u=farskids7@att.net&m=g&t=0" border=0 />
  • Error Line 211, Column 74: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <img src="http://opi.yahoo.com/online?u=farskids_devil&m=g&t=0" border=0 />
  • Error Line 211, Column 77: required attribute "alt" not specified
      <img src="http://opi.yahoo.com/online?u=farskids_devil&m=g&t=0" border=0 />

    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 218, Column 56: reference not terminated by REFC delimiter
      <img src="http://opi.yahoo.com/online?u=masoud.fa99&m=g&t=0" border=0 />

    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 218, Column 56: reference to external entity in attribute value
      <img src="http://opi.yahoo.com/online?u=masoud.fa99&m=g&t=0" border=0 />

    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 218, Column 56: reference to entity "m" for which no system identifier could be generated
      <img src="http://opi.yahoo.com/online?u=masoud.fa99&m=g&t=0" border=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 204, Column 60: entity was defined here
      <img src="http://opi.yahoo.com/online?u=farskids7@att.net&m=g&t=0" border=0 />
  • Warning Line 218, Column 60: reference not terminated by REFC delimiter
      <img src="http://opi.yahoo.com/online?u=masoud.fa99&m=g&t=0" border=0 />

    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 218, Column 60: reference to external entity in attribute value
      <img src="http://opi.yahoo.com/online?u=masoud.fa99&m=g&t=0" border=0 />

    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 218, Column 60: reference to entity "t" for which no system identifier could be generated
      <img src="http://opi.yahoo.com/online?u=masoud.fa99&m=g&t=0" border=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 204, Column 64: entity was defined here
      <img src="http://opi.yahoo.com/online?u=farskids7@att.net&m=g&t=0" border=0 />
  • Error Line 218, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <img src="http://opi.yahoo.com/online?u=masoud.fa99&m=g&t=0" border=0 />
  • Error Line 218, Column 74: required attribute "alt" not specified
      <img src="http://opi.yahoo.com/online?u=masoud.fa99&m=g&t=0" border=0 />

    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 190: end tag for "img" omitted, but OMITTAG NO was specified
    …es/farskids-seo-v1/images/login.jpg" width="277" height="66" alt="" ></a></div>

    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 269, Column 66: start tag was here
    …><a href="http://www.farskids320.com"><img src="http://www.farskids320.com/wp-…
  • Error Line 279, Column 140: end tag for "img" omitted, but OMITTAG NO was specified
    …><img src="/wp-content/uploads/2013/01/online-ardalan-tome.jpg" alt=""></a><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 279, Column 67: start tag was here
    …lan-tomeh-besalamat/" target="_blank"><img src="/wp-content/uploads/2013/01/on…
  • Error Line 279, Column 145: end tag for "br" omitted, but OMITTAG NO was specified
    …><img src="/wp-content/uploads/2013/01/online-ardalan-tome.jpg" alt=""></a><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 279, Column 141: start tag was here
    …><img src="/wp-content/uploads/2013/01/online-ardalan-tome.jpg" alt=""></a><br>
  • Error Line 313, Column 155: required attribute "alt" not specified
    …/www.farskids320.com/wp-content/themes/farskids-seo-v1/images/wink.gif" ></div>

    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 313, Column 161: end tag for "img" omitted, but OMITTAG NO was specified
    …/www.farskids320.com/wp-content/themes/farskids-seo-v1/images/wink.gif" ></div>

    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 313, Column 67: start tag was here
    …: ۸ بهمن ۱۳۹۱ شما در فارس کیدذ هستید  <img src="http://www.farskids320.com/wp-…
  • Error Line 314, Column 36: required attribute "type" not specified
        <div class="time">ساعت  <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 324, Column 53: character "<" is the first character of a delimiter but occurred as data
    …getElementById('CLOCK').innerHTML=((HH<10  )? "0"+HH:HH) + ":" + ((MM<10)? "0"…

    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.
  • Warning Line 324, Column 84: character "<" is the first character of a delimiter but occurred as data
    …ML=((HH<10  )? "0"+HH:HH) + ":" + ((MM<10)? "0"+MM:MM) + ":" + ((SS<10)? "0"+S…

    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.
  • Warning Line 324, Column 113: character "<" is the first character of a delimiter but occurred as data
    …HH<10  )? "0"+HH:HH) + ":" + ((MM<10)? "0"+MM:MM) + ":" + ((SS<10)? "0"+SS:SS);

    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 330, Column 124: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="learn"><img src="/wp-content/uploads/2012/08/e1.gif" border="0" alt=""></a>

    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 330, Column 57: start tag was here
    …ation/" target="_blank" class="learn"><img src="/wp-content/uploads/2012/08/e1…
  • Error Line 340, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 340, Column 1: start tag was here
    <br>
  • Error Line 342, Column 12: there is no attribute "role"
    <form role="search" method="get" id="searchform" action="http://www.farskids320…

    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 348, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 348, Column 1: start tag was here
    <br>
  • Error Line 360, Column 36: there is no attribute "data-href"
    <div class="fb-like-box" data-href="http://www.facebook.com/farskids4ever" data…

    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 360, Column 87: there is no attribute "data-width"
    …acebook.com/farskids4ever" data-width="310" data-height="440" data-show-faces=…

    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 360, Column 105: there is no attribute "data-height"
    …ds4ever" data-width="310" data-height="440" data-show-faces="true" data-border…

    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 360, Column 127: there is no attribute "data-show-faces"
    …10" data-height="440" data-show-faces="true" data-border-color="#fff" data-str…

    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 360, Column 152: there is no attribute "data-border-color"
    …a-show-faces="true" data-border-color="#fff" data-stream="false" data-header="…

    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 360, Column 171: there is no attribute "data-stream"
    …s="true" data-border-color="#fff" data-stream="false" data-header="true"></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 360, Column 191: there is no attribute "data-header"
    …s="true" data-border-color="#fff" data-stream="false" data-header="true"></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 383, Column 173: end tag for "img" omitted, but OMITTAG NO was specified
    …-seo-v1/images/radio.jpg" width="196" height="118" alt="رادیو فارس کیدذ"></div>

    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 383, Column 32: start tag was here
                <div class="login"><img src="http://www.farskids320.com/wp-content/…
  • Error Line 386, Column 163: ID "dewplayer" already defined
    …-v1/swf/dewplayer.swf" width="200" height="20" id="dewplayer" name="dewplayer">

    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 280, Column 163: ID "dewplayer" first defined here
    …-v1/swf/dewplayer.swf" width="200" height="20" id="dewplayer" name="dewplayer">
  • Error Line 416, Column 169: end tag for "img" omitted, but OMITTAG NO was specified
    …kids-seo-v1/images/sms.jpg" width="298" height="69" alt="خبرنامه پیامکی"></div>

    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 416, Column 32: start tag was here
                <div class="login"><img src="http://www.farskids320.com/wp-content/…
  • Error Line 434, Column 110: end tag for "img" omitted, but OMITTAG NO was specified
    …kids320.com/wp-content/uploads/2012/07/upywoulw6tbav0wux5n.jpg"  alt="تبلیغات">

    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 434, Column 6: start tag was here
    					<img src="http://www.farskids320.com/wp-content/uploads/2012/07/upywoulw6t…
  • Error Line 441, Column 110: end tag for "img" omitted, but OMITTAG NO was specified
    …kids320.com/wp-content/uploads/2012/07/upywoulw6tbav0wux5n.jpg"  alt="تبلیغات">

    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 441, Column 6: start tag was here
    					<img src="http://www.farskids320.com/wp-content/uploads/2012/07/upywoulw6t…
  • Error Line 450, Column 59: end tag for "br" omitted, but OMITTAG NO was specified
    کلیه حقوق مادی و معنوی برای فارس کیدذ محفوظ می باشد . <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 450, Column 55: start tag was here
    کلیه حقوق مادی و معنوی برای فارس کیدذ محفوظ می باشد . <br>
  • Error Line 457, Column 176: end tag for "img" omitted, but OMITTAG NO was specified
    …mes/farskids-seo-v1/images/sw.png" width="56" height="56" alt="گروه طراحی"></a>

    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 457, Column 47: start tag was here
    …ref="" rel="nofollow" target="_blank"><img src="http://www.farskids320.com/wp-…
  • Error Line 469, Column 30: required attribute "type" not specified
    <script language="Javascript">

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

Visitor Analysis

Daily Visitor
  • 105 visits