slop auditFind what breaks before launch.
Scan your website and get scores, evidence, and fixes.
JavaScript is required to start an interactive scan. No credentials are requested.
Review an example report →A report with scores and fixes.
Scores use measured checks, estimates, coverage, and recommended fixes.
- Production Readiness: how well the page loads, works, explains itself, and shows trust information.
- Slop Risk: a separate score for generic copy, weak proof, template patterns, and unfinished parts.
- Fixes with details: each warning names the observation, impact, source, and concrete next fix.
One URL. Four types of checks.
Each result shows checks, estimates, coverage, and the next fix. Checks that cannot run are labeled.
- Reachability, headers, metadata, robots, sitemap, and links.
- Mobile and desktop layout, focus, tap targets, console, and performance clues.
- Product clarity, action clarity, trust, and machine-readable context.
- Production Readiness, Slop Risk, evidence, and fixes with details.
What the audit does not check.
Does it need credentials?
No. Submit a public URL only. The audit does not request credentials or try to bypass access controls.
Is Slop Risk an authorship detector?
No. It describes observable page patterns and does not identify who wrote a page.
What if a check cannot run?
The report labels it unable to test and keeps coverage visible instead of silently turning missing measurement into a failure.
Not an authorship detector.
Slop Audit reports what a public page makes visible. It does not claim to identify who wrote it, certify security, or replace a full accessibility or performance program.
Read how the audit works →