Нужен совет по оптимизации сайта

line 411 column 609 - Предупреждение: entity "&nbsp" doesn't end in ';'
line 411 column 614 - Предупреждение: unescaped & or unknown entity "&nbsp02:25"
line 413 column 330 - Предупреждение: entity "&nbsp" doesn't end in ';'
line 413 column 335 - Предупреждение: unescaped & or unknown entity "&nbsp00:01"
line 415 column 528 - Предупреждение: entity "&nbsp" doesn't end in ';'
line 415 column 533 - Предупреждение: unescaped & or unknown entity "&nbsp22:12"
line 417 column 638 - Предупреждение: entity "&nbsp" doesn't end in ';'
line 417 column 643 - Предупреждение: unescaped & or unknown entity "&nbsp04:53"
line 419 column 672 - Предупреждение: entity "&nbsp" doesn't end in ';'
line 419 column 677 - Предупреждение: unescaped & or unknown entity "&nbsp00:11"
line 478 column 1 - Предупреждение: <style> isn't allowed in <div> elements
line 374 column 1 - Информация: <div> previously mentioned
line 512 column 9 - Предупреждение: <input> element not empty or not closed
line 514 column 9 - Предупреждение: <input> element not empty or not closed
line 515 column 117 - Предупреждение: <input> isn't allowed in <tbody> elements
line 515 column 110 - Информация: <tbody> previously mentioned
line 515 column 117 - Предупреждение: <input> element not empty or not closed
line 516 column 7 - Предупреждение: <input> element not empty or not closed
line 517 column 7 - Предупреждение: <input> element not empty or not closed
line 517 column 49 - Предупреждение: <input> element not empty or not closed
line 517 column 93 - Предупреждение: <input> element not empty or not closed
line 517 column 142 - Предупреждение: <input> element not empty or not closed
line 517 column 231 - Предупреждение: <input> element not empty or not closed
line 517 column 363 - Предупреждение: <input> element not empty or not closed
line 517 column 452 - Предупреждение: <input> element not empty or not closed
line 517 column 584 - Предупреждение: <input> element not empty or not closed
line 517 column 673 - Предупреждение: <input> element not empty or not closed
line 11 column 1 - Предупреждение: <script> inserting "type" attribute
line 515 column 110 - Предупреждение: trimming empty <tbody>
line 549 column 44 - Предупреждение: trimming empty <span>
Информация: Doctype given is "-//W3C//DTD XHTML 1.0 Transitional//EN"
Информация: Document content looks like XHTML 1.0 Transitional
подправить надо!!!


Validation Output: 32 Errors

Error Line 11, Column 8: required attribute "type" not specified

<script>

✉

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 411, Column 614: reference not terminated by REFC delimiter

…ss="posts-widget-meta">30.03.2013&nbsp&nbsp02:25 …

✉

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 411, Column 615: cannot generate system identifier for general entity "nbsp02:25"

…s="posts-widget-meta">30.03.2013&nbsp&nbsp02:25 …

✉

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 411, Column 615: general entity "nbsp02:25" not defined and no default entity

…s="posts-widget-meta">30.03.2013&nbsp&nbsp02:25 …

✉

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 411, Column 624: reference not terminated by REFC delimiter

…widget-meta">30.03.2013&nbsp&nbsp02:25 …

✉

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 411, Column 624: reference to entity "nbsp02:25" for which no system identifier could be generated

…widget-meta">30.03.2013&nbsp&nbsp02:25 …

✉

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 411, Column 614: entity was defined here

…ss="posts-widget-meta">30.03.2013&nbsp&nbsp02:25 …

Warning Line 413, Column 335: reference not terminated by REFC delimiter

…ss="posts-widget-meta">30.03.2013&nbsp&nbsp00:01 …

✉

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 413, Column 336: cannot generate system identifier for general entity "nbsp00:01"

…s="posts-widget-meta">30.03.2013&nbsp&nbsp00:01 …

✉

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 413, Column 336: general entity "nbsp00:01" not defined and no default entity

