live scan // request-level evidence

See everything your website is hiding.

One scan traces the request, reads the markup and probes the server. 150+ checks across SEO, speed, security and accessibility, each with the evidence and the fix.

try //
checks
150+
median run
<5s
pricing
Free
https://your-site.com
TLS 1.3 · h2
Build faster websites
h1 ✓
hero-dashboard.png
24 imgs without size
Trusted by 4,000 teams
contrast 3.1:1
755 KB blocking
no CSP

87

grade B

// 9 modules · 150+ checks · 100 points

Every layer of the stack, weighted into one score.

Each module owns a fixed share of the 100 points, so a missing security header can’t hide behind a fast page.

18

pts // seo

SEO

weight 18%

Crawlability, metadata and on-page structure that search engines index and rank.

  • › title + meta
  • › canonical
  • › robots.txt
  • › sitemap.xml
  • › schema.org
  • › internal links

// pipeline

Measured, never guessed.

Each stage collects evidence the next one scores, so every line in a report traces back to something the engine actually observed.

  1. 01

    Trace

    A real HTTP client times DNS, TCP, TLS, first byte and download, and follows every redirect.

    $ dns 12ms · tls 41ms · ttfb 118ms

  2. 02

    Parse

    The HTML becomes a full document model. Critical CSS, JS, images and fonts are fetched and weighed.

    $ 214 KB html · 38 assets sampled

  3. 03

    Probe

    robots.txt, sitemaps, the manifest, source maps, DNS records and the TLS certificate, inspected directly.

    $ sitemap 398 urls · cert 89d left

  4. 04

    Score

    Every rule returns a score, a severity, its evidence and a fix, weighted into one grade.

    $ 150+ checks → 87 / B

// faq

Before you scan

What to know before pointing the engine at a production site.

Do I need an API key or an account?

No. Scans are free and there are no accounts. The engine uses Node’s own HTTP client, DNS resolver and TLS stack, so it doesn’t depend on a third-party scanner. When Google PageSpeed Insights is available, reports also include Lighthouse lab data and CrUX field data.

How accurate are the Core Web Vitals numbers?

Field data only comes from Google. Without an API key, LCP, INP and CLS are modelled from the live request trace plus render-blocking and layout-shift analysis, scaled for a mid-range phone on mobile data. Reports always say which values are modelled and which are measured.

Can I audit any website?

Any public http or https address. Local, loopback and private network addresses are refused so the auditor can’t be pointed at internal systems. Audits are limited to 2 per minute per visitor.

Where are reports stored, and who can see them?

In a Postgres database hosted by Neon. Each report gets a random link, and anyone with that link can open, download, re-run or delete it. The most recent reports are also listed on this page. Reports stay until someone deletes them; the Privacy Policy has the details.

Can I get the raw data?

Yes. Every report can be downloaded as JSON with all findings, response headers, DNS records, the certificate, the sampled resources and, when configured, the full Lighthouse result.

Does it change anything on my site?

Never. The auditor only sends GET requests, behaves like a polite crawler and reports what it sees.

Run your first scan.

Paste any URL. A full report with every check, its evidence and the fix, in seconds.