Need Help? I consult with patients locally in the SF Bay Area and around the world via telephone & Skype CHRIS KRESSER L.AC MEDICINE FOR THE 21ST CENTURY Home About Consultations Podcast Store ...

chriskresser.com
  • Domain Name
    chriskresser.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #55146
  • Page Size
    53 KB
  • Ip Address
    66.175.215.222
  • Heading
    H1: 0, H2: 6, H3: 3, H4: 7, H5: 5, H6: 0
  • Images
    0 GIF, 3 JPG, 3 PNG

Website Meta Analysis

  • Title
    Chris Kresser
  • Meta Keyword
  • Meta Description
    Need Help? I consult with patients locally in the SF Bay Area and around the world via telephone & Skype CHRIS KRESSER L.AC MEDICINE FOR THE 21ST CENTURY Home About Consultations Podcast Store Contact Beyond Paleo Hypothyroidism Heart Disease ...

Technical Analysis

  • Webserver
    nginx/0.7.65
  • Ip Address
    66.175.215.222
  • Domain Age
    8 Years, 1 Months, 25 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/0.7.65
  • date: Thu, 28 Feb 2013 11:56:26 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • x-pingback: http://chriskresser.com/xmlrpc.php
  • x-cacheable: bot
  • cache-control: max-age=10800, must-revalidate
  • x-cache: HIT: 61
  • x-cache-group: bot
  • x-type: default
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Chris Kresser
6547 Whitney St
Oakland, California 94609
United States

Domain Name: CHRISKRESSER.COM
Created on: 16-Jan-05
Expires on: 16-Jan-13
Last Updated on: 30-Apr-12

Administrative Contact:
Kresser, Chris email
6547 Whitney St
Oakland, California 94609
United States
+1.4154253025

Technical Contact:
Kresser, Chris email
6547 Whitney St
Oakland, California 94609
United States
+1.4154253025

Domain servers in listed order:
NS10.DNSMADEEASY.COM
NS11.DNSMADEEASY.COM
NS12.DNSMADEEASY.COM
NS13.DNSMADEEASY.COM

DNS Analysis


DNS servers
jim.ns.cloudflare.com [173.245.59.125]
zara.ns.cloudflare.com [173.245.58.148]


DNS Records

Answer records
chriskresser.com A 66.175.215.222 300s
chriskresser.com MX
preference: 0
exchange: mail.chriskresser.com
300s
chriskresser.com NS  zara.ns.cloudflare.com 86400s
chriskresser.com NS  jim.ns.cloudflare.com 86400s
chriskresser.com SOA
server: jim.ns.cloudflare.com
email: dns@cloudflare.com
serial: 2013021312
refresh: 10000
retry: 2400
expire: 604800
minimum ttl: 3600
86400s
chriskresser.com TXT v=spf1amxinclude:websitewelcome.com~all 300s

Authority records

Additional records
mail.chriskresser.com A 67.18.18.246 300s

