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
Compare approximate visible word count with the expected range for a general page or long-form article.
Read methodologyTrust Signals Check
Detect visible language commonly associated with proof, policies, support, guarantees, and customer confidence.
Read methodologyResponsive Viewport Check
Verify that the page declares viewport behavior required for usable mobile rendering.
Read methodologyReadability Signals Check
Use average sentence length as a deterministic signal for copy that may be difficult to scan.
Read methodologySpacing Consistency Check
Look for repeated spacing tokens or style signals that suggest a systematic layout rhythm.
Read methodologyVisual Hierarchy Check
Detect headings, calls to action, and emphasized text that establish a perceivable order of importance.
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 undersized tap targets 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
