Website audit scorecard for saddlebrown-wren-127025.hostingersite.com
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://saddlebrown-wren-127025.hostingersite.com/
Final URL
https://saddlebrown-wren-127025.hostingersite.com
Created
Jul 8, 2026, 12:34 AM
Safe fetch
114 ms
78
out of 100
86
out of 100
98/114 rule points
84
out of 100
64/76 rule points
57
out of 100
54/94 rule points
83
out of 100
91/110 rule points
Category point breakdown
Biggest score-losing checks
axe found 4 violation rule(s), including 3 serious or critical rule(s). Top rules: aria-prohibited-attr (10), color-contrast (20), scrollable-region-focusable (1), region (1).
Detected labels or accessible names for 10 of 13 form control(s).
HTTP 404 returned for sitemap_xml.
Detected 1 of 5 common public security headers. Present: content-security-policy. Missing: strict-transport-security, x-content-type-options, x-frame-options, referrer-policy.
Fix rendered axe accessibility violations
-18 rule ptsWhat failed
The rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 4 violation rule(s), including 3 serious or critical rule(s). Top rules: aria-prohibited-attr (10), color-contrast (20), scrollable-region-focusable (1), region (1).
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
-12 rule ptsWhat failed
Several basic browser protection headers were not visible.
Evidence
Detected 1 of 5 common public security headers. Present: content-security-policy. Missing: strict-transport-security, x-content-type-options, x-frame-options, referrer-policy.
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
Label public form fields
-14 rule ptsWhat failed
Some form controls do not have a detectable label or accessible name.
Evidence
Detected labels or accessible names for 10 of 13 form control(s).
Priority
Priority 7: fix during launch polish.
Why it matters
Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
How to fix it
Connect each input to a visible label or an accurate aria-label/aria-labelledby value.
Copyable agent prompt
Publish a valid sitemap.xml
-12 rule ptsWhat failed
The sitemap file was not reachable or did not look like valid sitemap XML.
Evidence
HTTP 404 returned for sitemap_xml.
Priority
Priority 7: fix during launch polish.
Why it matters
A sitemap helps search engines discover the landing page and related public pages sooner.
How to fix it
Add a static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.
Copyable agent prompt
Fix rendered layout ergonomics
-9 rule ptsWhat failed
The browser-rendered page has layout or tap-target issues.
Evidence
Horizontal overflow: 0px. Small tap targets: 30.
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.
How to fix it
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
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 2 low.
sitemap.xml validity
-12 rule ptsHTTP 404 returned for sitemap_xml.
LLM-readable file
-4 rule ptsHTTP 404 returned for llms_txt.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Common security headers
-12 rule ptsDetected 1 of 5 common public security headers. Present: content-security-policy. Missing: strict-transport-security, x-content-type-options, x-frame-options, referrer-policy.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Rendered axe accessibility violations
-18 rule ptsaxe found 4 violation rule(s), including 3 serious or critical rule(s). Top rules: aria-prohibited-attr (10), color-contrast (20), scrollable-region-focusable (1), region (1).
Form labels
-14 rule ptsDetected labels or accessible names for 10 of 13 form control(s).
Basic contrast
-8 rule pts26 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.07.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Text density
-10 rule ptsDetected about 2948 visible word(s).
Rendered layout ergonomics
-9 rule ptsHorizontal overflow: 0px. Small tap targets: 30.
Showing failed checks.
Failed checks
These checks need attention.
sitemap.xml validity
0/12HTTP 404 returned for sitemap_xml.
Failed: earned 0 of 12 points.
Priority: Priority 7: fix during launch polish.
Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.
Fix: Add a static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.
Copyable agent prompt
LLM-readable file
0/4HTTP 404 returned for llms_txt.
Failed: earned 0 of 4 points.
Priority: Priority 24: lower-risk cleanup after urgent launch blockers.
Why it matters: A short LLM-readable file can help answer engines and AI tools summarize your product accurately.
Fix: Add /llms.txt or /.well-known/llms.txt with the product name, audience, value proposition, and key public links.
Copyable agent prompt
Common security headers
6/18Detected 1 of 5 common public security headers. Present: content-security-policy. Missing: strict-transport-security, x-content-type-options, x-frame-options, referrer-policy.
Failed: earned 6 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
Form labels
0/14Detected labels or accessible names for 10 of 13 form control(s).
Failed: earned 0 of 14 points.
Priority: Priority 7: fix during launch polish.
Why it matters: Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
Fix: Connect each input to a visible label or an accurate aria-label/aria-labelledby value.
Copyable agent prompt
Basic contrast
0/826 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.07.
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 4 violation rule(s), including 3 serious or critical rule(s). Top rules: aria-prohibited-attr (10), color-contrast (20), scrollable-region-focusable (1), region (1).
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 2948 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
Rendered layout ergonomics
0/9Horizontal overflow: 0px. Small tap targets: 30.
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
saddlebrown-wren-127025.hostingersite.com website audit report
Close to ready: 78/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.