IP 66.175.215.222 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Osceola
  • Continent Code
    46561
  • Latitude
    574
  • Longitude
    588
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 66.175.215.222"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=66.175.215.222?showDetails=true&showARIN=false&ext=netref2
    #

    NetRange: 66.175.208.0 - 66.175.223.255
    CIDR: 66.175.208.0/20
    OriginAS:
    NetName: LINODE-US
    NetHandle: NET-66-175-208-0-1
    Parent: NET-66-0-0-0-0
    NetType: Direct Allocation
    Comment: This block is used for static customer allocations.
    RegDate: 2012-06-25
    Updated: 2012-06-26
    Ref: http://whois.arin.net/rest/net/NET-66-175-208-0-1

    OrgName: Linode
    OrgId: LINOD
    Address: 329 E. Jimmie Leeds Road
    Address: Suite A
    City: Galloway
    StateProv: NJ
    PostalCode: 08205
    Country: US
    RegDate: 2008-04-24
    Updated: 2010-08-31
    Comment: http://www.linode.com
    Ref: http://whois.arin.net/rest/org/LINOD

    OrgAbuseHandle: LAS12-ARIN
    OrgAbuseName: Linode Abuse Support
    OrgAbusePhone: +1-609-593-7103
    OrgAbuseEmail: abuse@linode.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/LAS12-ARIN

    OrgTechHandle: LNO21-ARIN
    OrgTechName: Linode Network Operations
    OrgTechPhone: +1-609-593-7103
    OrgTechEmail: support@linode.com
    OrgTechRef: http://whois.arin.net/rest/poc/LNO21-ARIN

    OrgNOCHandle: LNO21-ARIN
    OrgNOCName: Linode Network Operations
    OrgNOCPhone: +1-609-593-7103
    OrgNOCEmail: support@linode.com
    OrgNOCRef: http://whois.arin.net/rest/poc/LNO21-ARIN

    RTechHandle: LNO21-ARIN
    RTechName: Linode Network Operations
    RTechPhone: +1-609-593-7103
    RTechEmail: support@linode.com
    RTechRef: http://whois.arin.net/rest/poc/LNO21-ARIN

    RNOCHandle: LNO21-ARIN
    RNOCName: Linode Network Operations
    RNOCPhone: +1-609-593-7103
    RNOCEmail: support@linode.com
    RNOCRef: http://whois.arin.net/rest/poc/LNO21-ARIN

    RAbuseHandle: LAS12-ARIN
    RAbuseName: Linode Abuse Support
    RAbusePhone: +1-609-593-7103
    RAbuseEmail: abuse@linode.com
    RAbuseRef: http://whois.arin.net/rest/poc/LAS12-ARIN

    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 76 Errors
  • 32 Warnings
Ratio Text/Html
  • 0.6732967113994985
