Website audit scorecard for getvisibly.app
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
getvisibly.app
Final URL
https://getvisibly.app
Created
Jul 26, 2026, 10:32 PM
Safe fetch
279 ms
81
out of 100
71
out of 100
81/114 rule points
100
out of 100
76/76 rule points
61
out of 100
57/94 rule points
92
out of 100
101/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: aria-prohibited-attr (3), color-contrast (23), heading-order (1), landmark-unique (1).
Heading levels found: 1, 3, 2, 2, 2, 3, 3, 3, 3, 2, 3, 3, 3, 3, 2, 3, 3, 3, 2, 2, 2, 2, 2, 2, 2.
Meta description is 195 characters.
No canonical link tag was detected.
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: aria-prohibited-attr (3), color-contrast (23), heading-order (1), landmark-unique (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 a useful meta description
-10 rule ptsWhat failed
The page does not expose a strong short summary for search and answer engines.
Evidence
Meta description is 195 characters.
Priority
Priority 3: fix before sharing the page publicly.
Why it matters
A missing description makes previews weaker when early users share or find the page.
How to fix it
Add a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.
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
Fix heading order
-11 rule ptsWhat failed
Heading levels appear to jump or start without a clear hierarchy.
Evidence
Heading levels found: 1, 3, 2, 2, 2, 3, 3, 3, 3, 2, 3, 3, 3, 3, 2, 3, 3, 3, 2, 2, 2, 2, 2, 2, 2.
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.
Meta description
-10 rule ptsMeta description is 195 characters.
Canonical tag
-10 rule ptsNo canonical link tag was detected.
Heading structure
-8 rule ptsDetected 1 H1 heading(s) and 25 total headings.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
No failed checks in this category.
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: aria-prohibited-attr (3), color-contrast (23), heading-order (1), landmark-unique (1).
Heading order
-11 rule ptsHeading levels found: 1, 3, 2, 2, 2, 3, 3, 3, 3, 2, 3, 3, 3, 3, 2, 3, 3, 3, 2, 2, 2, 2, 2, 2, 2.
Basic contrast
-8 rule pts8 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 2.56.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Rendered layout ergonomics
-9 rule ptsHorizontal overflow: 0px. Small tap targets: 47.
Showing failed checks.
Failed checks
These checks need attention.
Meta description
0/10Meta description is 195 characters.
Failed: earned 0 of 10 points.
Priority: Priority 3: fix before sharing the page publicly.
Why it matters: A missing description makes previews weaker when early users share or find the page.
Fix: Add a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.
Copyable agent prompt
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
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
Open Graph basics
0/5Detected 0 of 4 Open Graph basics.
Failed: earned 0 of 5 points.
Priority: Priority 18: lower-risk cleanup after urgent launch blockers.
Why it matters: Launch links on X, LinkedIn, Slack, and communities look less trustworthy without a strong preview.
Fix: Add og:title, og:description, og:image, and og:url that match the landing page content.
Copyable agent prompt
Heading order
0/11Heading levels found: 1, 3, 2, 2, 2, 3, 3, 3, 3, 2, 3, 3, 3, 3, 2, 3, 3, 3, 2, 2, 2, 2, 2, 2, 2.
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/88 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 2.56.
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: aria-prohibited-attr (3), color-contrast (23), heading-order (1), landmark-unique (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
Rendered layout ergonomics
0/9Horizontal overflow: 0px. Small tap targets: 47.
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
getvisibly.app website audit report
Close to ready: 81/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.