Design Audit Checks
Understand the evidence FreeScan looks for, the failures it reports, and the safest way to implement and verify each correction.
Visible Primary CTA Check
Check whether the page presents at least one recognizable primary call to action.
Read methodologyHero Clarity Signals Check
Evaluate whether the page opens with one clear primary heading and a meaningful supporting summary.
Read methodologyText Density Check
Use approximate visible word count as a role-aware context signal, then require review before treating long content as a scanability problem.
Read methodologyTrust Signals Check
Detect role-appropriate credibility, including commercial proof, cited sources, methodology, data provenance, authorship, review dates, audits, and guarantees.
Read methodologyResponsive Viewport Check
Verify that the page declares viewport behavior required for usable mobile rendering.
Read methodologyReadability Signals Check
Measure sentence length within qualifying prose blocks, preserving paragraph boundaries and excluding navigation, bylines, controls, and card labels.
Read methodologySpacing Consistency Check
Look for repeated spacing tokens as preliminary evidence, while reserving incomplete source-only results for visual review.
Read methodologyVisual Hierarchy Check
Compare the browser-rendered H1 size and weight with representative body text, using geometry and computed styles rather than emphasis tags.
Read methodologyRendered Speed Signals Check
Review browser-observed loading milestones, resource volume, scripts, third parties, and transferred data.
Read methodologyRuntime Console Health Check
Detect site-authored console errors and uncaught page errors during the rendered audit.
Read methodologyRendered Layout Ergonomics Check
Measure horizontal overflow and WCAG 2.2 AA target-size failures in the browser-rendered page.
Read methodologyRun the complete design audit
Use these methodology pages as references, then test the current public evidence in one FreeScan report.
Explore the audit tool