Message Error
  • Error Line 30, Column 16: there is no attribute "property"
    <meta property="og:title" content="Chris Kresser: Medicine for the 21st Century…

    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 44, Column 22: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
      <div id="title_msg"><div id="need_help"><a href="/clinic/" class="cssbutton g…

    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 44, Column 228: character "&" is the first character of a delimiter but occurred as data
    …cally in the SF Bay Area and around the world via telephone & Skype</div></div>

    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 45, Column 18: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
      <div id="title"><span class="large_cap">C</span>HRIS <span class="large_cap">…

    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 46, Column 22: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
      <div id="title_tag">MEDICINE FOR THE 21<span class="superscript">ST</span> CE…

    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 75, Column 217: value of attribute "method" cannot be "POST"; must be one of "get", "post"
    …/process/6021bbc940063940564c34d41aa02f61" class="infusion-form" method="POST">

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 76, Column 95: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …t name="inf_form_xid" type="hidden" value="6021bbc940063940564c34d41aa02f61" />

    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 77, Column 93: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …put name="inf_form_name" type="hidden" value="opt in form for ck.com and BP" />

    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 78, Column 80: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
               <input name="infusionsoft_version" type="hidden" value="1.26.4.29" />

    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 82, Column 141: there is no attribute "placeholder"
    …" type="text" name="inf_field_Email" value="" placeholder="Email Address..." />

    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 84, Column 129: end tag for "input" omitted, but OMITTAG NO was specified
    …" name="subscribe" id="mc-embedded-subscribe" class="cssbutton join_us button">

    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 84, Column 14: start tag was here
                 <input type="submit" value="Join Now" name="subscribe" id="mc-embe…
  • Error Line 109, Column 15: there is no attribute "data-url"
         data-url="http://chriskresser.com/the-saturated-fat-heart-disease-myth-col…

    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 110, Column 15: there is no attribute "data-via"
         data-via="chriskresser"

    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 111, Column 16: there is no attribute "data-text"
         data-text="Chris Kresser: RHR: The saturated fat &#8211; heart disease myt…

    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 112, Column 19: there is no attribute "data-related"
         data-related="Chris Kresser: "

    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 113, Column 17: there is no attribute "data-count"
         data-count="horizontal">Tweet</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 118, Column 47: there is no attribute "data-href"
    …d="fbshare" class="fb-like" data-href="http://chriskresser.com/the-saturated-f…

    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 118, Column 170: there is no attribute "data-send"
    …s-and-intermittent-fasting" data-send="true" data-layout="button_count" data-w…

    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 118, Column 189: there is no attribute "data-layout"
    …fasting" data-send="true" data-layout="button_count" data-width="125" data-sho…

    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 118, Column 215: there is no attribute "data-width"
    …rue" data-layout="button_count" data-width="125" data-show-faces="false"></div>

    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 118, Column 237: there is no attribute "data-show-faces"
    …rue" data-layout="button_count" data-width="125" data-show-faces="false"></div>

    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 126, Column 38: there is no attribute "data-size"
        <div class="g-plusone" data-size="medium" data-href="http://chriskresser.co…

    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 134, Column 351: cannot generate system identifier for general entity "h"
    …evolution-Health-Radio-logo1.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>

    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 134, Column 351: general entity "h" not defined and no default entity
    …evolution-Health-Radio-logo1.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>

    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.

  • Warning Line 134, Column 352: reference not terminated by REFC delimiter
    …evolution-Health-Radio-logo1.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>

    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.

  • Warning Line 134, Column 352: reference to external entity in attribute value
    …evolution-Health-Radio-logo1.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>

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

  • Error Line 134, Column 352: reference to entity "h" for which no system identifier could be generated
    …evolution-Health-Radio-logo1.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>

    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 134, Column 350: entity was defined here
    …evolution-Health-Radio-logo1.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>
  • Error Line 134, Column 377: required attribute "alt" not specified
    …evolution-Health-Radio-logo1.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></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 134, Column 381: end tag for element "a" which is not open
    …evolution-Health-Radio-logo1.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>

    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.

  • Warning Line 145, Column 171: reference not terminated by REFC delimiter
    …scopy-health-risks-and-intermittent-fasting">Read More &raquo</a></p>				</div>

    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.

  • Error Line 157, Column 12: ID "tweet" already defined
      <div id="tweet">

    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 107, Column 12: ID "tweet" first defined here
      <div id="tweet">
  • Error Line 168, Column 12: ID "fbshare" already defined
      <div id="fbshare" class="fb-like" data-href="http://chriskresser.com/are-you-…

    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 118, Column 12: ID "fbshare" first defined here
      <div id="fbshare" class="fb-like" data-href="http://chriskresser.com/the-satu…
  • Error Line 175, Column 12: ID "gplus" already defined
      <div id="gplus">

    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 125, Column 12: ID "gplus" first defined here
      <div id="gplus">
  • Warning Line 184, Column 336: reference not terminated by REFC delimiter
    …/support-300x300.jpeg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>Do you lov…

    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.

  • Warning Line 184, Column 336: reference to external entity in attribute value
    …/support-300x300.jpeg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>Do you lov…

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

  • Error Line 184, Column 336: reference to entity "h" for which no system identifier could be generated
    …/support-300x300.jpeg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>Do you lov…

    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 134, Column 350: entity was defined here
    …evolution-Health-Radio-logo1.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>
  • Error Line 184, Column 361: required attribute "alt" not specified
    …;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>Do you love sharing what you've lea…

    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 184, Column 365: end tag for element "a" which is not open
    …00&amp;&h=150&amp;zc=1&amp;q=80" /></a>Do you love sharing what you've learned…

    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.

  • Warning Line 186, Column 365: reference not terminated by REFC delimiter
    …make-a-difference-become-a-paleo-ambassador">Read More &raquo</a></p>				</div>

    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.

  • Error Line 198, Column 12: ID "tweet" already defined
      <div id="tweet">

    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 107, Column 12: ID "tweet" first defined here
      <div id="tweet">
  • Error Line 209, Column 12: ID "fbshare" already defined
      <div id="fbshare" class="fb-like" data-href="http://chriskresser.com/take-the…

    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 118, Column 12: ID "fbshare" first defined here
      <div id="fbshare" class="fb-like" data-href="http://chriskresser.com/the-satu…
  • Error Line 216, Column 12: ID "gplus" already defined
      <div id="gplus">

    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 125, Column 12: ID "gplus" first defined here
      <div id="gplus">
  • Warning Line 225, Column 286: reference not terminated by REFC delimiter
    …ploads/medfrd1248.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>One of the…

    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.

  • Warning Line 225, Column 286: reference to external entity in attribute value
    …ploads/medfrd1248.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>One of the…

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

  • Error Line 225, Column 286: reference to entity "h" for which no system identifier could be generated
    …ploads/medfrd1248.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>One of the…

    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 134, Column 350: entity was defined here
    …evolution-Health-Radio-logo1.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>
  • Error Line 225, Column 311: required attribute "alt" not specified
    …;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>One of the coolest things about the…

    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 225, Column 315: end tag for element "a" which is not open
    …00&amp;&h=150&amp;zc=1&amp;q=80" /></a>One of the coolest things about the anc…

    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.

  • Warning Line 227, Column 227: reference not terminated by REFC delimiter
    …com/take-the-online-ancestral-health-survey">Read More &raquo</a></p>				</div>

    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.

  • Error Line 239, Column 12: ID "tweet" already defined
      <div id="tweet">

    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 107, Column 12: ID "tweet" first defined here
      <div id="tweet">
  • Error Line 250, Column 12: ID "fbshare" already defined
      <div id="fbshare" class="fb-like" data-href="http://chriskresser.com/how-arti…

    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 118, Column 12: ID "fbshare" first defined here
      <div id="fbshare" class="fb-like" data-href="http://chriskresser.com/the-satu…
  • Error Line 257, Column 12: ID "gplus" already defined
      <div id="gplus">

    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 125, Column 12: ID "gplus" first defined here
      <div id="gplus">
  • Warning Line 266, Column 312: reference not terminated by REFC delimiter
    …/uploads/insomnia.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>"A good la…

    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.

  • Warning Line 266, Column 312: reference to external entity in attribute value
    …/uploads/insomnia.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>"A good la…

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

  • Error Line 266, Column 312: reference to entity "h" for which no system identifier could be generated
    …/uploads/insomnia.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>"A good la…

    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 134, Column 350: entity was defined here
    …evolution-Health-Radio-logo1.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>
  • Error Line 266, Column 337: required attribute "alt" not specified
    …;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>"A good laugh and a long sleep are …

    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 266, Column 341: end tag for element "a" which is not open
    …00&amp;&h=150&amp;zc=1&amp;q=80" /></a>"A good laugh and a long sleep are the …

    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.

  • Warning Line 268, Column 502: reference not terminated by REFC delimiter
    …wrecking-your-sleep-and-what-to-do-about-it">Read More &raquo</a></p>				</div>

    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.

  • Error Line 281, Column 12: ID "tweet" already defined
      <div id="tweet">

    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 107, Column 12: ID "tweet" first defined here
      <div id="tweet">
  • Error Line 292, Column 12: ID "fbshare" already defined
      <div id="fbshare" class="fb-like" data-href="http://chriskresser.com/recipe-s…

    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 118, Column 12: ID "fbshare" first defined here
      <div id="fbshare" class="fb-like" data-href="http://chriskresser.com/the-satu…
  • Error Line 299, Column 12: ID "gplus" already defined
      <div id="gplus">

    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 125, Column 12: ID "gplus" first defined here
      <div id="gplus">
  • Warning Line 307, Column 276: reference not terminated by REFC delimiter
    …/squash2-300x200.jpeg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>Today's re…

    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.

  • Warning Line 307, Column 276: reference to external entity in attribute value
    …/squash2-300x200.jpeg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>Today's re…

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

  • Error Line 307, Column 276: reference to entity "h" for which no system identifier could be generated
    …/squash2-300x200.jpeg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>Today's re…

    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 134, Column 350: entity was defined here
    …evolution-Health-Radio-logo1.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>
  • Error Line 307, Column 301: required attribute "alt" not specified
    …;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>Today's recipe isn't quite a recipe…

    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 307, Column 305: end tag for element "a" which is not open
    …00&amp;&h=150&amp;zc=1&amp;q=80" /></a>Today's recipe isn't quite a recipe - i…

    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.

  • Warning Line 312, Column 169: reference not terminated by REFC delimiter
    …://chriskresser.com/recipe-squash-thickener">Read More &raquo</a></p>				</div>

    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.

  • Error Line 323, Column 12: ID "tweet" already defined
      <div id="tweet">

    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 107, Column 12: ID "tweet" first defined here
      <div id="tweet">
  • Error Line 334, Column 12: ID "fbshare" already defined
      <div id="fbshare" class="fb-like" data-href="http://chriskresser.com/for-a-he…

    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 118, Column 12: ID "fbshare" first defined here
      <div id="fbshare" class="fb-like" data-href="http://chriskresser.com/the-satu…
  • Error Line 341, Column 12: ID "gplus" already defined
      <div id="gplus">

    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 125, Column 12: ID "gplus" first defined here
      <div id="gplus">
  • Warning Line 349, Column 280: reference not terminated by REFC delimiter
    …/uploads/96674849.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>I’ve writt…

    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.

  • Warning Line 349, Column 280: reference to external entity in attribute value
    …/uploads/96674849.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>I’ve writt…

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

  • Error Line 349, Column 280: reference to entity "h" for which no system identifier could be generated
    …/uploads/96674849.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>I’ve writt…

    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 134, Column 350: entity was defined here
    …evolution-Health-Radio-logo1.jpg&amp;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>
  • Error Line 349, Column 305: required attribute "alt" not specified
    …;w=200&amp;&h=150&amp;zc=1&amp;q=80" /></a>I’ve written before about the dange…

    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 349, Column 309: end tag for element "a" which is not open
    …00&amp;&h=150&amp;zc=1&amp;q=80" /></a>I’ve written before about the dangers o…

    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.

  • Warning Line 351, Column 153: reference not terminated by REFC delimiter
    …ser.com/for-a-healthy-heart-stick-to-butter">Read More &raquo</a></p>				</div>

    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.

  • Error Line 365, Column 9: end tag for "ul" which is not finished
    				</ul>

    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 370, Column 40: there is no attribute "target"
    …   <li class="icon twitter"><a target="_blank" class="ir" href="https://twitte…

    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 420, Column 11: ID "must_read" already defined
      <ul id="must_read">

    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 418, Column 10: ID "must_read" first defined here
    <div id="must_read" class="sidebar-section sidebar_posts">
  • Error Line 494, Column 10: ID "myths_truths" already defined
    <div id="myths_truths" class="sidebar_posts">

    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 473, Column 10: ID "myths_truths" first defined here
    <div id="myths_truths" class="sidebar_posts">
  • Error Line 535, Column 99: end tag for element "a" which is not open
    …e_tag">MEDICINE FOR THE 21<span class="superscript">ST</span> CENTURY</div></a>

    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.

  • Warning Line 572, Column 32: character "&" is the first character of a delimiter but occurred as data
    	  jQuery.ajax({	// add limit=5& to set a limit

    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 573, Column 73: cannot generate system identifier for general entity "access_token"
    …://graph.facebook.com/' + screen_name + '/feed?limit=20&access_token=' + token,

    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 573, Column 73: general entity "access_token" not defined and no default entity
    …://graph.facebook.com/' + screen_name + '/feed?limit=20&access_token=' + token,

    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.

  • Warning Line 573, Column 85: reference not terminated by REFC delimiter
    …://graph.facebook.com/' + screen_name + '/feed?limit=20&access_token=' + token,

    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.

  • Error Line 573, Column 85: reference to entity "access_token" for which no system identifier could be generated
    …://graph.facebook.com/' + screen_name + '/feed?limit=20&access_token=' + token,

    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 573, Column 72: entity was defined here
    …://graph.facebook.com/' + screen_name + '/feed?limit=20&access_token=' + token,
  • Error Line 590, Column 38: character ";" not allowed in attribute specification list
    		for(var i=0; i<jsonData.data.length; i++) {
  • Error Line 590, Column 38: element "jsonData.data.length" undefined
    		for(var i=0; i<jsonData.data.length; i++) {

    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).
  • Warning Line 593, Column 23: character "&" is the first character of a delimiter but occurred as data
    			if( "from" in item && fbid == item.from.id ){

    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 593, Column 24: character "&" is the first character of a delimiter but occurred as data
    			if( "from" in item && fbid == item.from.id ){

    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 600, Column 25: character data is not allowed here
        	var newHTML = '<ul>' + feedHTML.join('') + '</ul>';

    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.
  • Error Line 600, Column 54: end tag for "ul" which is not finished
        	var newHTML = '<ul>' + feedHTML.join('') + '</ul>';

    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.

  • Warning Line 625, Column 21: character "<" is the first character of a delimiter but occurred as data
    		a_p =  (curr_hour < 12 ? "am" : "pm");

    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 666, Column 10: end tag for "jsonData.data.length" omitted, but OMITTAG NO was specified
    	</script>

    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 590, Column 17: start tag was here
    		for(var i=0; i<jsonData.data.length; i++) {
  • Error Line 694, Column 87: there is no attribute "alt"
    …yAcupuncture.com" target="_blank" alt="Evan Haas" title="Evan Haas">Evan Haas<…

    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 694, Column 131: character "&" is the first character of a delimiter but occurred as data
    …Haas" title="Evan Haas">Evan Haas</a> & <a href="http://www.succulentorange.co…

    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 698, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 702, Column 57: cannot generate system identifier for general entity "appId"
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=234197713276392";

    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 702, Column 57: general entity "appId" not defined and no default entity
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=234197713276392";

    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.

  • Warning Line 702, Column 62: reference not terminated by REFC delimiter
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=234197713276392";

    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.

  • Error Line 702, Column 62: reference to entity "appId" for which no system identifier could be generated
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=234197713276392";

    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 702, Column 56: entity was defined here
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=234197713276392";
  • Error Line 706, Column 10: required attribute "type" not specified
      <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getEl…

    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 717, Column 10: ID "fb-root" already defined
    <div id="fb-root"></div>

    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 697, Column 12: ID "fb-root" first defined here
      <div id="fb-root"></div>
  • Error Line 718, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 727, Column 125: cannot generate system identifier for general entity "count"
    …es/user_timeline/chriskresser.json?callback=twitterCallback2&count=6"></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 727, Column 125: general entity "count" not defined and no default entity
    …es/user_timeline/chriskresser.json?callback=twitterCallback2&count=6"></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.

  • Warning Line 727, Column 130: reference not terminated by REFC delimiter
    …es/user_timeline/chriskresser.json?callback=twitterCallback2&count=6"></script>

    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.

  • Warning Line 727, Column 130: reference to external entity in attribute value
    …es/user_timeline/chriskresser.json?callback=twitterCallback2&count=6"></script>

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

  • Error Line 727, Column 130: reference to entity "count" for which no system identifier could be generated
    …es/user_timeline/chriskresser.json?callback=twitterCallback2&count=6"></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 727, Column 124: entity was defined here
    …es/user_timeline/chriskresser.json?callback=twitterCallback2&count=6"></script>

Visitor Analysis

Daily Visitor
  • 4.900 visits
Daily Visitor