Website audit scorecard for zensched.app
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://zensched.app/
Final URL
https://zensched.app
Created
Jul 26, 2026, 4:46 PM
Safe fetch
431 ms
69
out of 100
86
out of 100
98/114 rule points
67
out of 100
51/76 rule points
62
out of 100
58/94 rule points
59
out of 100
65/110 rule points
Category point breakdown
Biggest score-losing checks
axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (20).
A small allowlist probe returned a public success response.
No canonical link tag was detected.
Detected 0 landmark element(s) or roles.
Remove exposed sensitive files
-16 rule ptsWhat failed
A small public allowlist probe found a sensitive-looking file path.
Evidence
A small allowlist probe returned a public success response.
Priority
Priority 1: fix before sharing the page publicly.
Why it matters
Publicly exposed config or backup files can leak implementation details or secrets.
How to fix it
Remove the exposed file, block public access to that path, and rotate any secrets that may have been exposed.
Copyable agent prompt
Fix rendered axe accessibility violations
-18 rule ptsWhat failed
The rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (20).
Priority
Priority 5: fix before sharing the page publicly.
Why it matters
axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
How to fix it
Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.
Copyable agent prompt
Add common public security headers
-9 rule ptsWhat failed
Several basic browser protection headers were not visible.
Evidence
Detected 3 of 5 common public security headers. Present: strict-transport-security, x-content-type-options, referrer-policy. Missing: content-security-policy, x-frame-options.
Priority
Priority 5: fix before sharing the page publicly.
Why it matters
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
How to fix it
Configure headers such as Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.
Copyable agent prompt
Add a canonical URL
-10 rule ptsWhat failed
The page does not declare which public URL is the preferred version.
Evidence
No canonical link tag was detected.
Priority
Priority 9: fix during launch polish.
Why it matters
A canonical tag reduces duplicate URL confusion before marketing links start spreading.
How to fix it
Add a canonical link tag that points to the final public landing page URL.
Copyable agent prompt
Strengthen visual hierarchy
-9 rule ptsWhat failed
The page does not expose enough hierarchy signals from headings, emphasis, or CTA structure.
Evidence
Detected 2 hierarchy signal(s) from headings, CTA, and emphasized text.
Priority
Priority 12: fix during launch polish.
Why it matters
Hierarchy tells visitors what to read first and what action to take next.
How to fix it
Create a clear H1, supportive section headings, emphasized proof, and one visually prominent primary CTA.
Copyable agent prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 2 low.
Canonical tag
-10 rule ptsNo canonical link tag was detected.
Internal link basics
-6 rule ptsDetected 1 internal link(s).
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Sensitive file probes
-16 rule ptsA small allowlist probe returned a public success response.
Common security headers
-9 rule ptsDetected 3 of 5 common public security headers. Present: strict-transport-security, x-content-type-options, referrer-policy. Missing: content-security-policy, x-frame-options.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Rendered axe accessibility violations
-18 rule ptsaxe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (20).
Landmark presence
-10 rule ptsDetected 0 landmark element(s) or roles.
Basic contrast
-8 rule pts2 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.6.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Text density
-10 rule ptsDetected about 54 visible word(s).
Rendered speed signals
-10 rule ptsDOMContentLoaded: 1151ms. Load complete: 0ms. First contentful paint: 1124ms. Resources: 34. Scripts: 2. Images: 26. Third-party origins: 29. Transfer: not available.
Visual hierarchy
-9 rule ptsDetected 2 hierarchy signal(s) from headings, CTA, and emphasized text.
Showing failed checks.
Failed checks
These checks need attention.
Canonical tag
0/10No canonical link tag was detected.
Failed: earned 0 of 10 points.
Priority: Priority 9: fix during launch polish.
Why it matters: A canonical tag reduces duplicate URL confusion before marketing links start spreading.
Fix: Add a canonical link tag that points to the final public landing page URL.
Copyable agent prompt
Internal link basics
0/6Detected 1 internal link(s).
Failed: earned 0 of 6 points.
Priority: Priority 16: lower-risk cleanup after urgent launch blockers.
Why it matters: Internal links help visitors find pricing, docs, contact, legal, or product details without getting stuck.
Fix: Add clear public links such as pricing, docs, contact, privacy, terms, or product detail pages where appropriate.
Copyable agent prompt
Common security headers
9/18Detected 3 of 5 common public security headers. Present: strict-transport-security, x-content-type-options, referrer-policy. Missing: content-security-policy, x-frame-options.
Failed: earned 9 of 18 points from partial coverage.
Priority: Priority 5: fix before sharing the page publicly.
Why it matters: These headers reduce avoidable browser-side risk and show a baseline of care before launch.
Fix: Configure headers such as Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.
Copyable agent prompt
Sensitive file probes
0/16A small allowlist probe returned a public success response.
Failed: earned 0 of 16 points.
Priority: Priority 1: fix before sharing the page publicly.
Why it matters: Publicly exposed config or backup files can leak implementation details or secrets.
Fix: Remove the exposed file, block public access to that path, and rotate any secrets that may have been exposed.
Copyable agent prompt
Landmark presence
0/10Detected 0 landmark element(s) or roles.
Failed: earned 0 of 10 points.
Priority: Priority 18: lower-risk cleanup after urgent launch blockers.
Why it matters: Landmarks make the page easier to navigate for assistive technology and keyboard users.
Fix: Use semantic elements such as header, nav, main, and footer around the appropriate page areas.
Copyable agent prompt
Basic contrast
0/82 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.6.
Failed: earned 0 of 8 points.
Priority: Priority 20: lower-risk cleanup after urgent launch blockers.
Why it matters: Low contrast makes a launch page feel less polished and can exclude users with low vision.
Fix: Review key text, buttons, and links against a 4.5:1 contrast target for normal text.
Copyable agent prompt
Rendered axe accessibility violations
0/18axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (20).
Failed: earned 0 of 18 points.
Priority: Priority 5: fix before sharing the page publicly.
Why it matters: axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
Fix: Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.
Copyable agent prompt
Text density
0/10Detected about 54 visible word(s).
Failed: earned 0 of 10 points.
Priority: Priority 21: lower-risk cleanup after urgent launch blockers.
Why it matters: Too little copy can leave visitors confused; too much copy can bury the value proposition.
Fix: Add concise sections for value, proof, how it works, and next steps, then remove repetitive copy.
Copyable agent prompt
Visual hierarchy
0/9Detected 2 hierarchy signal(s) from headings, CTA, and emphasized text.
Failed: earned 0 of 9 points.
Priority: Priority 12: fix during launch polish.
Why it matters: Hierarchy tells visitors what to read first and what action to take next.
Fix: Create a clear H1, supportive section headings, emphasized proof, and one visually prominent primary CTA.
Copyable agent prompt
Rendered speed signals
0/10DOMContentLoaded: 1151ms. Load complete: 0ms. First contentful paint: 1124ms. Resources: 34. Scripts: 2. Images: 26. Third-party origins: 29. Transfer: not available.
Failed: earned 0 of 10 points.
Priority: Priority 14: fix during launch polish.
Why it matters: Slow pages lose impatient visitors and make every SEO, social, and paid-traffic visit work harder.
Fix: Reduce render-blocking scripts/styles, compress and size images, defer non-critical JavaScript, reduce third-party tags, and keep above-the-fold content quick to paint.
Copyable agent prompt
Runtime console health
0/7Detected 1 console error(s) and 0 uncaught page error(s) during render.
Failed: earned 0 of 7 points.
Priority: Priority 15: fix during launch polish.
Why it matters: Runtime errors can break forms, CTAs, animations, tracking, or responsive behavior even when the static HTML looks fine.
Fix: Open the page in a browser, reproduce the console errors, and fix missing assets, hydration problems, client-side exceptions, or failing third-party scripts.
Copyable agent prompt
Rendered layout ergonomics
0/9Horizontal overflow: 0px. Small tap targets: 62.
Failed: earned 0 of 9 points.
Priority: Priority 13: fix during launch polish.
Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
Fix: Remove elements wider than the viewport, add responsive constraints, and make important links, buttons, inputs, and controls at least 40px tall and wide where possible.
Copyable agent prompt
Share preview
zensched.app website audit report
Needs fixes before launch: 69/100 overall, with prioritized fixes for SEO, security, accessibility, and design.
Public reports expose the scanned public URL, safe scores, sanitized public evidence, and fix guidance. They do not include credentials, cookies, hidden form values, or sensitive response bodies.