Security and technical hygiene
HTTPS and Lighthouse best-practices checks.
What it tells you
Part of site health. These checks read whether pages are served securely and built with sound, current markup.
Checks
Character-encoding meta tag present
No character-encoding meta tag. Most servers declare the encoding in the HTTP header, which is what actually takes effect.
Read the documentation ›Consistent character encoding
The page declares two different character encodings in its meta tags. The browser picks one, so the other's text can render as mojibake.
Read the documentation ›DOCTYPE present
No DOCTYPE declaration, which puts browsers into quirks mode. Rendering may differ from what the page intends, though parsing still works.
Read the documentation ›HTTPS enabled
Served over plain HTTP. Browsers mark it insecure and it is ranked below the HTTPS equivalent.
Read the documentation ›No mixed content
A secure page loads or links insecure HTTP resources. Browsers block this content, so parts of the page genuinely fail to load.
Read the documentation ›No deprecated HTML tags
The page uses HTML tags that are no longer part of the standard. Browsers still render them, so this is maintenance debt.
Read the documentation ›Best-practices score
The Lighthouse best-practices score for this page is below 90. This is a summary, the individual audits are listed as their own findings.
Read the documentation ›Seen in the app on: Technical Audit
See how the brand's site does on these checks.Related guides
- How the audit score is built
One score out of 100 for the brand's site: how well AI models can reach and read it, and how sound it is, with AI readability counting most.
- AI readability and site health
AI readability is whether AI models can reach and understand the brand's pages; site health is how fast, safe and sound they are.
Still stuck? Contact support ›