Watch free Chinese series and movies, Thai Lakorn drama and movies, Korean drama, Khmer drama and movies, Khmer CTN comedy, Khmer karaoke, MP3 and much more! ...

video4khmer.com
  • Domain Name
    video4khmer.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #24553
  • Page Size
    32.8 KB
  • Ip Address
    192.185.52.147
  • Heading
    H1: 0, H2: 0, H3: 4, H4: 0, H5: 0, H6: 0
  • Images
    12 GIF, 21 JPG, 2 PNG

Website Meta Analysis

  • Title
    KHVDO.com - Movie Khmer - Khmer Movie - Khmer Dubbed, Chinese Series, Thai Lakorn, Drama Khmer
  • Meta Keyword
    Khmer Movies, Khmer Chinese drama, Khmer Thai lakhorn, Khmer Chinese movie, Khmer Korean drama, Khmer Thai movie, Khmer comedy, neay peakmi, neay koy, Prum Manh, Ayai, latest Khmer movies, Khmer drama, TV series, Khmer video karaoke, khmer music video, Khmer dubbed, Hang Meas Production, BigMan Production, M Production, Sunday Production, Town Production, Rock Production, Classic Production, Blue Diamond Production, SSB Production, Cambodia video music karaoke
  • Meta Description
    Watch free Chinese series and movies, Thai Lakorn drama and movies, Korean drama, Khmer drama and movies, Khmer CTN comedy, Khmer karaoke, MP3 and much more!

Technical Analysis

  • Webserver
    cloudflare-nginx
  • Ip Address
    192.185.52.147
  • Domain Age
    1 Years, 11 Months, 4 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: cloudflare-nginx
  • date: Fri, 11 Oct 2013 03:12:13 GMT
  • content-type: text/html
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-powered-by: PHP/5.3.26
  • cf-ray: bb85e1612ee020d
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: VIDEO4KHMER.COM
Created on: 17-Oct-11
Expires on: 17-Oct-14
Last Updated on: 13-Mar-12

Registrant:
Video4Khmer
No.19B
Street 103R
Tuol Sangke, Phnom Penh 11111
Cambodia

Administrative Contact:
ForKhmer, Video email
Video4Khmer
No.19B
Street 103R
Tuol Sangke, Phnom Penh 11111
Cambodia
+855.12678345

Technical Contact:
ForKhmer, Video email
Video4Khmer
No.19B
Street 103R
Tuol Sangke, Phnom Penh 11111
Cambodia
+855.12678345

Domain servers in listed order:
NS191.HOSTGATOR.COM
NS192.HOSTGATOR.COM

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 35 Errors
  • 9 Warnings
Ratio Text/Html
  • 0.76563986679353