…s="posts-widget-meta">30.03.2013&nbsp&nbsp00:01 …

✉

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 413, Column 345: reference not terminated by REFC delimiter

…widget-meta">30.03.2013&nbsp&nbsp00:01 …

✉

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 413, Column 345: reference to entity "nbsp00:01" for which no system identifier could be generated

…widget-meta">30.03.2013&nbsp&nbsp00:01 …

✉

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 413, Column 335: entity was defined here

…ss="posts-widget-meta">30.03.2013&nbsp&nbsp00:01 …

Warning Line 415, Column 533: reference not terminated by REFC delimiter

…ss="posts-widget-meta">29.03.2013&nbsp&nbsp22:12 …

✉

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 415, Column 534: cannot generate system identifier for general entity "nbsp22:12"

…s="posts-widget-meta">29.03.2013&nbsp&nbsp22:12 …

✉

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 415, Column 534: general entity "nbsp22:12" not defined and no default entity

…s="posts-widget-meta">29.03.2013&nbsp&nbsp22:12 …

✉

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 415, Column 543: reference not terminated by REFC delimiter

…widget-meta">29.03.2013&nbsp&nbsp22:12 …

✉

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 415, Column 543: reference to entity "nbsp22:12" for which no system identifier could be generated

…widget-meta">29.03.2013&nbsp&nbsp22:12 …

✉

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 415, Column 533: entity was defined here

…ss="posts-widget-meta">29.03.2013&nbsp&nbsp22:12 …

Warning Line 417, Column 643: reference not terminated by REFC delimiter

…ss="posts-widget-meta">25.03.2013&nbsp&nbsp04:53 …

✉

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 417, Column 644: cannot generate system identifier for general entity "nbsp04:53"

…s="posts-widget-meta">25.03.2013&nbsp&nbsp04:53 …

✉

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 417, Column 644: general entity "nbsp04:53" not defined and no default entity

…s="posts-widget-meta">25.03.2013&nbsp&nbsp04:53 …

✉

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 417, Column 653: reference not terminated by REFC delimiter

…widget-meta">25.03.2013&nbsp&nbsp04:53 …

✉

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 417, Column 653: reference to entity "nbsp04:53" for which no system identifier could be generated

…widget-meta">25.03.2013&nbsp&nbsp04:53 …

✉

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 417, Column 643: entity was defined here

…ss="posts-widget-meta">25.03.2013&nbsp&nbsp04:53 …

Warning Line 419, Column 677: reference not terminated by REFC delimiter

…ss="posts-widget-meta">25.03.2013&nbsp&nbsp00:11 …

✉

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 419, Column 678: cannot generate system identifier for general entity "nbsp00:11"

…s="posts-widget-meta">25.03.2013&nbsp&nbsp00:11 …

✉

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 419, Column 678: general entity "nbsp00:11" not defined and no default entity

…s="posts-widget-meta">25.03.2013&nbsp&nbsp00:11 …

✉

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 419, Column 687: reference not terminated by REFC delimiter

…widget-meta">25.03.2013&nbsp&nbsp00:11 …

✉

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 419, Column 687: reference to entity "nbsp00:11" for which no system identifier could be generated

…widget-meta">25.03.2013&nbsp&nbsp00:11 …

✉

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 419, Column 677: entity was defined here

…ss="posts-widget-meta">25.03.2013&nbsp&nbsp00:11 …

Error Line 425, Column 397: required attribute "alt" not specified

…om/avatar.php?gravatar_id=e9fe3942264b03467b5260613c213507&amp;size=32" /></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 430, Column 296: required attribute "alt" not specified

…om/avatar.php?gravatar_id=b135ca55ea3c7db1822febd4a2cc24b4&amp;size=32" /></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 435, Column 333: required attribute "alt" not specified

…om/avatar.php?gravatar_id=b135ca55ea3c7db1822febd4a2cc24b4&amp;size=32" /></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 440, Column 305: required attribute "alt" not specified

…om/avatar.php?gravatar_id=b135ca55ea3c7db1822febd4a2cc24b4&amp;size=32" /></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 445, Column 308: required attribute "alt" not specified

