Croma Retail is one stop destination for online shopping in India. Buy online all the products that you need here. Shop online in India through Croma Retail and get products delivered in just ...

cromaretail.com
  • Domain Name
    cromaretail.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #9037
  • Page Size
    53 KB
  • Ip Address
    103.23.28.17
  • Heading
    H1: 1, H2: 16, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 26 JPG, 11 PNG

Website Meta Analysis

  • Title
    Online Shopping in India | Buy Online | Shop Online in India - Croma Retail
  • Meta Keyword
    shop online india, buy online india, online shop, buy online, shop online, online shopping in india, online shopping
  • Meta Description
    Croma Retail is one stop destination for online shopping in India. Buy online all the products that you need here. Shop online in India through Croma Retail and get products delivered in just few days to your doorsteps.

Technical Analysis

  • Webserver
    Microsoft-IIS/6.0
  • Ip Address
    103.23.28.17
  • Domain Age
    7 Years, 0 Months, 21 days.
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • date: Sat, 07 Sep 2013 21:08:18 GMT
  • pragma: no-cache
  • content-type: text/html; charset=utf-8
  • expires: Mon, 26 Jul 1997 05:00:00 GMT
  • etag: ""
  • server: Microsoft-IIS/6.0
  • x-powered-by: ASP.NET 2.0
  • x-powered-by-plesk: PleskWin
  • x-aspnet-version: 2.0.50727
  • xsltname: showbag
  • xsltload: 0
  • xslttransform: 3
  • content-encoding: gzip
  • vary: Accept-Encoding
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Infiniti Retail Ltd.
2nd floor, Akruti Centre Point,
Next to Marol Telephone Exchange,
MIDC, Andheri (E),
Mumbai, Maharashtra 400093
IN
Domain Domain Name: CROMARETAIL.COM

Administrative Contact:
Malim, Nadeem email
2nd floor, Akruti Centre Point,
Next to Marol Telephone Exchange,
MIDC, Andheri (E),
Mumbai, Maharashtra 400093
IN
91-22-67613600 Fax: 91-22-67101903
Technical Contact:
Deorah, Prashant email
77, Atlanta,
Nariman Point,
Mumbai, Maharashtra 400021
IN
91-22-22833158 Fax: 91-22-22876085

Registrar: TUCOWS, INC.
Updated: 19-Sep-2011.
Expires: 24-Aug-2018.
Created: 24-Aug-2006.
Name Servers:
NS1.PURETECHDSM.COM
NS1.PURETECH.CO.IN

Domain Domain Status: ok

DNS Analysis


DNS servers
ns.cromaretail.com [103.23.28.17]


DNS Records

Answer records
cromaretail.com MX
preference: 10
exchange: mail.global.frontbridge.com
86400s
cromaretail.com TXT 86400s
cromaretail.com A 103.23.28.17 86400s
cromaretail.com SOA
server: ns.cromaretail.com
email: nettigritty@nettigritty.com
serial: 1345722296
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 10800
86400s
cromaretail.com NS  ns.cromaretail.com 86400s

Authority records

Additional records
ns.cromaretail.com A 103.23.28.17 86400s