Message Error
  • Error Line 8, Column 81: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="shortcut icon" href="http://www.video4khmer.com/uploads/favicon.ico">

    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 8, Column 1: start tag was here
    <link rel="shortcut icon" href="http://www.video4khmer.com/uploads/favicon.ico">
  • Error Line 87, Column 173: required attribute "alt" not specified
    …/templates/3column/images/header/logo-original.png" style="border:none;" /></a>

    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 88, Column 173: required attribute "alt" not specified
    …/templates/3column/images/header/desc-black-01.gif" style="border:none;" /></a>

    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 92, Column 156: required attribute "alt" not specified
    …com/templates/3column/images/header/mp3_header.gif"  style="border:none; "></a>

    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 92, Column 160: end tag for "img" omitted, but OMITTAG NO was specified
    …com/templates/3column/images/header/mp3_header.gif"  style="border:none; "></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 92, Column 49: start tag was here
    …href="http://www.video4khmer.com/mp3"><img src="http://www.video4khmer.com/tem…
  • Error Line 116, Column 154: there is no attribute "autocomplete"
    …String" onkeyup="lookup(this.value);" onblur="fill();" autocomplete="off"  />  

    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 290, Column 295: required attribute "alt" not specified
    …e="Khmer Joke"  width="333" height="90" style="border:none; " /></a></div></td>

    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 302, Column 308: required attribute "alt" not specified
    …f" title="Khmer Joke"  width="190" height="90" style="border:none;" /></a></td>

    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 314, Column 9: character "<" is the first character of a delimiter but occurred as data
            <! 

    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 352, Column 89: cannot generate system identifier for general entity "aID"
    …=62959826-ff0d-4bac-9a9c-fb8bf6bb1798&aID=62859&cID=55c636e3-97cf-413b-9550-b0…

    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 352, Column 89: general entity "aID" not defined and no default entity
    …=62959826-ff0d-4bac-9a9c-fb8bf6bb1798&aID=62859&cID=55c636e3-97cf-413b-9550-b0…

    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 352, Column 92: reference not terminated by REFC delimiter
    …959826-ff0d-4bac-9a9c-fb8bf6bb1798&aID=62859&cID=55c636e3-97cf-413b-9550-b0e3f…

    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 352, Column 92: reference to external entity in attribute value
    …959826-ff0d-4bac-9a9c-fb8bf6bb1798&aID=62859&cID=55c636e3-97cf-413b-9550-b0e3f…

    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 352, Column 92: reference to entity "aID" for which no system identifier could be generated
    …959826-ff0d-4bac-9a9c-fb8bf6bb1798&aID=62859&cID=55c636e3-97cf-413b-9550-b0e3f…

    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 352, Column 88: entity was defined here
    …D=62959826-ff0d-4bac-9a9c-fb8bf6bb1798&aID=62859&cID=55c636e3-97cf-413b-9550-b…
  • Warning Line 352, Column 99: cannot generate system identifier for general entity "cID"
    …ff0d-4bac-9a9c-fb8bf6bb1798&aID=62859&cID=55c636e3-97cf-413b-9550-b0e3f8c54c20…

    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 352, Column 99: general entity "cID" not defined and no default entity
    …ff0d-4bac-9a9c-fb8bf6bb1798&aID=62859&cID=55c636e3-97cf-413b-9550-b0e3f8c54c20…

    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 352, Column 102: reference not terminated by REFC delimiter
    …d-4bac-9a9c-fb8bf6bb1798&aID=62859&cID=55c636e3-97cf-413b-9550-b0e3f8c54c20' t…

    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 352, Column 102: reference to external entity in attribute value
    …d-4bac-9a9c-fb8bf6bb1798&aID=62859&cID=55c636e3-97cf-413b-9550-b0e3f8c54c20' t…

    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 352, Column 102: reference to entity "cID" for which no system identifier could be generated
    …d-4bac-9a9c-fb8bf6bb1798&aID=62859&cID=55c636e3-97cf-413b-9550-b0e3f8c54c20' t…

    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 352, Column 98: entity was defined here
    …-ff0d-4bac-9a9c-fb8bf6bb1798&aID=62859&cID=55c636e3-97cf-413b-9550-b0e3f8c54c2…
  • Warning Line 352, Column 245: cannot generate system identifier for general entity "id"
    …=62959826-ff0d-4bac-9a9c-fb8bf6bb1798&id=55c636e3-97cf-413b-9550-b0e3f8c54c20'…

    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 352, Column 245: general entity "id" not defined and no default entity
    …=62959826-ff0d-4bac-9a9c-fb8bf6bb1798&id=55c636e3-97cf-413b-9550-b0e3f8c54c20'…

    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 352, Column 247: reference not terminated by REFC delimiter
    …2959826-ff0d-4bac-9a9c-fb8bf6bb1798&id=55c636e3-97cf-413b-9550-b0e3f8c54c20' b…

    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 352, Column 247: reference to external entity in attribute value
    …2959826-ff0d-4bac-9a9c-fb8bf6bb1798&id=55c636e3-97cf-413b-9550-b0e3f8c54c20' b…

    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 352, Column 247: reference to entity "id" for which no system identifier could be generated
    …2959826-ff0d-4bac-9a9c-fb8bf6bb1798&id=55c636e3-97cf-413b-9550-b0e3f8c54c20' b…

    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 352, Column 244: entity was defined here
    …D=62959826-ff0d-4bac-9a9c-fb8bf6bb1798&id=55c636e3-97cf-413b-9550-b0e3f8c54c20…
  • Error Line 352, Column 296: required attribute "alt" not specified
    …4bac-9a9c-fb8bf6bb1798&id=55c636e3-97cf-413b-9550-b0e3f8c54c20' border='0'></a>

    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 352, Column 300: end tag for "img" omitted, but OMITTAG NO was specified
    …4bac-9a9c-fb8bf6bb1798&id=55c636e3-97cf-413b-9550-b0e3f8c54c20' border='0'></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 352, Column 157: start tag was here
    …3b-9550-b0e3f8c54c20' target='_blank'><img src='http://adv.36bol.com/Collatera…
  • Warning Line 356, Column 92: reference not terminated by REFC delimiter
    …51ef89-ee56-4913-83ef-0df32403d1c3&aID=71148&cID=7dc9fd08-9c92-49d9-be68-73573…

    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 356, Column 92: reference to external entity in attribute value
    …51ef89-ee56-4913-83ef-0df32403d1c3&aID=71148&cID=7dc9fd08-9c92-49d9-be68-73573…

    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 356, Column 92: reference to entity "aID" for which no system identifier could be generated
    …51ef89-ee56-4913-83ef-0df32403d1c3&aID=71148&cID=7dc9fd08-9c92-49d9-be68-73573…

    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 352, Column 88: entity was defined here
    …D=62959826-ff0d-4bac-9a9c-fb8bf6bb1798&aID=62859&cID=55c636e3-97cf-413b-9550-b…
  • Warning Line 356, Column 102: reference not terminated by REFC delimiter
    …6-4913-83ef-0df32403d1c3&aID=71148&cID=7dc9fd08-9c92-49d9-be68-73573eb88614' t…

    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 356, Column 102: reference to external entity in attribute value
    …6-4913-83ef-0df32403d1c3&aID=71148&cID=7dc9fd08-9c92-49d9-be68-73573eb88614' t…

    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 356, Column 102: reference to entity "cID" for which no system identifier could be generated
    …6-4913-83ef-0df32403d1c3&aID=71148&cID=7dc9fd08-9c92-49d9-be68-73573eb88614' t…

    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 352, Column 98: entity was defined here
    …-ff0d-4bac-9a9c-fb8bf6bb1798&aID=62859&cID=55c636e3-97cf-413b-9550-b0e3f8c54c2…
  • Warning Line 356, Column 247: reference not terminated by REFC delimiter
    …051ef89-ee56-4913-83ef-0df32403d1c3&id=7dc9fd08-9c92-49d9-be68-73573eb88614' b…

    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 356, Column 247: reference to external entity in attribute value
    …051ef89-ee56-4913-83ef-0df32403d1c3&id=7dc9fd08-9c92-49d9-be68-73573eb88614' b…

    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 356, Column 247: reference to entity "id" for which no system identifier could be generated
    …051ef89-ee56-4913-83ef-0df32403d1c3&id=7dc9fd08-9c92-49d9-be68-73573eb88614' b…

    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 352, Column 244: entity was defined here
    …D=62959826-ff0d-4bac-9a9c-fb8bf6bb1798&id=55c636e3-97cf-413b-9550-b0e3f8c54c20…
  • Error Line 356, Column 296: required attribute "alt" not specified
    …4913-83ef-0df32403d1c3&id=7dc9fd08-9c92-49d9-be68-73573eb88614' border='0'></a>

    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 356, Column 300: end tag for "img" omitted, but OMITTAG NO was specified
    …4913-83ef-0df32403d1c3&id=7dc9fd08-9c92-49d9-be68-73573eb88614' border='0'></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 356, Column 157: start tag was here
    …d9-be68-73573eb88614' target='_blank'><img src='http://adv.m88sb.com/Collatera…
  • Error Line 362, Column 182: required attribute "alt" not specified
    …o4khmer.com/templates/3column/images/left/cambodiawindow.png" border="0" /></a>

    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 367, Column 115: required attribute "alt" not specified
    …c="http://www.video4khmer.com/templates/3column/images/left/our_ad.png" ></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 367, Column 121: end tag for "img" omitted, but OMITTAG NO was specified
    …c="http://www.video4khmer.com/templates/3column/images/left/our_ad.png" ></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 367, Column 36: start tag was here
    							 <div class="block_content"><img src="http://www.video4khmer.com/templat…
  • Error Line 372, Column 115: required attribute "alt" not specified
    ….com/templates/3column/images/right/khmernow_right.gif" style="border:none; "/>

    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 378, Column 26: ID "reg_box" already defined
    						 									<div id="reg_box">	  <h3 class="captions">Tags</h3>	  

    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 361, Column 70: ID "reg_box" first defined here
    …bar"><div class="block_content">	<div id="reg_box" style="text-align:center; ">
  • Error Line 461, Column 174: required attribute "alt" not specified
    …ates/3column/images/right/fb_like_below_325.gif" style="border:none; "><br />		

    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 461, Column 175: end tag for "img" omitted, but OMITTAG NO was specified
    …ates/3column/images/right/fb_like_below_325.gif" style="border:none; "><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 461, Column 62: start tag was here
    …lign:left; background-color:#FFFFFF;"><img src="http://www.video4khmer.com/tem…
  • Error Line 463, Column 13: required attribute "type" not specified
    					<script>(function(d, s, id) {  var js, fjs = d.getElementsByTagName(s)[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 464, Column 41: there is no attribute "data-href"
    …			<div class="fb-like-box" data-href="http://www.facebook.com/pages/Video-4-K…

    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 464, Column 114: there is no attribute "data-width"
    …o-4-Khmer/327098180637933" data-width="320" data-height="260" 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 464, Column 132: there is no attribute "data-height"
    …0637933" data-width="320" data-height="260" data-show-faces="true" data-stream…

    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 464, Column 154: there is no attribute "data-show-faces"
    …20" data-height="260" data-show-faces="true" 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 464, Column 173: there is no attribute "data-stream"
    …0" data-show-faces="true" data-stream="false" data-header="false"></div>	</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 464, Column 193: there is no attribute "data-header"
    …" data-show-faces="true" data-stream="false" data-header="false"></div>	</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 474, Column 82: required attribute "alt" not specified
    …class="imag" src="http://www.video4khmer.com/images/subcat/506/2477.jpg" /></a>

    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 478, Column 82: required attribute "alt" not specified
    …class="imag" src="http://www.video4khmer.com/images/subcat/506/2451.jpg" /></a>

    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 640, Column 259: character "&" is the first character of a delimiter but occurred as data
    …08.2012 (Arrest 4 tons Narcotic Drugs & Other significant news of the day)" cl…

    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 642, Column 210: character "&" is the first character of a delimiter but occurred as data
    …08.2012 (Arrest 4 tons Narcotic Drugs & Other significant news of the day)">CT…

    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 667, Column 276: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …height:250px; margin-left:7px;' class=imag src=http://www.video4khmer.com/imag…
  • Error Line 667, Column 285: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …0px; margin-left:7px;' class=imag src=http://www.video4khmer.com/images/subcat…
  • Error Line 667, Column 291: NET-enabling start-tag not immediately followed by null end-tag
    …argin-left:7px;' class=imag src=http://www.video4khmer.com/images/subcat/510/1…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 667, Column 291: required attribute "alt" not specified
    …argin-left:7px;' class=imag src=http://www.video4khmer.com/images/subcat/510/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 667, Column 291: end tag for "img" omitted, but OMITTAG NO was specified
    …argin-left:7px;' class=imag src=http://www.video4khmer.com/images/subcat/510/1…

    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 667, Column 213: start tag was here
    …com/browse-VCD110-videos-1-date.html"><img style='width:230px; height:250px; m…
  • Error Line 667, Column 751: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …height:250px; margin-left:7px;' class=imag src=http://www.video4khmer.com/imag…
  • Error Line 667, Column 760: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …0px; margin-left:7px;' class=imag src=http://www.video4khmer.com/images/subcat…
  • Error Line 667, Column 766: NET-enabling start-tag not immediately followed by null end-tag
    …argin-left:7px;' class=imag src=http://www.video4khmer.com/images/subcat/505/1…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 667, Column 766: required attribute "alt" not specified
    …argin-left:7px;' class=imag src=http://www.video4khmer.com/images/subcat/505/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 667, Column 766: end tag for "img" omitted, but OMITTAG NO was specified
    …argin-left:7px;' class=imag src=http://www.video4khmer.com/images/subcat/505/1…

    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 667, Column 688: start tag was here
    …ovie-khmer-dubbed-videos-1-date.html"><img style='width:230px; height:250px; m…
  • Error Line 708, Column 18: required attribute "type" not specified
    										<script>var _wau = _wau || []; _wau.push(["tab", "n2s6uwhq9zpt", "qx6…

    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 732, Column 10: end tag for element "div" which is not open
        </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

Visitor Analysis

Daily Visitor
  • 6.767 visits