suong.vn

Website chính thức của BomChat, ứng dụng nhắn tin & gọi điện HD miễn phí, ứng dụng OTT đầu tiên trên thế giới cho phép cài đặt nhạc chờ cuộc gọi, nhạc nền ...
Last updated from 25-10-2014 01:42:49 

Overview Info

  • Domain Name
    suong.vn
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    0
  • Ip Address
    123.30.214.108
  • Page Size
    8 KB
  • Images
    0 GIF, 0 JPG, 9 PNG
Heading
H1H2H3H4H5H6
0 0 0 0 0 0

Website Meta Analysis

  • Title
    BomChat - Gọi điện HD miễn phí - Kết bạn cực đã
  • Meta Keyword
    bomchat, boomchat, bomchatapp
  • Meta Description
    Website chính thức của BomChat, ứng dụng nhắn tin & gọi điện HD miễn phí, ứng dụng OTT đầu tiên trên thế giới cho phép cài đặt nhạc chờ cuộc gọi, nhạc nền cuộc gọi, chữ ký cuộc gọi
Advertisement

Technical Analysis

  • Webserver
    Apache/2.4.9 (Unix) PHP/5.5.12
  • Ip Address
    123.30.214.108
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sat, 25 Oct 2014 01:38:26 GMT
  • server: Apache/2.4.9 (Unix) PHP/5.5.12
  • x-powered-by: Borua Framework
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-length: 7795
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

No data whois for suong.vn

IP 123.30.214.108 Analysis

  • Country Name
    Viet Nam
  • City
  • Latitude
    19.75
  • Longitude
    105.32
  • IP Address Country Region City ISP
    123.30.214.108 Viet Nam Thang Vietnam Data Communication Company Vdc
      Continent Latitude Longitude Time Zone
      Asia 19.75 105.32 GMT+7

Site Same Ip

Traffic Analysis

Magestic Backlinks


Daily Ranks

Rank Trend

Visitor Trend

Bounce Trend

HTML Analysis

HTML validation

  • 45 Errors
  • 19 Warnings

Ratio Text/Html

  • 0.5655339805825244