IP 103.23.28.17 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • % [whois.apnic.net node-1]
    % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

    inetnum: 103.23.28.0 - 103.23.28.255
    netname: NETTIGRITTY-IN
    descr: Nettigritty Private Limited
    descr: Web Hosting Provider
    descr: Hyderabad
    descr: Andhara Pradesh State of India
    country: IN
    admin-c: NPLN5-AP
    tech-c: NPLN5-AP
    status: ASSIGNED PORTABLE
    mnt-by: APNIC-HM
    mnt-routes: MAINT-NETTIGRITTY-IN
    mnt-irt: IRT-NETTIGRITTY-IN
    remarks: -+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    remarks: This object can only be updated by APNIC hostmasters.
    remarks: To update this object, please contact APNIC
    remarks: hostmasters and include your organisation's account
    remarks: name in the subject line.
    remarks: -+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    changed: hm-changed@apnic.net 20111114
    changed: hm-changed@apnic.net 20111121
    source: APNIC

    route: 103.23.28.0/24
    descr: Nettigritty Route Object
    origin: AS18229
    country: IN
    notify: nettigritty@nettigritty.com
    mnt-lower: MAINT-NETTIGRITTY-IN
    mnt-routes: MAINT-NETTIGRITTY-IN
    mnt-by: MAINT-NETTIGRITTY-IN
    changed: hm-changed@apnic.net 20111115
    source: APNIC

    role: NETTIGRITTY PRIVATE LIMITED - network administrato
    address: 6, 2nd Main Road
    address: JP Nagar 3rd Phase
    address: Bangalore - 560078
    address: Karnataka
    country: IN
    phone: +918026493025
    fax-no: +918026493056
    e-mail: nettigritty@nettigritty.com
    admin-c: NPLN5-AP
    tech-c: NPLN5-AP
    nic-hdl: NPLN5-AP
    mnt-by: MAINT-NETTIGRITTY-IN
    changed: zubin@nettigritty.com 20111117
    abuse-mailbox: abuse@nettigritty.com
    remarks: -+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    remarks: Please send abuse reports to abuse@nettigritty.com
    remarks: -+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    source: APNIC


In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 38 Errors
  • 15 Warnings
Ratio Text/Html
  • 0.588586485839061
