Loading scan status...
completed
HTTP 200
0 redirects
36 checks
Website audit scorecard for launchchair.io
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://www.launchchair.io/
Final URL
https://www.launchchair.io
Created
Jun 29, 2026, 3:11 AM
Safe fetch
160 ms
Four-score result
Close to ready (Strong): 29 passed, 6 failed, and 1 unknown. Strongest area: SEO / AEO. Weakest area: Design.
Overall
85
out of 100
SEO / AEO
100
out of 100
82/82 rule points
Security
97
out of 100
74/76 rule points
Accessibility
72
out of 100
68/94 rule points
Design
70
out of 100
77/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 / AEO82/82
Security74/76
Accessibility68/94
Design77/110
Biggest score-losing checks
high
Accessibility
Rendered axe accessibility violationsaxe found 1 violation rule(s), including 0 serious or critical rule(s). Top rules: region (9).
medium
Design
Rendered speed signalsDOMContentLoaded: 1561ms. Load complete: 2817ms. First contentful paint: 1276ms. Resources: 76. Scripts: 26. Images: 44. Third-party origins: 44. Transfer: not available.
medium
Design
Rendered layout ergonomicsHorizontal overflow: 0px. Small tap targets: 4.
medium
Accessibility
Basic contrast50 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
Recommendations
Score-losing issues ordered by remediation priority, severity, and score impact.
5 fixes
4 opportunities
9 insights
1
high
Accessibility
Priority 5
Fix rendered axe accessibility violations
-18 ptsWhat failed
The rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 1 violation rule(s), including 0 serious or critical rule(s). Top rules: region (9).
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
medium
Design
Priority 13
Fix rendered layout ergonomics
-9 ptsWhat failed
The browser-rendered page has layout or tap-target issues.
Evidence
Horizontal overflow: 0px. Small tap targets: 4.
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.
3
medium
Design
Priority 14
Improve rendered speed signals
-10 ptsWhat failed
The browser-rendered page shows slow or heavy speed signals.
Evidence
DOMContentLoaded: 1561ms. Load complete: 2817ms. First contentful paint: 1276ms. Resources: 76. Scripts: 26. Images: 44. Third-party origins: 44. Transfer: not available.
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.
How to fix it
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.
4
low
Design
Priority 15
Fix runtime browser errors
-7 ptsWhat failed
The rendered page produced console or uncaught JavaScript errors.
Evidence
Detected 2 console error(s) and 0 uncaught page error(s) during render.
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.
How to fix it
Open the page in a browser, reproduce the console errors, and fix missing assets, hydration problems, client-side exceptions, or failing third-party scripts.
5
medium
Accessibility
Priority 20
Improve detectable color contrast
-8 ptsWhat failed
The scanner found text/background color pairs that may be hard to read, or could not verify contrast.
Evidence
50 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
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.
How to fix it
Review key text, buttons, and links against a 4.5:1 contrast target for normal text.
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.
1 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.not detected
Security
Priority 20
Visible cookie flags
Cookie flags were not visible from the safe public metadata captured for this page.
Why it matters: Session and preference cookies should avoid unnecessary exposure before early users sign in or submit forms.
Manual check: Review application cookies in the browser and set Secure, HttpOnly where appropriate, SameSite, and narrow expiration values before launch.
Score aggregation details
Category scores come from earned rule points divided by available rule points. Failed checks are ordered by severity and score lost.
100/100
11 pass, 0 fail, 0 unknown
SEO / AEO
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
No failed checks in this category.
97/100
5 pass, 0 fail, 1 unknown
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
No failed checks in this category.
72/100
6 pass, 2 fail, 0 unknown
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
high
Rendered axe accessibility violations
-18 ptsaxe found 1 violation rule(s), including 0 serious or critical rule(s). Top rules: region (9).
medium
Basic contrast
-8 pts50 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
70/100
7 pass, 4 fail, 0 unknown
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
medium
Rendered speed signals
-10 ptsDOMContentLoaded: 1561ms. Load complete: 2817ms. First contentful paint: 1276ms. Resources: 76. Scripts: 26. Images: 44. Third-party origins: 44. Transfer: not available.
medium
Rendered layout ergonomics
-9 ptsHorizontal overflow: 0px. Small tap targets: 4.
low
Spacing consistency
-7 ptsDetected 2 spacing class/style signal(s).
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
Accessibility
Basic contrast
0/850 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.
fail
high
Accessibility
Rendered axe accessibility violations
0/18axe found 1 violation rule(s), including 0 serious or critical rule(s). Top rules: region (9).
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
low
Design
Spacing consistency
0/7Detected 2 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.
fail
medium
Design
Rendered speed signals
0/10DOMContentLoaded: 1561ms. Load complete: 2817ms. First contentful paint: 1276ms. Resources: 76. Scripts: 26. Images: 44. Third-party origins: 44. 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 2 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: 4.
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 2007 captured header(s)Checked: https://www.launchchair.io
Next/final: https://www.launchchair.io
Content type: text/html; charset=utf-8
Landing page
Step 2HTTP 2006 captured header(s)Checked: https://www.launchchair.io
Next/final: https://www.launchchair.io
Content type: text/html; charset=utf-8
Content hash: f3be90a6eb0bfc3cde729b10fe4f2243f7f671c6b4273eab502420e34f88d7a8
robots.txt
Step 3HTTP 2002 captured header(s)Checked: https://www.launchchair.io/robots.txt
Next/final: https://www.launchchair.io/robots.txt
Content type: text/plain
Content hash: afb0ec030dfd185b519be0bf5dbbc7393e5e8f1cd2e0ee4823e18ddf47790ab9
sitemap.xml
Step 4HTTP 2002 captured header(s)Checked: https://www.launchchair.io/sitemap.xml
Next/final: https://www.launchchair.io/sitemap.xml
Content type: application/xml
Content hash: 7619179978a121c8bfe3b895a3df90a36443f54e802e69ef89432171219c7364
llms.txt
Step 5HTTP 2002 captured header(s)Checked: https://www.launchchair.io/llms.txt
Next/final: https://www.launchchair.io/llms.txt
Content type: text/plain; charset=utf-8
Content hash: 3f074aeca68acf1feb5d6a986d138038ec76e6ac30e3dbb6e807e7118a18597c
Security probe
Step 6HTTP 4047 captured header(s)Checked: https://www.launchchair.io/.env
Next/final: https://www.launchchair.io/.env
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Security probe
Step 7HTTP 4047 captured header(s)Checked: https://www.launchchair.io/.git/config
Next/final: https://www.launchchair.io/.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.launchchair.io/wp-config.php
Next/final: https://www.launchchair.io/wp-config.php
Content type: text/html; charset=utf-8
Fetch result: HTTP 403 returned for security_probe.
Security probe
Step 9HTTP 4047 captured header(s)Checked: https://www.launchchair.io/backup.zip
Next/final: https://www.launchchair.io/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
content-length
406044
referrer-policy
strict-origin-when-cross-origin
permissions-policy
camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=()
x-content-type-options
nosniff
content-security-policy
default-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors https://buildhop.io; object-src 'none'; img-src 'self' data: blob: https:; font-src 'self' data: https://fonts.googleapis.com https://fonts.gstatic.com https://crisp.chat https://*.crisp.chat; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://hcaptcha.com https://*.hcaptcha.com https://crisp.chat https://*.crisp.chat; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://hcaptcha.com https://js.hcaptch
strict-transport-security
max-age=31536000; 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
launchchair.io website audit report
Close to ready: 85/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 launchchair.io without re-entering the URL. The previous report stays saved so the next result can be compared against it.