In Page Analysis

jblover.com has 2 outlinks. The relation of external links to inner links influences the distribution of the site's weight in general. To grow the amount of indexed pages, there should be more inner links than external links.

HTML validation

Ratio Text/Html

Message Error

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.

Line 97, Column 14: end tag for element "tr" which is not open

</tr></table>

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.

Line 97, Column 22: end tag for element "table" which is not open

</tr></table>

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.

Line 99, Column 7: end tag for "br" omitted, but OMITTAG NO was specified

<br>

You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 99, Column 3: start tag was here

<br>

Line 110, Column 54: cannot generate system identifier for general entity "t"

…p://www.jblover.com/viewtopic.php?f=2&t=4575" title="Topic of The Week">Topic …

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.

Line 110, Column 54: general entity "t" not defined and no default entity

…p://www.jblover.com/viewtopic.php?f=2&t=4575" title="Topic of The Week">Topic …

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.

Line 110, Column 55: reference not terminated by REFC delimiter

…://www.jblover.com/viewtopic.php?f=2&t=4575" title="Topic of The Week">Topic o…

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.

Line 110, Column 55: reference to external entity in attribute value

…://www.jblover.com/viewtopic.php?f=2&t=4575" title="Topic of The Week">Topic o…

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

Line 110, Column 55: reference to entity "t" for which no system identifier could be generated

…://www.jblover.com/viewtopic.php?f=2&t=4575" title="Topic of The Week">Topic o…

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.

Line 110, Column 53: entity was defined here

…tp://www.jblover.com/viewtopic.php?f=2&t=4575" title="Topic of The Week">Topic…

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.

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.