This is a real audit of test.scanoraai.com run through our own engine on May 28, 2026 — the same engine, same data sources, same scoring you get when you audit any site here. Every score links to the source provider so you can verify it independently. Verified findings (measured data) and AI explanations (generated text) are clearly labelled throughout.
test.scanoraai.com (the engine's pre-launch staging host) but the page's canonical URL points to scanoraai.com (the apex). Lighthouse correctly flags this as “page is canonicalized to a different URL,” which costs ~30 SEO points. After DNS cutover the audited host and the canonical match, and we'll re-run this audit and update the numbers. Both subdomains serve the identical build — robots.txt is fully crawl-allowed, meta robots is index, follow, this is a canonical-pointer artifact only.Performance score is lower than other categories — the large JS bundle is the primary driver. This is a known issue we are actively working on. See findings below.
Performance 78 (median of 5 runs, range 74–81) — large JS bundle and render-blocking resources identified
Performance 61 (median of 5 runs, range 54–68, confidence: medium) — mobile lower due to large JS payload + LCP image
Site does not yet meet CrUX origin sample threshold; relying on lab data only
Color contrast on muted text, missing aria-label on icon buttons. Manual review still required.
CSP present, HSTS enabled, COOP/COEP headers enforce full cross-origin isolation.
TLS 1.3, valid certificate, HSTS enabled
No malware or phishing signals
Duplicate id attributes in SSR output
Slightly above the 0.36 g global average — large JS bundle is the main driver. Hosted on renewable infrastructure (partial offset).
React 19, Vite, Tailwind CSS, Node.js/Express — server-side probe only (no JS execution)
Single H1, meta description present, canonical set, no thin content
WebApplication, HowTo, FAQPage, Organization — all required properties present
robots.txt valid, sitemap.xml reachable, no crawl-delay issues
SPF, DMARC, MX, CAA, AAAA all resolve via Cloudflare/Google DoH — sending-domain verifiability OK
archive.org CDX — domain age and change cadence; not a brand-new or stale-archive domain
Hero image missing fetchpriority="high"; 3 below-fold images missing loading="lazy"
No orphan pages on the homepage crawl sample; hub-page identified (/methodology, 14 inbound links)
Mobile shows a 14-point spread (54–68) — typical for sites where TTI is sensitive to network throttling variance. Confidence is medium; we recommend re-running on PageSpeed Insights to confirm the median before optimising. Desktop is tighter (74–81) and stable.
One upstream issue can affect many findings. The engine groups them so you fix the root once and resolve cascading impacts — and so you aren't double-penalised in the score for the same underlying problem.
Impacts: LCP · TBT · Mobile performance · Carbon footprint · Transfer size
A single root issue — the 1.4 MB main bundle — affects multiple findings. The engine flags this group so you fix it once and resolve cascading impacts. Followers contribute reduced penalty to avoid double-counting.
How to read evidence labels — every finding answers “how was this produced?”
Hover any label to see its definition. AI-explained text is never the source of a score — only of the prose around it.
Same 18 sources. Same verified findings. Same AI-explained fixes. No account, no card.
Audit My Site Free →Results in 30 seconds to 5 minutes · No signup · No credit card