Message Error
  • Error Line 12, Column 20: there is no attribute "property"
        <meta property="og:title" content="Croma :: Online Shopping in India | Buy …

    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 36, Column 33: character "&" is the first character of a delimiter but occurred as data
                    if (headElement && headElement.innerHTML)

    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.
  • Warning Line 36, Column 34: character "&" is the first character of a delimiter but occurred as data
                    if (headElement && headElement.innerHTML)

    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 37, Column 64: an attribute value must be a literal unless it contains only name characters
    …        headElement.innerHTML += "<meta http-equiv=\"refresh\" content=\"1\">";

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 37, Column 84: an attribute value must be a literal unless it contains only name characters
    …        headElement.innerHTML += "<meta http-equiv=\"refresh\" content=\"1\">";

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 37, Column 89: document type does not allow element "meta" here
    …        headElement.innerHTML += "<meta http-equiv=\"refresh\" content=\"1\">";

    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 37, Column 90: end tag for "meta" omitted, but OMITTAG NO was specified
    …        headElement.innerHTML += "<meta http-equiv=\"refresh\" content=\"1\">";

    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 37, Column 47: start tag was here
    …            headElement.innerHTML += "<meta http-equiv=\"refresh\" content=\"1…
  • Error Line 95, Column 124: there is no attribute "tite"
    …n="left" vspace="1" alt="customer care" tite="customer care" />&nbsp;&nbsp;Toll

    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 254, Column 30: ID "middle-box" already defined
                        <div id="middle-box">

    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 253, Column 1139: ID "middle-box" first defined here
    …="0" /></a></div></div></div><div id="middle-box" xmlns:commonClass="commonCla…
  • Error Line 261, Column 458: required attribute "alt" not specified
    …ight="50" align="left" class="promo" /></span></a><br /><a href="Sony-Cyber-sh…

    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 267, Column 406: required attribute "alt" not specified
    …ight="50" align="left" class="promo" /></span></a><br /><a href="Sony-Xperia-J…

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

  • Warning Line 326, Column 41: character "&" is the first character of a delimiter but occurred as data
                Subscribe to our Newsletter & never miss a latest product or offer

    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.
  • Warning Line 346, Column 176: character "&" is the first character of a delimiter but occurred as data
    …e</strong>’ to receive our newsletter & never miss a latest product or an attr…

    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 404, Column 112: document type does not allow element "br" here
    …ng with us for Croma newsletters.<br /><br />TATA Croma brings to you an excit…

    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 404, Column 118: document type does not allow element "br" here
    …h us for Croma newsletters.<br /><br />TATA Croma brings to you an exciting ra…

    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 404, Column 331: document type does not allow element "br" here
    …n \'Continue Shopping\' to begin.<br /><br /><a href=\"default.aspx\"><img src…

    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 404, Column 337: document type does not allow element "br" here
    …ntinue Shopping\' to begin.<br /><br /><a href=\"default.aspx\"><img src=\"ima…

    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 404, Column 346: an attribute value must be a literal unless it contains only name characters
    …opping\' to begin.<br /><br /><a href=\"default.aspx\"><img src=\"images/conti…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 404, Column 362: document type does not allow element "a" here
    …n.<br /><br /><a href=\"default.aspx\"><img src=\"images/continue-shopping-btn…

    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 404, Column 372: an attribute value must be a literal unless it contains only name characters
    …r /><a href=\"default.aspx\"><img src=\"images/continue-shopping-btn.png\" wid…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 404, Column 415: an attribute value must be a literal unless it contains only name characters
    …ges/continue-shopping-btn.png\" width=\"170\" height=\"30\" border=\"0\"/></a>…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 404, Column 430: an attribute value must be a literal unless it contains only name characters
    …s/continue-shopping-btn.png\" width=\"170\" height=\"30\" border=\"0\"/></a>');

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 404, Column 444: an attribute value must be a literal unless it contains only name characters
    …s/continue-shopping-btn.png\" width=\"170\" height=\"30\" border=\"0\"/></a>');

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 404, Column 450: required attribute "alt" not specified
    …s/continue-shopping-btn.png\" width=\"170\" height=\"30\" border=\"0\"/></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 404, Column 454: end tag for "img" omitted, but OMITTAG NO was specified
    …s/continue-shopping-btn.png\" width=\"170\" height=\"30\" border=\"0\"/></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 404, Column 363: start tag was here
    ….<br /><br /><a href=\"default.aspx\"><img src=\"images/continue-shopping-btn.…
  • Error Line 408, Column 113: document type does not allow element "br" here
    …ed with us for Croma newsletters.<br /><br />TATA Croma brings to you an excit…

    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 408, Column 119: document type does not allow element "br" here
    …h us for Croma newsletters.<br /><br />TATA Croma brings to you an exciting ra…

    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 408, Column 332: document type does not allow element "br" here
    …n \'Continue Shopping\' to begin.<br /><br /><a href=\"default.aspx\"><img src…

    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 408, Column 338: document type does not allow element "br" here
    …ntinue Shopping\' to begin.<br /><br /><a href=\"default.aspx\"><img src=\"ima…

    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 408, Column 347: an attribute value must be a literal unless it contains only name characters
    …opping\' to begin.<br /><br /><a href=\"default.aspx\"><img src=\"images/conti…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 408, Column 363: document type does not allow element "a" here
    …n.<br /><br /><a href=\"default.aspx\"><img src=\"images/continue-shopping-btn…

    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 408, Column 373: an attribute value must be a literal unless it contains only name characters
    …r /><a href=\"default.aspx\"><img src=\"images/continue-shopping-btn.png\" wid…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 408, Column 416: an attribute value must be a literal unless it contains only name characters
    …ges/continue-shopping-btn.png\" width=\"170\" height=\"30\" border=\"0\"/></a>…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 408, Column 431: an attribute value must be a literal unless it contains only name characters
    …s/continue-shopping-btn.png\" width=\"170\" height=\"30\" border=\"0\"/></a>");

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 408, Column 445: an attribute value must be a literal unless it contains only name characters
    …s/continue-shopping-btn.png\" width=\"170\" height=\"30\" border=\"0\"/></a>");

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 408, Column 451: required attribute "alt" not specified
    …s/continue-shopping-btn.png\" width=\"170\" height=\"30\" border=\"0\"/></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 408, Column 455: end tag for "img" omitted, but OMITTAG NO was specified
    …s/continue-shopping-btn.png\" width=\"170\" height=\"30\" border=\"0\"/></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 408, Column 364: start tag was here
    ….<br /><br /><a href=\"default.aspx\"><img src=\"images/continue-shopping-btn.…
  • Warning Line 470, Column 41: character "&" is the first character of a delimiter but occurred as data
                var regex = new RegExp("[\\?&]" + key + "=([^&#]*)");

    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.
  • Warning Line 470, Column 58: character "&" is the first character of a delimiter but occurred as data
                var regex = new RegExp("[\\?&]" + key + "=([^&#]*)");

    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.

Visitor Analysis

Daily Visitor
  • 24.500 visits