…om/avatar.php?gravatar_id=40d053bada3562c45d510a3e4fd49b77&amp;size=32" /></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 478, Column 23: document type does not allow element "style" here

<style type="text/css">/*<![CDATA[*/.sr-box table {width: auto !important;}#ele…

✉

The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Warning Line 484, Column 91: character "&" is the first character of a delimiter but occurred as data

…put[name="script_path_2_38"]').length && (document.charset || document.charact…

✉

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 484, Column 92: character "&" is the first character of a delimiter but occurred as data

…ut[name="script_path_2_38"]').length && (document.charset || document.characte…

✉

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 512, Column 110: end tag for "input" omitted, but OMITTAG NO was specified

…nput" name="field_name_first" class="sr-required" value="Ваше имя" type="text">

✉

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 512, Column 9: start tag was here

<input id="your_name_input" name="field_name_first" class="sr-required"…

Error Line 514, Column 111: end tag for "input" omitted, but OMITTAG NO was specified

…ns" name="field_email" class="sr-required" value="Ваш email-адрес" type="text">

✉

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 514, Column 9: start tag was here

<input id="your_email_ins" name="field_email" class="sr-required" value…

Error Line 515, Column 213: document type does not allow element "input" here

…" name="subscribe" value="Подписаться" type="submit"></tbody></table></li></ul>

✉

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 515, Column 221: end tag for "input" omitted, but OMITTAG NO was specified

…" name="subscribe" value="Подписаться" type="submit"></tbody></table></li></ul>

✉

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 515, Column 117: start tag was here

…scribe" class="style_of_table"><tbody><input class="button_subscribe" id="grad…

Error Line 515, Column 221: end tag for "tbody" which is not finished

…" name="subscribe" value="Подписаться" type="submit"></tbody></table></li></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 516, Column 54: end tag for "input" omitted, but OMITTAG NO was specified

<input name="uid" value="227468" type="hidden">

✉

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 516, Column 7: start tag was here

<input name="uid" value="227468" type="hidden">

Error Line 517, Column 49: end tag for "input" omitted, but OMITTAG NO was specified

…ut name="tid" value="0" type="hidden"><input name="lang" value="ru" type="hidd…

✉

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 517, Column 7: start tag was here

<input name="tid" value="0" type="hidden"><input name="lang" value="ru" t…

Error Line 517, Column 93: end tag for "input" omitted, but OMITTAG NO was specified

… name="lang" value="ru" type="hidden"><input name="did[]" value="264266" type=…

✉

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 517, Column 49: start tag was here

…ut name="tid" value="0" type="hidden"><input name="lang" value="ru" type="hidd…

Error Line 517, Column 142: end tag for "input" omitted, but OMITTAG NO was specified

…="did[]" value="264266" type="hidden"><input value="/227001-228000/227468/sr-j…

✉

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 517, Column 93: start tag was here

… name="lang" value="ru" type="hidden"><input name="did[]" value="264266" type=…

Error Line 517, Column 231: end tag for "input" omitted, but OMITTAG NO was specified

…name="script_path_2_67" type="hidden"><input value="https://imgs.smartresponde…

✉

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 517, Column 142: start tag was here

…="did[]" value="264266" type="hidden"><input value="/227001-228000/227468/sr-j…

Error Line 517, Column 363: end tag for "input" omitted, but OMITTAG NO was specified

… name="script_url_2_67" type="hidden"><input value="/227001-228000/227468/sr-j…

✉

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 517, Column 231: start tag was here

…name="script_path_2_67" type="hidden"><input value="https://imgs.smartresponde…

Error Line 517, Column 452: end tag for "input" omitted, but OMITTAG NO was specified

…name="script_path_2_84" type="hidden"><input value="https://imgs.smartresponde…

✉

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 517, Column 363: start tag was here

… name="script_url_2_67" type="hidden"><input value="/227001-228000/227468/sr-j…

Error Line 517, Column 584: end tag for "input" omitted, but OMITTAG NO was specified

