Loading scan status...
completed
HTTP 200
0 redirects
36 checks
Website audit scorecard for launchpanda.dev
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
Four-score result
Close to ready (Needs polish): 27 passed, 9 failed, and 0 unknown. Strongest area: Security. Weakest area: Accessibility.
Overall
80
out of 100
SEO / AEO
87
out of 100
80/92 rule points
Security
96
out of 100
73/76 rule points
Accessibility
61
out of 100
57/94 rule points
Design
76
out of 100
84/110 rule points
Why this scored this way
Scores are deterministic: each category earns rule points for verified public signals and loses points for failed checks. Unknown checks are shown separately instead of guessed.
Category point breakdown
SEO / AEO80/92
Security73/76
Accessibility57/94
Design84/110
Biggest score-losing checks
high
Accessibility
Rendered axe accessibility violationsaxe 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).
medium
Accessibility
Heading orderHeading 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.
medium
Design
Rendered speed signalsDOMContentLoaded: 1476ms. Load complete: 0ms. First contentful paint: 800ms. Resources: 152. Scripts: 36. Images: 49. Third-party origins: 49. Transfer: not available.
medium
Design
Rendered layout ergonomicsHorizontal overflow: 0px. Small tap targets: 33.
Recommendations
Score-losing issues ordered by remediation priority, severity, and score impact.
5 fixes
7 opportunities
9 insights
1
fail
high
Accessibility
Priority 5
Fix rendered axe accessibility violations
-18 rule ptsWhat 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.
2
fail
high
Security
Priority 5
Add common public security headers
-3 rule ptsWhat 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.
3
fail
medium
SEO / AEO
Priority 9
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 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.
4
fail
medium
Accessibility
Priority 13
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, 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.
5
fail
medium
Design
Priority 13
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: 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.
Unknown and not detected states
FreeScan.app keeps partial public data explicit. It marks unverifiable signals as unknown or not detected instead of inventing evidence.
0 unknown
Safe public scans cannot see private cookies, authenticated content, browser-rendered state, or reliable contrast values unless they are present in static public markup.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.
Score aggregation details
Category scores come from earned rule points divided by available rule points. Failed checks are ordered by severity and score lost.
87/100
9 pass, 2 fail, 0 unknown
SEO / AEO
Severity mix: 0 critical, 6 high, 3 medium, 2 low.
medium
Heading structure
-8 rule ptsDetected 1 H1 heading(s) and 26 total headings.
low
LLM-readable file
-4 rule ptsHTTP 404 returned for llms_txt.
96/100
5 pass, 1 fail, 0 unknown
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
high
Common security headers
-3 rule ptsDetected 4 of 5 common public security headers. Present: strict-transport-security, content-security-policy, x-content-type-options, referrer-policy. Missing: x-frame-options.
61/100
5 pass, 3 fail, 0 unknown
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
high
Rendered axe accessibility violations
-18 rule ptsaxe 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).
medium
Heading order
-11 rule ptsHeading 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.
medium
Basic contrast
-8 rule pts22 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 3.
76/100
8 pass, 3 fail, 0 unknown
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
medium
Rendered speed signals
-10 rule ptsDOMContentLoaded: 1476ms. Load complete: 0ms. First contentful paint: 800ms. Resources: 152. Scripts: 36. Images: 49. Third-party origins: 49. Transfer: not available.
medium
Rendered layout ergonomics
-9 rule ptsHorizontal overflow: 0px. Small tap targets: 33.
low
Runtime console health
-7 rule ptsDetected 3 console error(s) and 0 uncaught page error(s) during render.
Full check list
Failed, unknown, and passed checks are all shown so the report is transparent even when public data is partial.
Showing failed checks.
Failed checks
These checks need attention.
fail
medium
SEO / AEO
Heading structure
0/8Detected 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.
fail
low
SEO / AEO
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.
fail
high
Security
Common security headers
15/18Detected 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.
fail
medium
Accessibility
Heading order
0/11Heading 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.
fail
medium
Accessibility
Basic contrast
0/822 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.
fail
high
Accessibility
Rendered axe accessibility violations
0/18axe 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.
fail
medium
Design
Rendered speed signals
0/10DOMContentLoaded: 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.
fail
low
Design
Runtime console health
0/7Detected 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.
fail
medium
Design
Rendered layout ergonomics
0/9Horizontal 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.
Safe fetch metadata
Public headers and redirects captured during intake. Response bodies, cookies, and credentials are not stored.
Security and accessibility checks are basic automated public checks. They are not a complete security audit, penetration test, privacy review, or WCAG certification.
Landing page
Step 1HTTP 2006 captured header(s)Checked: https://www.launchpanda.dev
Next/final: https://www.launchpanda.dev
Content type: text/html; charset=utf-8
Landing page
Step 2HTTP 2006 captured header(s)Checked: https://www.launchpanda.dev
Next/final: https://www.launchpanda.dev
Content type: text/html; charset=utf-8
Content hash: b5cf4523fbe934007f214ec440e603bddf21d2fc44f1e882d791fc879c90dcf0
robots.txt
Step 3HTTP 2007 captured header(s)Checked: https://www.launchpanda.dev/robots.txt
Next/final: https://www.launchpanda.dev/robots.txt
Content type: text/plain
Content hash: 7ce9cd011b0df53d5ec5bfd0d9c0429efc05cddfad88070f7c74f58191824920
sitemap.xml
Step 4HTTP 2006 captured header(s)Checked: https://www.launchpanda.dev/sitemap.xml
Next/final: https://www.launchpanda.dev/sitemap.xml
Content type: application/xml
Content hash: 24fe18cf919764e9068e822ac63f04da03178a73c3d51f9a134e35dd29c9319c
llms.txt
Step 5HTTP 4046 captured header(s)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.
Security probe
Step 6HTTP 4046 captured header(s)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.
Security probe
Step 7HTTP 4046 captured header(s)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.
Security probe
Step 8HTTP 4031 captured header(s)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.
Security probe
Step 9HTTP 4046 captured header(s)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
Public report link
Markdown export
Share the website audit report
Copy a public report link or a Markdown version with scores, fixes, opportunities, insights, and a normal link back to the scanned site.
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.
Rescan same URL
Rerun the full deterministic scanner for launchpanda.dev without re-entering the URL. The previous report stays saved so the next result can be compared against it.