This is an website of newspaper for gujarati Language news, read by NRI and NRG from all over the world, specially from USA,Uk

akilanews.com
  • Domain Name
    akilanews.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #54837
  • Page Size
    934 B
  • Ip Address
    67.222.23.147
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    Akila Daily Gujarati News Online Newspaper
  • Meta Keyword
    gujarati news,gujarat news,news,india,india news,usa,usa news,uk,uk news,gujarati,gujarat,NRI,NRG,nri news,nrg news,electronics news,real estate news,computer news,politics,political news,india political news,gujarat political news, hotel news
  • Meta Description
    This is an website of newspaper for gujarati Language news, read by NRI and NRG from all over the world, specially from USA,Uk

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    67.222.23.147
  • Domain Age
    11 Years, 11 Months, 2 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Mon, 18 Feb 2013 17:48:02 GMT
  • server: Apache
  • last-modified: Thu, 07 Feb 2013 12:44:13 GMT
  • accept-ranges: bytes
  • content-length: 841
  • content-type: text/html
  • age: 12
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
No data whois for akilanews.com

DNS Analysis


DNS servers
ns1.akilanews.com [67.222.22.147]
ns2.akilanews.com [67.222.23.147]


DNS Records

Answer records
akilanews.com MX
preference: 0
exchange: akilanews.com
14400s
akilanews.com SOA
server: ns1.akilanews.com
email: ng@akilaindia.com
serial: 2013021402
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
akilanews.com NS  ns1.akilanews.com 86400s
akilanews.com NS  ns2.akilanews.com 86400s
akilanews.com A 67.222.23.147 14400s

Authority records

Additional records
akilanews.com A 67.222.23.147 14400s
ns1.akilanews.com A 67.222.22.147 14400s
ns2.akilanews.com A 67.222.23.147 14400s

IP 67.222.23.147 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 6 Errors
  • 6 Warnings
Ratio Text/Html
  • 0.8276231263383298
Message Error
  • Error Line 1, Column 1: no document type declaration; will parse without validation
    <script lanquage="Javascript">

    The document type could not be determined, because the document had no correct DOCTYPE declaration. The document does not look like HTML, therefore automatic fallback could not be performed, and the document was only checked against basic markup syntax.

    Learn how to add a doctype to your document from our FAQ, or use the validator's Document Type option to validate your document against a specific Document Type.

  • Error Line 5, Column 6: document type does not allow element "HEAD" here
    <head>

    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).

  • Error Line 7, Column 21: an attribute specification must start with a name or name token
    <META NAME="Author" "Nimish Ganatra">

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Warning Line 13, Column 1: unclosed start-tag requires SHORTTAG YES
    </head>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Error Line 15, Column 3: document type does not allow element "P" here
    <p>&nbsp;</p>

    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).

  • Warning Line 15, Column 5: cannot generate system identifier for general entity "nbsp"
    <p>&nbsp;</p>

    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 15, Column 5: general entity "nbsp" not defined and no default entity
    <p>&nbsp;</p>

    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 15, Column 9: reference to entity "nbsp" for which no system identifier could be generated
    <p>&nbsp;</p>

    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 15, Column 4: entity was defined here
    <p>&nbsp;</p>

Visitor Analysis

Daily Visitor
  • 4.083 visits
Daily Visitor