Androidpcreview.com W3C HTML Markup Validation
HTML markup errors and warnings
(Rescan now...)
Errors:
Bad value “https://api.w.org/” for attribute “rel” on element “link”: The string “https://api.w.org/” is not a registered keyword.
“"” in an unquoted attribute value. Probable causes: Attributes running together or a URL query string in an unquoted attribute value.
“=” in an unquoted attribute value. Probable causes: Attributes running together or a URL query string in an unquoted attribute value.
Bad value “\"https://www.googletagmanager.com/gtag/js?id=UA-42470749-1\"” for attribute “src” on element “script”: Backslash ("\") used as path segment delimiter.
Bad value “\\\\\\\\\\\\\\\"fb:app_id\\\\\\\\\\\\\\\"” for attribute “property” on element “meta”: The string “\\\\\\\\\\\\\\\"fb:app_id\\\\\\\\\\\\\\\"” is not an absolute URL.
Element “meta” is missing one or more of the following attributes: “charset”, “content”, “http-equiv”, “itemprop”, “name”, “property”.
Attribute “pagespeed_no_defer” not allowed on element “script” at this point.
Element “p” not allowed as child of element “h1” 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.)
Element “script” must not have attribute “async” unless attribute “src” is also specified.
Bad value “\\\\\\\"//z-na.amazon-adsystem.com/widgets/onejs?MarketPlace=US&adInstanceId=a687c207-9d1f-42dc-967b-978487e9b046\\\\\\\"” for attribute “src” on element “script”: Backslash ("\") used as path segment delimiter.
Warnings:
Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.
Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).
United States US