youtube-converter-mp3.com

Youtube Converter Mp3 Telecharger et Convertir les videos directement de Youtube, Google, Metacafe et plus. Un Simple copier et coller. ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    youtube-converter-mp3.com
  • Favicon
  • Alexa Rank
    #8646449
  • Google Page Rank
    PR 0
  • Ip Address
    196.203.83.249
  • Page Size
    5.7 KB
  • Images
    0 GIF, 0 JPG, 6 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 1 3 0 0 0

Website Meta Analysis



  • Title
    Youtube Converter Mp3
  • Meta Keyword
    Youtube Converter Mp3,convert , youtube to mo3 , save, video, stream, youtube, yuotube, toutube, uoutube, houtube
  • Meta Description
    Youtube Converter Mp3 Telecharger et Convertir les videos directement de Youtube, Google, Metacafe et plus. Un Simple copier et coller.

Technical Analysis



  • Webserver
    Apache
  • Ip Address
    196.203.83.249
  • Domain Age
    5 Months, 12 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from youtube-converter-mp3.com.

HTML Analysis

  • date: Tue, 23 Jul 2013 23:27:54 GMT
  • server: Apache
  • x-powered-by: PHP/5.4.16
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • content-length: 2329
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for youtube-converter-mp3.com

IP 196.203.83.249 Analysis

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 8 Errors
  • 8 Warnings
Ratio Text/Html
  • 0.5890740422607799
