Errors:
Content-Security-Policy HTTP header: Bad content security policy: Expecting directive-name but found "'unsafe-inline'".
Almost standards mode doctype. Expected “<!DOCTYPE html>”.
Internal encoding declaration “iso-8859-1” disagrees with the actual encoding of the document (“utf-8”).
Bad value “text/html; charset=iso-8859-1” for attribute “content” on element “meta”: “charset=” must be followed by “utf-8”.
Self-closing syntax (“/>”) used on a non-void HTML element. Ignoring the slash and treating as a start tag.
An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
Duplicate ID “anything”.
Bad value “wp-video-lightbox” for attribute “rel” on element “a”: The string “wp-video-lightbox” is not a registered keyword.
Element “g:plusone” not allowed as child of element “div” in this context. (Suppressing further errors from this subtree.)
Element “style” not allowed as child of element “div” in this context. (Suppressing further errors from this subtree.)
End of file seen and there were open elements.
Unclosed element “div”.
Warnings:
The “type” attribute is unnecessary for JavaScript resources.
The “type” attribute for the “style” element is not needed and should be omitted.
The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.
The first occurrence of ID “anything” was here.
Element name “g:plusone” cannot be represented as XML 1.0.
This document appears to be written in English. Consider adding “lang="en"” (or variant) to the “html” start tag.
United States US