Paste your address and get an instant report card on speed, mobile, SEO, structured data, security, and AI-readiness, with the plain-English fix for everything that's costing you customers.
A pretty website isn’t the same as an effective one. This report card grades the things that determine whether you get found, trusted, and chosen: speed, mobile, SEO, structured data, security, and AI-readiness. Each one is a lever that affects rankings and conversions.
Performance: fast sites rank and convert better. Mobile: most local searches are on phones. SEO: titles, descriptions, and headings tell Google what each page is. Structured data: schema helps search and AI understand you. Security: HTTPS is table stakes for trust. AI readiness: can AI engines find and cite you. A weak grade in any one quietly costs you customers.
Use the fixes as a prioritized to-do list, the failing items are where you’re losing the most. Many are quick (add a meta description, enable compression, add schema). Some, like a slow page-builder site, point to a deeper fix: a fast, custom-coded foundation that passes all six by design.
Submit an address and the page is fetched once, server-side, the way a crawler receives it. Two more files are pulled from the same domain: robots.txt and llms.txt. Everything in the report comes out of those three responses. Six categories are scored from a short list of specific checks. Performance reads render-blocking scripts and stylesheets in the head, the size of the HTML document, and page-builder fingerprints in the markup. Mobile reads the viewport tag and the share of images carrying alt text. SEO reads title length, meta description length, H1 count, and any noindex tag. Structured data looks for JSON-LD, for LocalBusiness or Organization schema, and for Open Graph tags. Security is HTTPS. AI readiness looks for an llms.txt file, for machine-readable markup, and for robots.txt rules blocking GPTBot, ClaudeBot, PerplexityBot, or Google-Extended.
Every check is a pass, a warning worth half, or a fail. A category score is the average of its own checks, and the overall score is a plain average of the six categories, not a weighted one. Two consequences are worth knowing. Security rests on one check, so it is all or nothing. Performance always includes an informational item pointing you at Google PageSpeed, counted as a warning, which holds that category below an A by design. Each address is also cached for 24 hours, so a re-grade immediately after a change can return the earlier result.
The limits are wide. It reads one page, not your whole site, and only the HTML your server sends, so anything painted in afterward by JavaScript looks missing. It does not run Lighthouse or measure real load time: performance here is a structural estimate, and the official number is behind the link it hands you. Mobile is inferred from a viewport tag and alt text coverage, not from a render on an actual phone. It has no view of your rankings, traffic, backlinks, reviews, Analytics, Search Console, or Google Business Profile, and no idea who your competitors are. Two of the fixes it hands back have free tools of their own, the local schema generator and the llms.txt generator. If you would rather have a person walk the list with you, the free audit is here.
Because the category includes an item that is not really a test: a link out to Google's own PageSpeed check. It counts as a warning, since the tool has not measured your load time, and that pulls the average down even on a clean page. The real performance checks are structural: render-blocking files in the head, the size of the HTML document, and whether the markup carries a page-builder signature. For an actual Lighthouse score, follow the PageSpeed link in your result.
Each address is cached for 24 hours after it is graded, so a re-run inside that window returns the stored result instead of a fresh fetch. Wait a day and grade it again. If the grade still has not moved, check whether the change is in the HTML your server sends or only in what the browser assembles afterward, because the grader reads the served HTML and nothing else.