… name="script_url_2_84" type="hidden"><input value="/227001-228000/227468/sr-j…

✉

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 517, Column 452: start tag was here

…name="script_path_2_84" type="hidden"><input value="https://imgs.smartresponde…

Error Line 517, Column 673: end tag for "input" omitted, but OMITTAG NO was specified

…name="script_path_2_38" type="hidden"><input value="https://imgs.smartresponde…

✉

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 517, Column 584: start tag was here

… name="script_url_2_84" type="hidden"><input value="/227001-228000/227468/sr-j…

Error Line 517, Column 811: end tag for "input" omitted, but OMITTAG NO was specified

…27001-228000/227468/sr-js-2_38.js" name="script_url_2_38" type="hidden"></form>

✉

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 517, Column 673: start tag was here

…name="script_path_2_38" type="hidden"><input value="https://imgs.smartresponde…



W3C результаты проверки CSS для http://v-zdor.com/ (CSS2.1)
К сожалению, мы обнаружили следующие ошибки (60)
URI : http://v-zdor.com/wp-content/t... faults.css
216 .wp-caption Свойство border-radius не существует в CSS2.1, но существует в [css3] : 3px
URI : http://fonts.googleapis.com/cs... rillic-ext
2 Ошибка значения : font-family Свойство font-family не существует в CSS2.1, но существует в [css1, css2, css3] : 'Ubuntu Condensed'
URI : http://fonts.googleapis.com/cs... rillic-ext
3 Ошибка значения : font-style Свойство font-style не существует в CSS2.1, но существует в [css1, css2, css3] : normal
URI : http://fonts.googleapis.com/cs... rillic-ext
4 Ошибка значения : font-weight Свойство font-weight не существует в CSS2.1, но существует в [css1, css2, css3] : 400
URI : http://fonts.googleapis.com/cs... rillic-ext
5 Свойство src не существует : local('Ubuntu Condensed'),local('UbuntuCondensed-Regular'),url(http://themes.googleuserconten... BMyj2w.ttf) format('truetype')
URI : http://fonts.googleapis.com/cs... n,cyrillic
2 Ошибка значения : font-family Свойство font-family не существует в CSS2.1, но существует в [css1, css2, css3] : 'Underdog'
URI : http://fonts.googleapis.com/cs... n,cyrillic
3 Ошибка значения : font-style Свойство font-style не существует в CSS2.1, но существует в [css1, css2, css3] : normal
URI : http://fonts.googleapis.com/cs... n,cyrillic
4 Ошибка значения : font-weight Свойство font-weight не существует в CSS2.1, но существует в [css1, css2, css3] : 400
URI : http://fonts.googleapis.com/cs... n,cyrillic
5 Свойство src не существует : local('Underdog'),local('Underdog-Regular'),url(http://themes.googleuserconten... 7m55DA.ttf) format('truetype')
URI : http://v-zdor.com/wp-content/t... /style.css
36 body Свойство overflow-y не существует в CSS2.1, но существует в [css3] : scroll
154 .menu-primary-container Свойство border-radius не существует в CSS2.1, но существует в [css3] : 5px
370 .no_indent Ошибка значения : text-indent none не является значением text-indent : none
719 .fp-content Свойство opacity не существует в CSS2.1, но существует в [css3] : 0.7
720 .fp-content Ошибка разбора = 70)
757 .fp-pager a Свойство opacity не существует в CSS2.1, но существует в [css3] : 0.7
758 .fp-pager a Ошибка разбора = 70)
764 .fp-pager a:hover, .fp-pager a.activeSlide Свойство opacity не существует в CSS2.1, но существует в [css3] : 1.0
765 .fp-pager a:hover, .fp-pager a.activeSlide Ошибка разбора = 100)
787 .fp-prev Свойство opacity не существует в CSS2.1, но существует в [css3] : 0.6
788 .fp-prev Ошибка разбора = 60)
792 .fp-prev:hover Свойство opacity не существует в CSS2.1, но существует в [css3] : 0.8
793 .fp-prev:hover Ошибка разбора = 80)
802 .fp-next Свойство opacity не существует в CSS2.1, но существует в [css3] : 0.6
803 .fp-next Ошибка разбора = 60)
807 .fp-next:hover Свойство opacity не существует в CSS2.1, но существует в [css3] : 0.8
808 .fp-next:hover Ошибка разбора = 80)
891 #credits Свойство opacity не существует в CSS2.1, но существует в [css3] : 0.1px
912 #no_credits Ошибка значения : clear bpth не является значением clear : bpth
1284 .social-profiles-widget img:hover Свойство opacity не существует в CSS2.1, но существует в [css3] : 0.8
1419 Неизвестный псевдоэлемент или псевдокласс :last-child
1429 Неизвестный псевдоэлемент или псевдокласс :last-child
1451 .comment-author Свойство border-radius не существует в CSS2.1, но существует в [css3] : 4px
1466 #author Свойство border-radius не существует в CSS2.1, но существует в [css3] : 4px
1478 #email Свойство border-radius не существует в CSS2.1, но существует в [css3] : 4px
1489 #url Свойство border-radius не существует в CSS2.1, но существует в [css3] : 4px
1505 #submit Свойство border-radius не существует в CSS2.1, но существует в [css3] : 4px
1581 .comment-reply-link Свойство border-radius не существует в CSS2.1, но существует в [css3] : 3px
1746 #back-top a Свойство transition не существует в CSS2.1, но существует в [css3] : 1s
1761 #back-top span Свойство border-radius не существует в CSS2.1, но существует в [css3] : 15px
1764 #back-top span Свойство transition не существует в CSS2.1, но существует в [css3] : 1s
1778 #subscribe_form Свойство border-radius не существует в CSS2.1, но существует в [css3] : 4px
1788 #subscribe_wrapper Свойство border-radius не существует в CSS2.1, но существует в [css3] : 4px
1796 .preload Свойство opacity не существует в CSS2.1, но существует в [css3] : 0.5
1804 #top_of_form Свойство border-radius не существует в CSS2.1, но существует в [css3] : 0 0 0 0
1807 #top_of_form Ошибка значения : background Ошибка разбора
1828 #your_email_input Ошибка значения : background попытка найти точку с запятой до имени свойства. добавьте ее
1848 #bottom_part Свойство border-radius не существует в CSS2.1, но существует в [css3] : 0 0 0 0
1851 #bottom_part Ошибка значения : background попытка найти точку с запятой до имени свойства. добавьте ее
1876 .button_subscribe Свойство border-radius не существует в CSS2.1, но существует в [css3] : 4px
1907 .pages Свойство border-radius не существует в CSS2.1, но существует в [css3] : 3px 3px 3px 3px
1934 span.current Свойство text-shadow не существует в CSS2.1, но существует в [css2, css3] : 0 1px #3C3C3C
1936 span.current Свойство border-radius не существует в CSS2.1, но существует в [css3] : 3px 3px 3px 3px
1937 span.current Свойство background-size не существует в CSS2.1, но существует в [css3] : auto
1944 .navigation a:hover Свойство text-shadow не существует в CSS2.1, но существует в [css2, css3] : 0 1px #3C3C3C
1949 .navigation a:hover Свойство border-radius не существует в CSS2.1, но существует в [css3] : 3px 3px 3px 3px
1950 .navigation a:hover Свойство background-size не существует в CSS2.1, но существует в [css3] : auto
1964 .navigation a, .navigation span.extend Свойство text-shadow не существует в CSS2.1, но существует в [css2, css3] : 0 1px #F6F6F6
1973 .navigation a, .navigation span.extend Свойство border-radius не существует в CSS2.1, но существует в [css3] : 3px 3px 3px 3px
1983 .navigation span.pages Свойство text-shadow не существует в CSS2.1, но существует в [css2, css3] : 0 1px #F6F6F6
URI : http://v-zdor.com/
0 .sr-box-list input[type="text"] Свойство box-sizing не существует в CSS2.1, но существует в [css3] : border-box