Message Error
  • Warning Line 9, Column 180: NET-enabling start-tag requires SHORTTAG YES
    …rectement de Youtube, Google, Metacafe et plus. Un Simple copier et coller." />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 9, Column 181: character data is not allowed here
    …rectement de Youtube, Google, Metacafe et plus. Un Simple copier et coller." />

    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.
  • Warning Line 10, Column 154: NET-enabling start-tag requires SHORTTAG YES
    … to mo3 ,  save, video, stream, youtube, yuotube, toutube, uoutube, houtube" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 40, Column 53: required attribute "TYPE" not specified
    <script src="http://platform.twitter.com/widgets.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 45, Column 19: there is no attribute "LANGUAGE"
    	<script language="javascript">

    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 45, Column 31: 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>.

  • Error Line 62, Column 31: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
                    <div id="logo">

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

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

  • Warning Line 69, Column 89: NET-enabling start-tag requires SHORTTAG YES
    … <a class="addinto_button_email"><img src="/imgs/eemail.png" alt="Email" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 70, Column 98: NET-enabling start-tag requires SHORTTAG YES
    …="addinto_button_facebook"><img src="/imgs/efacebook.png" alt="Facebook" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 71, Column 95: NET-enabling start-tag requires SHORTTAG YES
    …ass="addinto_button_twitter"><img src="/imgs/etwitter.png" alt="Twitter" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 72, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …ddinto_button_delicious"><img src="/imgs/edelicious.png" alt="Delicious" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 73, Column 103: NET-enabling start-tag requires SHORTTAG YES
    …into_button_google_plus"><img src="/imgs/egoogle_plus.png" alt="Google+" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 74, Column 94: NET-enabling start-tag requires SHORTTAG YES
    …lass="addinto_button_more_dd"><img src="/imgs/eai2_32x32.png" alt="More" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 94, Column 148: cannot generate system identifier for general entity "h"
    …WYKOpmI1jcZaNnnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=728&h=90&target=_blank"></script>

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 94, Column 148: general entity "h" not defined and no default entity
    …WYKOpmI1jcZaNnnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=728&h=90&target=_blank"></script>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Error Line 94, Column 149: reference to entity "h" for which no system identifier could be generated
    …WYKOpmI1jcZaNnnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=728&h=90&target=_blank"></script>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 94, Column 147: entity was defined here
    …WYKOpmI1jcZaNnnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=728&h=90&target=_blank"></script>
  • Warning Line 94, Column 153: cannot generate system identifier for general entity "target"
    …WYKOpmI1jcZaNnnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=728&h=90&target=_blank"></script>

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 94, Column 153: general entity "target" not defined and no default entity
    …WYKOpmI1jcZaNnnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=728&h=90&target=_blank"></script>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Error Line 94, Column 159: reference to entity "target" for which no system identifier could be generated
    …WYKOpmI1jcZaNnnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=728&h=90&target=_blank"></script>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 94, Column 152: entity was defined here
    …WYKOpmI1jcZaNnnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=728&h=90&target=_blank"></script>
  • Error Line 95, Column 29: there is no attribute "SCROLLING"
    <noscript><iframe scrolling="no" frameborder="0" border="0" style="overflow:hid…

    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 95, Column 46: there is no attribute "FRAMEBORDER"
    …pt><iframe scrolling="no" frameborder="0" border="0" style="overflow:hidden; b…

    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 95, Column 57: there is no attribute "BORDER"
    …scrolling="no" frameborder="0" border="0" style="overflow:hidden; border:0px" …

    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 95, Column 67: there is no attribute "STYLE"
    …"no" frameborder="0" border="0" style="overflow:hidden; border:0px" width="728…

    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 95, Column 103: there is no attribute "WIDTH"
    …e="overflow:hidden; border:0px" width="728"  height="90" src="http://network.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.

  • Error Line 95, Column 117: there is no attribute "HEIGHT"
    …dden; border:0px" width="728"  height="90" src="http://network.adsmarket.com/c…

    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 95, Column 126: there is no attribute "SRC"
    …der:0px" width="728"  height="90" src="http://network.adsmarket.com/ceas/2/2/2…

    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 95, Column 233: reference to entity "h" for which no system identifier could be generated
    …NnnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=728&h=90&target=_blank" ></iframe></noscript>

    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 147: entity was defined here
    …WYKOpmI1jcZaNnnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=728&h=90&target=_blank"></script>
  • Error Line 95, Column 243: reference to entity "target" for which no system identifier could be generated
    …NnnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=728&h=90&target=_blank" ></iframe></noscript>

    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 152: entity was defined here
    …WYKOpmI1jcZaNnnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=728&h=90&target=_blank"></script>
  • Error Line 95, Column 252: element "IFRAME" undefined
    …NnnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=728&h=90&target=_blank" ></iframe></noscript>

    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 95, Column 272: end tag for "NOSCRIPT" which is not finished
    …NnnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=728&h=90&target=_blank" ></iframe></noscript>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 104, Column 167: document type does not allow element "INPUT" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
    … la video ..." onclick="if(this.value == 'Enter Video URL ...')this.value='';">

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

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

  • Error Line 106, Column 91: document type does not allow element "A" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
    …                    <a href="#" onclick="document.forms['download'].submit();">

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

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

  • Error Line 110, Column 35: end tag for "FORM" which is not finished
                                </form>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 115, Column 17: ID "JAVA-REQUIRED" already defined
    						 <div id="java-required">

    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 112, Column 34: ID "JAVA-REQUIRED" first defined here
                            <div id="java-required">
  • Error Line 116, Column 143: reference to entity "h" for which no system identifier could be generated
    …YKOpmI1jcZaNnnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=800&h=440&target=_blank"></script>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 94, Column 147: entity was defined here
    …WYKOpmI1jcZaNnnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=728&h=90&target=_blank"></script>
  • Error Line 116, Column 154: reference to entity "target" for which no system identifier could be generated
    …YKOpmI1jcZaNnnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=800&h=440&target=_blank"></script>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 94, Column 152: entity was defined here
    …WYKOpmI1jcZaNnnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=728&h=90&target=_blank"></script>
  • Error Line 117, Column 234: reference to entity "h" for which no system identifier could be generated
    …nnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=800&h=440&target=_blank" ></iframe></noscript…

    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 147: entity was defined here
    …WYKOpmI1jcZaNnnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=728&h=90&target=_blank"></script>
  • Error Line 117, Column 245: reference to entity "target" for which no system identifier could be generated
    …nnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=800&h=440&target=_blank" ></iframe></noscript>

    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 152: entity was defined here
    …WYKOpmI1jcZaNnnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=728&h=90&target=_blank"></script>
  • Error Line 117, Column 254: element "IFRAME" undefined
    …nnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=800&h=440&target=_blank" ></iframe></noscript>

    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 117, Column 274: end tag for "NOSCRIPT" which is not finished
    …nnqUimpqxGKif5uOYpiYZZ59mImQaQ?w=800&h=440&target=_blank" ></iframe></noscript>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

Visitor Analysis

Daily Visitor
  • 76 visits

In Page Analysis