Website audit scorecard for sparqo.ai
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://sparqo.ai/
Final URL
https://sparqo.ai
Created
Jul 18, 2026, 1:47 PM
Safe fetch
172 ms
71
out of 100
93
out of 100
106/114 rule points
62
out of 100
47/76 rule points
61
out of 100
57/94 rule points
67
out of 100
74/110 rule points
Category point breakdown
Biggest score-losing checks
axe found 4 violation rule(s), including 2 serious or critical rule(s). Top rules: color-contrast (13), scrollable-region-focusable (1), heading-order (1), image-redundant-alt (3).
A small allowlist probe returned a public success response.
Detected 2 of 5 common public security headers. Present: x-content-type-options, referrer-policy. Missing: strict-transport-security, content-security-policy, x-frame-options.
Heading levels found: 1, 2, 3, 3, 3, 3, 3, 3, 3, 3, 2, 3, 3, 3, 2, 2, 3, 3, 3, 2, 4, 4, 4, 4, 4.
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 4 violation rule(s), including 2 serious or critical rule(s). Top rules: color-contrast (13), scrollable-region-focusable (1), heading-order (1), image-redundant-alt (3).
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
-13 rule ptsWhat failed
Several basic browser protection headers were not visible.
Evidence
Detected 2 of 5 common public security headers. Present: x-content-type-options, referrer-policy. Missing: strict-transport-security, 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
Fix heading order
-11 rule ptsWhat failed
Heading levels appear to jump or start without a clear hierarchy.
Evidence
Heading levels found: 1, 2, 3, 3, 3, 3, 3, 3, 3, 3, 2, 3, 3, 3, 2, 2, 3, 3, 3, 2, 4, 4, 4, 4, 4.
Priority
Priority 13: fix during launch polish.
Why it matters
A clean heading outline helps visitors scan the page and helps assistive technology navigate it.
How to fix it
Use headings in order: one H1, then H2 for major sections, then H3 for subsections.
Copyable agent prompt
Use one clear H1 and ordered headings
-8 rule ptsWhat failed
The page heading structure is either missing a single main heading or skips heading levels.
Evidence
Detected 1 H1 heading(s) and 25 total headings.
Priority
Priority 9: fix during launch polish.
Why it matters
Clear headings help visitors, search engines, and assistive technology understand the page quickly.
How to fix it
Keep one H1 for the main promise, then use H2 and H3 headings in order for sections below it.
Copyable agent prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 2 low.
Heading structure
-8 rule ptsDetected 1 H1 heading(s) and 25 total headings.
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
-13 rule ptsDetected 2 of 5 common public security headers. Present: x-content-type-options, referrer-policy. Missing: strict-transport-security, 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 4 violation rule(s), including 2 serious or critical rule(s). Top rules: color-contrast (13), scrollable-region-focusable (1), heading-order (1), image-redundant-alt (3).
Heading order
-11 rule ptsHeading levels found: 1, 2, 3, 3, 3, 3, 3, 3, 3, 3, 2, 3, 3, 3, 2, 2, 3, 3, 3, 2, 4, 4, 4, 4, 4.
Basic contrast
-8 rule pts28 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Trust signals
-10 rule ptsDetected 0 trust-signal keyword occurrence(s).
Rendered speed signals
-10 rule ptsDOMContentLoaded: 622ms. Load complete: 1739ms. First contentful paint: 940ms. Resources: 45. Scripts: 5. Images: 29. Third-party origins: 13. Transfer: not available.
Rendered layout ergonomics
-9 rule ptsHorizontal overflow: 0px. Small tap targets: 66.
Showing failed checks.
Failed checks
These checks need attention.
Heading structure
0/8Detected 1 H1 heading(s) and 25 total headings.
Failed: earned 0 of 8 points.
Priority: Priority 9: fix during launch polish.
Why it matters: Clear headings help visitors, search engines, and assistive technology understand the page quickly.
Fix: Keep one H1 for the main promise, then use H2 and H3 headings in order for sections below it.
Copyable agent prompt
Common security headers
5/18Detected 2 of 5 common public security headers. Present: x-content-type-options, referrer-policy. Missing: strict-transport-security, content-security-policy, x-frame-options.
Failed: earned 5 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
Heading order
0/11Heading levels found: 1, 2, 3, 3, 3, 3, 3, 3, 3, 3, 2, 3, 3, 3, 2, 2, 3, 3, 3, 2, 4, 4, 4, 4, 4.
Failed: earned 0 of 11 points.
Priority: Priority 13: fix during launch polish.
Why it matters: A clean heading outline helps visitors scan the page and helps assistive technology navigate it.
Fix: Use headings in order: one H1, then H2 for major sections, then H3 for subsections.
Copyable agent prompt
Basic contrast
0/828 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
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 2 serious or critical rule(s). Top rules: color-contrast (13), scrollable-region-focusable (1), heading-order (1), image-redundant-alt (3).
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
Trust signals
0/10Detected 0 trust-signal keyword occurrence(s).
Failed: earned 0 of 10 points.
Priority: Priority 16: lower-risk cleanup after urgent launch blockers.
Why it matters: Trust signals reduce hesitation when strangers see the product for the first time.
Fix: Add honest proof such as customer quotes, usage stats, founder credibility, security notes, or relevant logos.
Copyable agent prompt
Rendered speed signals
0/10DOMContentLoaded: 622ms. Load complete: 1739ms. First contentful paint: 940ms. Resources: 45. Scripts: 5. Images: 29. Third-party origins: 13. 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 0 console error(s) and 6 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: 66.
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
sparqo.ai website audit report
Close to ready: 71/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.