The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://www.launchpanda.dev/
Final URL
https://www.launchpanda.dev
Created
Jul 3, 2026, 6:11 AM
Safe fetch
130 ms
80
out of 100
87
out of 100
80/92 rule points
96
out of 100
73/76 rule points
61
out of 100
57/94 rule points
76
out of 100
84/110 rule points
Category point breakdown
Biggest score-losing checks
axe found 5 violation rule(s), including 3 serious or critical rule(s). Top rules: button-name (1), aria-prohibited-attr (38), color-contrast (35), heading-order (1), landmark-unique (1).
Heading levels found: 1, 2, 3, 3, 3, 3, 3, 3, 2, 3, 3, 3, 2, 3, 3, 3, 2, 2, 3, 3, 2, 2, 4, 4, 4, 4.
DOMContentLoaded: 1476ms. Load complete: 0ms. First contentful paint: 800ms. Resources: 152. Scripts: 36. Images: 49. Third-party origins: 49. Transfer: not available.
Horizontal overflow: 0px. Small tap targets: 33.
What failed
The rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 5 violation rule(s), including 3 serious or critical rule(s). Top rules: button-name (1), aria-prohibited-attr (38), color-contrast (35), 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.
What failed
Several basic browser protection headers were not visible.
Evidence
Detected 4 of 5 common public security headers. Present: strict-transport-security, content-security-policy, x-content-type-options, referrer-policy. Missing: 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.
What failed
The page heading structure is either missing a single main heading or skips heading levels.
Evidence
Detected 1 H1 heading(s) and 26 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.
What failed
Heading levels appear to jump or start without a clear hierarchy.
Evidence
Heading levels found: 1, 2, 3, 3, 3, 3, 3, 3, 2, 3, 3, 3, 2, 3, 3, 3, 2, 2, 3, 3, 2, 2, 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.
What failed
The browser-rendered page has layout or tap-target issues.
Evidence
Horizontal overflow: 0px. Small tap targets: 33.
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.
This scan did not produce unknown checks. If a future page has partial public data, the report will show those checks here instead of guessing.
Severity mix: 0 critical, 6 high, 3 medium, 2 low.
Detected 1 H1 heading(s) and 26 total headings.
HTTP 404 returned for llms_txt.
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Detected 4 of 5 common public security headers. Present: strict-transport-security, content-security-policy, x-content-type-options, referrer-policy. Missing: x-frame-options.
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
axe found 5 violation rule(s), including 3 serious or critical rule(s). Top rules: button-name (1), aria-prohibited-attr (38), color-contrast (35), heading-order (1), landmark-unique (1).
Heading levels found: 1, 2, 3, 3, 3, 3, 3, 3, 2, 3, 3, 3, 2, 3, 3, 3, 2, 2, 3, 3, 2, 2, 4, 4, 4, 4.
22 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 3.
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
DOMContentLoaded: 1476ms. Load complete: 0ms. First contentful paint: 800ms. Resources: 152. Scripts: 36. Images: 49. Third-party origins: 49. Transfer: not available.
Horizontal overflow: 0px. Small tap targets: 33.
Detected 3 console error(s) and 0 uncaught page error(s) during render.
Showing failed checks.
These checks need attention.
Detected 1 H1 heading(s) and 26 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.
HTTP 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.
Detected 4 of 5 common public security headers. Present: strict-transport-security, content-security-policy, x-content-type-options, referrer-policy. Missing: x-frame-options.
Failed: earned 15 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.
Heading levels found: 1, 2, 3, 3, 3, 3, 3, 3, 2, 3, 3, 3, 2, 3, 3, 3, 2, 2, 3, 3, 2, 2, 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.
22 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 3.
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.
axe found 5 violation rule(s), including 3 serious or critical rule(s). Top rules: button-name (1), aria-prohibited-attr (38), color-contrast (35), 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.
DOMContentLoaded: 1476ms. Load complete: 0ms. First contentful paint: 800ms. Resources: 152. Scripts: 36. Images: 49. Third-party origins: 49. 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.
Detected 3 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.
Horizontal overflow: 0px. Small tap targets: 33.
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.
Security and accessibility checks are basic automated public checks. They are not a complete security audit, penetration test, privacy review, or WCAG certification.
Checked: https://www.launchpanda.dev
Next/final: https://www.launchpanda.dev
Content type: text/html; charset=utf-8
Checked: https://www.launchpanda.dev
Next/final: https://www.launchpanda.dev
Content type: text/html; charset=utf-8
Content hash: b5cf4523fbe934007f214ec440e603bddf21d2fc44f1e882d791fc879c90dcf0
Checked: https://www.launchpanda.dev/robots.txt
Next/final: https://www.launchpanda.dev/robots.txt
Content type: text/plain
Content hash: 7ce9cd011b0df53d5ec5bfd0d9c0429efc05cddfad88070f7c74f58191824920
Checked: https://www.launchpanda.dev/sitemap.xml
Next/final: https://www.launchpanda.dev/sitemap.xml
Content type: application/xml
Content hash: 24fe18cf919764e9068e822ac63f04da03178a73c3d51f9a134e35dd29c9319c
Checked: https://www.launchpanda.dev/llms.txt
Next/final: https://www.launchpanda.dev/llms.txt
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for llms_txt.
Checked: https://www.launchpanda.dev/.env
Next/final: https://www.launchpanda.dev/.env
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Checked: https://www.launchpanda.dev/.git/config
Next/final: https://www.launchpanda.dev/.git/config
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Checked: https://www.launchpanda.dev/wp-config.php
Next/final: https://www.launchpanda.dev/wp-config.php
Content type: text/html; charset=utf-8
Fetch result: HTTP 403 returned for security_probe.
Checked: https://www.launchpanda.dev/backup.zip
Next/final: https://www.launchpanda.dev/backup.zip
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Captured public headers
content-type
text/html; charset=utf-8
referrer-policy
strict-origin-when-cross-origin
permissions-policy
camera=(), microphone=(), geolocation=()
x-content-type-options
nosniff
content-security-policy
frame-ancestors 'self' https://buildhop.io https://*.buildhop.io
strict-transport-security
max-age=63072000; includeSubDomains; preload
Share preview
launchpanda.dev website audit report
Close to ready: 80/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.