The leading and trend setting tabloid in the newspaper industry, ran by highly and technologically creative and innovative Filipino workers, committed and dedicated to serve readers by providing credible and accurate news reports ...
|Google Page Rank||5|
|Page Size||253.5 KB|
|Heading||H1: 0, H2: 2, H3: 25, H4: 245, H5: 0, H6: 0|
|Images||2 GIF, 32 JPG, 8 PNG|
Website Meta Analysis
|Title||Abante Online - Home|
|Meta Keyword||abante, tonite, balita, tabloid, dyaryo, online, mabilis, una, news, philippines, pilipinas, ngayon, bago, huli, latest, luzon, vismin, sports, entertainment, showbiz, opinyon, opinion, public, service, serbisyo, ilocandia, bicol, central, abroad, crimes, sagitsit, mindanao, style, fashion, health, lifestyle, istayl, food, pagkain, recipe, beauty, cosmetics, music|
|Meta Description||The leading and trend setting tabloid in the newspaper industry, ran by highly and technologically creative and innovative Filipino workers, committed and dedicated to serve readers by providing credible and accurate news reports and stories.|
|Webserver||Apache/2.2.3 (Red Hat)|
Hyper Text Transfer Protocol (HTTP) header show data header response from ninodezign.com.
- date: Tue, 07 Oct 2014 22:42:02 GMT
- server: Apache/2.2.3 (Red Hat)
- x-powered-by: PHP/5.4.28
- x-logged-in: False
- p3p: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
- etag: 2c0187b8225c556ddea9e68e268f2bd3
- content-encoding: gzip
- x-content-encoded-by: Joomla! 2.5
- cache-control: no-cache
- pragma: no-cache
- connection: close
- content-type: text/html; charset=UTF-8
- x-google-cache-control: remote-fetch
- via: HTTP/1.1 GWA
No data whois for abante.com.ph
IP 18.104.22.168 Analysis
|Country Code :|
|Country Code3 :|
|Country Name :|
|Continent Code :|
No whois ip data for 22.214.171.124
In Page Analysis
abante.com.ph has 5 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.
- 504 Errors
- 7 Warnings
- Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.
- Line 9, Column 14: there is no attribute "ROBOTS"
<META robots='index, nofollow'>
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.
- Line 9, Column 31: required attribute "CONTENT" not specified
<META robots='index, nofollow'>
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
- Line 25, Column 7: end tag for element "HEAD" which is not open
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 26, Column 6: document type does not allow element "BODY" here
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
- Line 30, Column 35: NET-enabling start-tag requires SHORTTAG YES
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.