How ScanoraAI scores your site
No black boxes. We document every data source, every scoring algorithm, and every known limitation. We also run a full audit on our own site every 7 days and publish the results here — including issues we haven't fixed yet.
ScanoraAI audits itself
We run a full ScanoraAI audit on scanoraai.com every 7 days and publish the results here. This includes issues we haven't fixed yet — and why. The honesty is the product.
Live scores will appear here after the first self-audit runs
ScanoraAI runs a full audit on scanoraai.com every 7 days using the same engine you can run on your URL. The first scheduled run happens shortly after launch — until then, this section deliberately shows no scores rather than placeholder zeros, because publishing fake numbers on a transparency page would defeat the purpose.
Want to see what the audit actually outputs in the meantime? Run one on your own site at scanoraai.com — the scoring algorithm, data sources, and report format are identical.
Scoring methodology
Every score is computed from real, third-party-verifiable data. Here's exactly how each category works.
Known limitations
Lab data vs real-user experience
Lighthouse runs in a controlled lab environment (throttled CPU, simulated 4G). Real users on fast connections will see better performance. We show CrUX field data alongside lab data when available so you can compare.
Single-page scan
We audit your homepage (or the URL you provide). Internal pages, blog posts, and product pages may have different scores. A full site audit would require crawling every page.
Server location bias
Our probe server runs from a single region (visible at the top of every audit report — it's detected at runtime, not assumed). Response times and TTFB you see in the report reflect that one vantage point and will differ from what users in other regions experience. Lighthouse and Core Web Vitals run on Google's infrastructure, which is independent of our probe location.
Login-gated pages
We cannot audit pages that require authentication. If your important content is behind a login wall, the audit will only reflect the public-facing pages.
Score variance between runs
Lighthouse scores can naturally vary between runs due to network conditions and server load. We run 5 independent PSI audits and take the median to reduce this variance. The stability panel on your results page shows the score range.
Data retention & privacy
Audit results are stored server-side, keyed by a SHA-256 hash of your URL. No personal data is stored alongside audit results.
We do not store the full HTML of your page — only the extracted signals (title, meta, header counts, etc.).
Audit history is retained for up to 90 days. After that, old records are automatically purged.
We never sell audit data to third parties. Aggregate, anonymised statistics may be used to improve the engine.
The "email when done" feature stores your email only until the audit completes, then it is deleted.
For full details, see our Privacy Policy.