QA engineering tools,
not another dashboard.

Most site-quality tools sell you a place to look at your problems. You get a login, a graph that trends sideways, a weekly digest you stop reading in a month, and a number that goes up when someone else fixes something. The work of finding out what is actually wrong gets replaced by the work of maintaining an account.

The scanner is the opposite bet. You paste a URL, wait about twenty seconds, and get a list of specific, named defects with a severity on each one. No signup. Nothing to configure. If the list is empty, you close the tab and get on with your day — and that is a good outcome, not a failed conversion.

A scan reads the page you enter and asks Google’s PageSpeed Insights to render it, which is where the Core Web Vitals and the phone-viewport verdicts come from — their Lighthouse run, on their hardware, reproducible at pagespeed.web.dev. Alongside that it requests outbound links directly to see which ones are dead, reads the response headers, inspects the TLS certificate, and checks the domain’s SPF and DMARC records. Unlock a crawl and a real headless browser walks up to ten more pages. Fifty-eight assertions in total.

Then it subtracts. Every site starts at 100 and each finding costs points by severity. There is no curve. A site that scores 62 has, quite literally, thirty-eight points of named damage you can read line by line.