How scores are calculated
Every report gives six 0–100 scores plus an overall letter grade. Here's exactly what each one measures.
Grade scale
A+ 90+ · A 80+ · B 70+ · C 55+ · D 40+ · F below 40
SEO
On-page fundamentals: title tag, meta description, a single H1, canonical URL, Open Graph tags, sitemap.xml, robots.txt, image alt text, internal links, and structured data.
AI Visibility (AEO)
How citable the page is to AI answer engines: Organization & FAQ schema, clear descriptive content, brand/About identity, authorship & dates, heading structure, external citations, and industry/location info.
Schema
Breadth of JSON-LD structured data: Organization, FAQPage, LocalBusiness, Article/Product, Breadcrumb, and author/date markup.
Technical
Crawlability & hygiene: robots.txt, sitemap.xml, canonical, mobile viewport, language attribute, Open Graph, and sensible title/description lengths (measured by visual width so CJK isn't penalized).
Speed
Measured from our own server-side request to your homepage: time to first byte, how long the HTML takes to arrive, its uncompressed size, whether compression and caching headers are set, how many render-blocking scripts and stylesheets sit in <head>, and whether images are lazy-loaded with explicit dimensions. This is a lab proxy, not field Core Web Vitals — it will not exactly match a Lighthouse or PageSpeed Insights run, which measures a full browser render from a different network location.
Security
Transport and header hygiene: HTTPS, whether http:// redirects to https, TLS certificate expiry, HSTS, Content-Security-Policy, X-Content-Type-Options, clickjacking protection (X-Frame-Options or CSP frame-ancestors), Referrer-Policy, Permissions-Policy, insecure http:// resources on an HTTPS page, and whether the Server / X-Powered-By headers leak a version number. This is not a penetration test — it checks what any visitor's browser can see.
Our crawler
A report is built from one request to a site's homepage, plus small probes for robots.txt, sitemap.xml and the TLS certificate. We fetch the homepage only — we don't crawl deeper, and we don't try to get around bot protection: an HTTP 403 or 429 is reported as a refusal rather than retried through a headless browser.
Mozilla/5.0 (compatible; ELabStudioBot/1.0; +https://elab-studio.com/methodology)
We read robots.txt before fetching anything else and obey it. To keep us out entirely, add this to yours — it takes effect on the next check, with nothing to request from us:
User-agent: ELabStudioBot Disallow: /
robots.txt stops future checks but doesn't remove a report that already exists. For that, ask us directly: Request report removal
Scores are computed from publicly fetched HTML and are heuristic — a fast directional signal, not a ranking guarantee.