Message Error

  • Error Line 8, Column 16: there is no attribute "property"
    <meta property="og:image" content="http://static.onchat.vn/image/BomChat_icon_A…

    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.

  • Warning Line 10, Column 85: character "&" is the first character of a delimiter but occurred as data
    …h thức của BomChat, ứng dụng nhắn tin & gọi điện HD miễn phí, ứng dụng OTT đầu…

    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 22, Column 91: required attribute "alt" not specified
    …<a href="/"><img src="http://static.onchat.vn/image/onChat_icon.png"></a></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 22, Column 95: end tag for "img" omitted, but OMITTAG NO was specified
    …<a href="/"><img src="http://static.onchat.vn/image/onChat_icon.png"></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 22, Column 35: start tag was here
    				<div class="logo"><a href="/"><img src="http://static.onchat.vn/image/onCha…
  • Warning Line 53, Column 84: cannot generate system identifier for general entity "autohide"
    …w.youtube.com/embed/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080" framebo…

    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 53, Column 84: general entity "autohide" not defined and no default entity
    …w.youtube.com/embed/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080" framebo…

    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 53, Column 92: reference not terminated by REFC delimiter
    …e.com/embed/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080" frameborder="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 53, Column 92: reference to external entity in attribute value
    …e.com/embed/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080" frameborder="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 53, Column 92: reference to entity "autohide" for which no system identifier could be generated
    …e.com/embed/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080" frameborder="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 53, Column 83: entity was defined here
    …ww.youtube.com/embed/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080" frameb…
  • Warning Line 53, Column 95: cannot generate system identifier for general entity "showinfo"
    …om/embed/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080" frameborder="0" al…

    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 53, Column 95: general entity "showinfo" not defined and no default entity
    …om/embed/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080" frameborder="0" al…

    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 53, Column 103: reference not terminated by REFC delimiter
    …/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080" frameborder="0" allowfulls…

    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 53, Column 103: reference to external entity in attribute value
    …/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080" frameborder="0" allowfulls…

    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 53, Column 103: reference to entity "showinfo" for which no system identifier could be generated
    …/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080" frameborder="0" allowfulls…

    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 53, Column 94: entity was defined here
    …com/embed/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080" frameborder="0" a…
  • Warning Line 53, Column 106: cannot generate system identifier for general entity "vq"
    …i2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080" frameborder="0" allowfullscre…

    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 53, Column 106: general entity "vq" not defined and no default entity
    …i2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080" frameborder="0" allowfullscre…

    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 53, Column 108: reference not terminated by REFC delimiter
    …kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080" frameborder="0" allowfullscreen…

    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 53, Column 108: reference to external entity in attribute value
    …kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080" frameborder="0" allowfullscreen…

    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 53, Column 108: reference to entity "vq" for which no system identifier could be generated
    …kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080" frameborder="0" allowfullscreen…

    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 53, Column 105: entity was defined here
    …Mi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080" frameborder="0" allowfullscr…
  • Error Line 53, Column 148: "allowfullscreen" is not a member of a group specified for any attribute
    …el=0&autohide=1&showinfo=0&vq=hd1080" frameborder="0" allowfullscreen></iframe>
  • Warning Line 56, Column 68: reference not terminated by REFC delimiter
    …ttp://www.youtube.com/embed/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080">

    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 56, Column 68: reference to external entity in attribute value
    …ttp://www.youtube.com/embed/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080">

    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 56, Column 68: reference to entity "autohide" for which no system identifier could be generated
    …ttp://www.youtube.com/embed/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080">

    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 53, Column 83: entity was defined here
    …ww.youtube.com/embed/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080" frameb…
  • Warning Line 56, Column 79: reference not terminated by REFC delimiter
    …ttp://www.youtube.com/embed/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080">

    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 56, Column 79: reference to external entity in attribute value
    …ttp://www.youtube.com/embed/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080">

    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 56, Column 79: reference to entity "showinfo" for which no system identifier could be generated
    …ttp://www.youtube.com/embed/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080">

    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 53, Column 94: entity was defined here
    …com/embed/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080" frameborder="0" a…
  • Warning Line 56, Column 84: reference not terminated by REFC delimiter
    …ttp://www.youtube.com/embed/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080">

    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 56, Column 84: reference to external entity in attribute value
    …ttp://www.youtube.com/embed/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080">

    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 56, Column 84: reference to entity "vq" for which no system identifier could be generated
    …ttp://www.youtube.com/embed/OMi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080">

    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 53, Column 105: entity was defined here
    …Mi2kzV87Ik?rel=0&autohide=1&showinfo=0&vq=hd1080" frameborder="0" allowfullscr…
  • Error Line 68, Column 116: end tag for "br" omitted, but OMITTAG NO was specified
    …#434343;padding-bottom: 20px;">Gọi điện chất lượng cao <br><br>(HD voice)</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 68, Column 112: start tag was here
    …#434343;padding-bottom: 20px;">Gọi điện chất lượng cao <br><br>(HD voice)</div>
  • Error Line 68, Column 120: end tag for "br" omitted, but OMITTAG NO was specified
    …#434343;padding-bottom: 20px;">Gọi điện chất lượng cao <br><br>(HD voice)</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 68, Column 116: start tag was here
    …#434343;padding-bottom: 20px;">Gọi điện chất lượng cao <br><br>(HD voice)</div>
  • Error Line 78, Column 73: required attribute "alt" not specified
    	<div class="phone1"><img src="http://static.onchat.vn/image/call-2.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 78, Column 79: end tag for "img" omitted, but OMITTAG NO was specified
    	<div class="phone1"><img src="http://static.onchat.vn/image/call-2.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 78, Column 22: start tag was here
    	<div class="phone1"><img src="http://static.onchat.vn/image/call-2.png"></div>
  • Error Line 79, Column 20: end tag for "br" omitted, but OMITTAG NO was specified
    	<br class="clear">

    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 79, Column 2: start tag was here
    	<br class="clear">
  • Error Line 86, Column 20: end tag for "br" omitted, but OMITTAG NO was specified
    	<br class="clear">

    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 86, Column 2: start tag was here
    	<br class="clear">
  • Error Line 91, Column 84: required attribute "alt" not specified
    …="/bgmusic/upload"><img src="http://static.onchat.vn/image/create-rbt.png"></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 91, Column 88: end tag for "img" omitted, but OMITTAG NO was specified
    …="/bgmusic/upload"><img src="http://static.onchat.vn/image/create-rbt.png"></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 91, Column 29: start tag was here
    		<a href="/bgmusic/upload"><img src="http://static.onchat.vn/image/create-rbt.…
  • Warning Line 94, Column 89: cannot generate system identifier for general entity "mt"
    …-goi-ien-hd-mien-phi/id894379951?ls=1&mt=8"><img src="http://static.onchat.vn/…

    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 94, Column 89: general entity "mt" not defined and no default entity
    …-goi-ien-hd-mien-phi/id894379951?ls=1&mt=8"><img src="http://static.onchat.vn/…

    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 94, Column 91: reference not terminated by REFC delimiter
    …oi-ien-hd-mien-phi/id894379951?ls=1&mt=8"><img src="http://static.onchat.vn/im…

    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 94, Column 91: reference to external entity in attribute value
    …oi-ien-hd-mien-phi/id894379951?ls=1&mt=8"><img src="http://static.onchat.vn/im…

    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 94, Column 91: reference to entity "mt" for which no system identifier could be generated
    …oi-ien-hd-mien-phi/id894379951?ls=1&mt=8"><img src="http://static.onchat.vn/im…

    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 94, Column 88: entity was defined here
    …t-goi-ien-hd-mien-phi/id894379951?ls=1&mt=8"><img src="http://static.onchat.vn…
  • Error Line 94, Column 145: required attribute "alt" not specified
    …/id894379951?ls=1&mt=8"><img src="http://static.onchat.vn/image/ios-2.png"></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 94, Column 149: end tag for "img" omitted, but OMITTAG NO was specified
    …/id894379951?ls=1&mt=8"><img src="http://static.onchat.vn/image/ios-2.png"></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 94, Column 95: start tag was here
    …en-hd-mien-phi/id894379951?ls=1&mt=8"><img src="http://static.onchat.vn/image/…
  • Error Line 96, Column 159: required attribute "alt" not specified
    …=com.bomchat"><img src="http://static.onchat.vn/image/android-2.png"></a></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 96, Column 163: end tag for "img" omitted, but OMITTAG NO was specified
    …=com.bomchat"><img src="http://static.onchat.vn/image/android-2.png"></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 96, Column 105: start tag was here
    …om/store/apps/details?id=com.bomchat"><img src="http://static.onchat.vn/image/…
  • Error Line 97, Column 20: end tag for "br" omitted, but OMITTAG NO was specified
    	<br class="clear">

    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 97, Column 2: start tag was here
    	<br class="clear">
  • Error Line 103, Column 72: required attribute "alt" not specified
    		<div class="cont02im"><img src="http://static.onchat.vn/image/s1.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 103, Column 78: end tag for "img" omitted, but OMITTAG NO was specified
    		<div class="cont02im"><img src="http://static.onchat.vn/image/s1.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 103, Column 25: start tag was here
    		<div class="cont02im"><img src="http://static.onchat.vn/image/s1.png"></div>
  • Error Line 111, Column 38: end tag for "br" omitted, but OMITTAG NO was specified
    				<li>Gửi ảnh tự vẽ cực chất :)<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 111, Column 34: start tag was here
    				<li>Gửi ảnh tự vẽ cực chất :)<br>
  • Error Line 115, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
    		<br class="clear">

    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 115, Column 3: start tag was here
    		<br class="clear">
  • Error Line 117, Column 20: end tag for "br" omitted, but OMITTAG NO was specified
    	<br class="clear">

    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 117, Column 2: start tag was here
    	<br class="clear">
  • Error Line 123, Column 51: required attribute "alt" not specified
    			<img src="http://static.onchat.vn/image/s2.png">

    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 123, Column 52: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="http://static.onchat.vn/image/s2.png">

    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 123, Column 4: start tag was here
    			<img src="http://static.onchat.vn/image/s2.png">
  • Error Line 133, Column 57: end tag for "br" omitted, but OMITTAG NO was specified
    				<li>Tùy chọn thiết lập riêng tư, bảo mật mạnh mẽ<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 133, Column 53: start tag was here
    				<li>Tùy chọn thiết lập riêng tư, bảo mật mạnh mẽ<br>
  • Error Line 137, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
    		<br class="clear">

    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 137, Column 3: start tag was here
    		<br class="clear">
  • Error Line 139, Column 20: end tag for "br" omitted, but OMITTAG NO was specified
    	<br class="clear">

    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 139, Column 2: start tag was here
    	<br class="clear">
  • Error Line 144, Column 72: required attribute "alt" not specified
    		<div class="cont02im"><img src="http://static.onchat.vn/image/s3.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 144, Column 78: end tag for "img" omitted, but OMITTAG NO was specified
    		<div class="cont02im"><img src="http://static.onchat.vn/image/s3.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 144, Column 25: start tag was here
    		<div class="cont02im"><img src="http://static.onchat.vn/image/s3.png"></div>
  • Error Line 150, Column 158: end tag for "br" omitted, but OMITTAG NO was specified
    …mọi người xem trang cá nhân, nhắn tin, gọi điện cho bạn để tránh sự rắc rối<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 150, Column 154: start tag was here
    …mọi người xem trang cá nhân, nhắn tin, gọi điện cho bạn để tránh sự rắc rối<br>
  • Error Line 154, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
    		<br class="clear">

    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 154, Column 3: start tag was here
    		<br class="clear">
  • Error Line 156, Column 20: end tag for "br" omitted, but OMITTAG NO was specified
    	<br class="clear">

    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 156, Column 2: start tag was here
    	<br class="clear">
  • Error Line 158, Column 22: end tag for "br" omitted, but OMITTAG NO was specified
    			<br class="clear">

    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 158, Column 4: start tag was here
    			<br class="clear">
  • Error Line 169, Column 8: 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>.

Visitor Analysis

In Page Analysis