Website audit scorecard for snapsub.super.site
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
SnapSub.super.site
Final URL
https://snapsub.super.site
Created
Jul 3, 2026, 9:24 PM
Safe fetch
69 ms
68
out of 100
45
out of 100
41/92 rule points
82
out of 100
62/76 rule points
81
out of 100
76/94 rule points
65
out of 100
71/110 rule points
Category point breakdown
Biggest score-losing checks
axe found 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (2), region (1), image-redundant-alt (1).
Detected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
Detected 2 H1 heading(s) and 132 meta-description characters.
Title is 7 characters.
Add common public security headers
-14 rule ptsWhat failed
Several basic browser protection headers were not visible.
Evidence
Detected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, 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.
Fix rendered axe accessibility violations
-18 rule ptsWhat failed
The rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (2), region (1), image-redundant-alt (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.
Remove noindex signals
-9 rule ptsWhat failed
The page appears to tell crawlers not to index it.
Evidence
A noindex directive was detected.
Priority
Priority 2: fix before sharing the page publicly.
Why it matters
A noindex directive can prevent the launch page from appearing in search results.
How to fix it
Remove noindex from meta robots or X-Robots-Tag headers once the page is ready to be public.
Clarify the hero promise
-13 rule ptsWhat failed
The hero area does not provide enough clear product context.
Evidence
Detected 2 H1 heading(s) and 132 meta-description characters.
Priority
Priority 6: fix during launch polish.
Why it matters
Visitors decide quickly whether the product is relevant; a vague hero weakens every acquisition channel.
How to fix it
Use one clear H1 plus supporting copy that names the audience, problem, and outcome.
Write a clear page title
-10 rule ptsWhat failed
The browser title is missing, too short, or too long for a reliable search result headline.
Evidence
Title is 7 characters.
Priority
Priority 8: fix during launch polish.
Why it matters
Search engines, social previews, and saved browser tabs use the title to tell people what your product is.
How to fix it
Set one concise title tag, ideally 10 to 70 characters, that includes the product name and the main promise.
SEO / AEO
Severity mix: 0 critical, 6 high, 3 medium, 2 low.
Page title
-10 rule ptsTitle is 7 characters.
Canonical tag
-10 rule ptsNo canonical link tag was detected.
Schema presence
-10 rule ptsDetected 0 JSON-LD schema block(s).
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Common security headers
-14 rule ptsDetected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, 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 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (2), region (1), image-redundant-alt (1).
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Hero clarity signals
-13 rule ptsDetected 2 H1 heading(s) and 132 meta-description characters.
Trust signals
-10 rule ptsDetected 0 trust-signal keyword occurrence(s).
Rendered layout ergonomics
-9 rule ptsHorizontal overflow: 0px. Small tap targets: 3.
Showing failed checks.
Failed checks
These checks need attention.
Page title
0/10Title is 7 characters.
Failed: earned 0 of 10 points.
Priority: Priority 8: fix during launch polish.
Why it matters: Search engines, social previews, and saved browser tabs use the title to tell people what your product is.
Fix: Set one concise title tag, ideally 10 to 70 characters, that includes the product name and the main promise.
Heading structure
0/8Detected 2 H1 heading(s) and 3 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.
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.
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.
Schema presence
0/10Detected 0 JSON-LD schema block(s).
Failed: earned 0 of 10 points.
Priority: Priority 12: fix during launch polish.
Why it matters: Structured data gives search and answer engines explicit facts about your product.
Fix: Add JSON-LD for SoftwareApplication, Product, Organization, or WebSite using only accurate public facts.
Indexability signals
0/9A noindex directive was detected.
Failed: earned 0 of 9 points.
Priority: Priority 2: fix before sharing the page publicly.
Why it matters: A noindex directive can prevent the launch page from appearing in search results.
Fix: Remove noindex from meta robots or X-Robots-Tag headers once the page is ready to be public.
Common security headers
4/18Detected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
Failed: earned 4 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.
Rendered axe accessibility violations
0/18axe found 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (2), region (1), image-redundant-alt (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.
Hero clarity signals
0/13Detected 2 H1 heading(s) and 132 meta-description characters.
Failed: earned 0 of 13 points.
Priority: Priority 6: fix during launch polish.
Why it matters: Visitors decide quickly whether the product is relevant; a vague hero weakens every acquisition channel.
Fix: Use one clear H1 plus supporting copy that names the audience, problem, and outcome.
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.
Spacing consistency
0/7Detected 0 spacing class/style signal(s).
Failed: earned 0 of 7 points.
Priority: Priority 25: lower-risk cleanup after urgent launch blockers.
Why it matters: Consistent spacing helps the page feel deliberate and easier to scan.
Fix: Use consistent section padding, gaps, and margins across repeated content blocks.
Rendered layout ergonomics
0/9Horizontal overflow: 0px. Small tap targets: 3.
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.
Share preview
snapsub.super.site website audit report
Needs fixes before launch: 68/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.