How it works
Paste a public URL. The form stays on this page. A ?url= query runs the check automatically and can be copied as a link to this result; the canonical URL of this page stays clean, and parameterized URLs are noindexed, so search engines do not index a result per domain. We fetch the HTML, robots.txt, a sitemap lookup, and the http variant for the HTTPS redirect check — at most those four destinations, with a sitemap HEAD then GET fallback. Speed on mobile is a separate Google PageSpeed Insights lab test. Both requests start together. The HTML grade appears first. Speed fills in when the lab run finishes, or shows Not measured if that test cannot run.
The score is points earned divided by points of measured checks, times 100. Unmeasured checks are N/A, not fails. The builder we detect — Wix, Squarespace, WordPress, and the rest — never changes the number. Bands below are our own labels, not Google's: 90–100 Strong; 70–89 Good, with fixes; 50–69 Needs work; below 50 Priority fixes. After a result you can download a PDF report (your browser's print dialog, Save as PDF) and a PNG score card, both watermarked nuvoraweb.com/tools/website-grader. Both are built in the browser. No email, no paid API.
| Category | Weight | What is counted |
|---|---|---|
| Speed on mobile | 30 | 30 × Lighthouse mobile performance / 100. Real-user LCP, INP, and CLS p75 from loadingExperience are info only, and only when Google has field data. |
| Search basics | 25 | Title present 5; meta description 4; exactly one H1 4; indexable (no noindex) 6; canonical 3; html lang 3. |
| Mobile-ready | 15 | Viewport width=device-width 10; zoom not blocked 5. |
| Security | 15 | HTTPS with a valid certificate 8; http→https redirect 5; HSTS 2. |
| Found by Google and AI | 15 | robots.txt reachable and not blocking Googlebot for the whole site 4; sitemap found 4; JSON-LD present 4; Open Graph title and image 3. |
How scoring works
Every check uses the same four statuses. A warning is not a pass: it never awards the full weight of that check.
| Status | Points | When we use it |
|---|---|---|
| Pass | Full published weight | The check is present and inside our guidelines. |
| Warn | Full weight minus 1 (never full points) | The thing exists, but a guideline is off — for example a title shorter than 30 or longer than 60 characters, or a meta description outside 70–160 characters. Those lengths are our guidelines, not Google rules. |
| Fail | 0 | The check is missing or blocked. |
| N/A | Left out of the total | We could not measure it (for example Speed when PageSpeed Insights does not run). Not a fail. |
Grade = (points earned ÷ points of measured checks) × 100, rounded to a whole number. Speed on mobile is the exception to the four statuses: it is a scaled score (30 × Lighthouse mobile performance / 100), not pass/warn/fail.
This grader measures speed, search, mobile, security, and AI-readiness. For tap targets, contrast, proof next to the call to action, and the rest of the design half, use the website design checklist.
AI crawlers (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended) and llms.txt are listed as information. They are not scored. Want the full AI check? Run the AI readiness checker for crawler access, llms.txt, schema and entity clarity. You can also check which builder the site uses or open the website cost calculator.
Moving sites? Check your old URLs with the redirect checker.
What each check means
Speed on mobile is the Lighthouse performance category from PageSpeed Insights, strategy=mobile. That is a lab run on a phone-sized viewport, not a promise of how every visitor experiences the live site. If the lab test is missing or fails, Speed shows Not measured and the grade is re-weighted over the other four categories.
Search basics. A title tag has to exist. Length outside 30–60 characters is a warn (full points minus 1), not a fail (0) and not a pass (full points). The same rule applies to meta descriptions outside 70–160 characters, and to any other check that warns. Those thresholds are guidelines, not Google rules. Exactly one H1 is a pass. Indexable means we did not find noindex in a meta robots tag or an X-Robots-Tag header. Canonical and html lang have to be present.
Mobile-ready looks at the viewport meta tag. width=device-width is required. Zoom is blocked when user-scalable=no or maximum-scale is 1 or below.
Security. HTTPS with a valid certificate means we completed a TLS handshake. The http→https check uses the http twin of the same host, or a redirect we already followed. HSTS is a Strict-Transport-Security header on the HTTPS response. For the certificate itself — trust, names, expiry, and the chain — use the SSL checker.
Found by Google and AI. robots.txt must be reachable and must not Disallow: / for Googlebot (or * if there is no Googlebot group). A sitemap is a robots.txt Sitemap: line or /sitemap.xml. JSON-LD is a script type=application/ld+json that parses; we list the @type values. To write LocalBusiness or Organization markup, use the schema generator. Open Graph needs both og:title and og:image.
Limits
This is a public homepage check, not a crawl of every URL. We do not run JavaScript, so client-rendered titles, tags, and JSON-LD that never appear in the first HTML will look missing. Bot protection, a login wall, or a challenge page will fail the fetch. We only follow public http and https on ports 80 and 443, and we refuse private or metadata addresses. Custom and headless setups can hide builder fingerprints; the Wix / Squarespace checker shows the evidence so you can judge it. We do not store the address you enter. Results stay on this page — there are no indexable per-domain result URLs, and nothing about a result goes in the sitemap. The PDF report uses the browser print dialog; the PNG score card is drawn in this page. Neither asks for an email.
A certificate we cannot validate fails HTTPS. An http address that never redirects to https fails that check; if http does not respond, the redirect is N/A rather than a fail. HSTS is the header on the HTTPS response, not a guess from the certificate.
If you are leaving a builder, the switch from Wix or Squarespace guide covers what you can take with you. The portfolio shows the kind of custom work, labelled as client work or studio concepts.
When Nuvora isn't the right fit
If lowest cash matters and you will design, build, and update the site yourself, a DIY builder is the cheaper path. If you want a one-off brochure you will not change, an entry one-time build is the closer match. Nuvora is for small and growing businesses that want a custom site that does not look average, kept current by a team. Popular is $500/month, first month paid upfront. Start from the contact form if that is the shape of work you need.