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/build
Final URL
https://www.launchchair.io/build
Created
Jun 29, 2026, 6:02 PM
Safe fetch
156 ms
Four-score result
Close to ready (Strong): 32 passed, 4 failed, and 0 unknown. Strongest area: SEO / AEO. Weakest area: Accessibility.
Overall
89
out of 100
SEO / AEO
100
out of 100
92/92 rule points
Security
100
out of 100
76/76 rule points
Accessibility
72
out of 100
68/94 rule points
Design
82
out of 100
90/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 / AEO92/92
Security76/76
Accessibility68/94
Design90/110
Biggest score-losing checks
high
Accessibility
Rendered axe accessibility violationsaxe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (18).
medium
Design
Text densityDetected about 2093 visible word(s).
medium
Design
Rendered speed signalsDOMContentLoaded: 469ms. Load complete: 983ms. First contentful paint: 616ms. Resources: 30. Scripts: 24. Images: 0. Third-party origins: 2. Transfer: not available.
medium
Accessibility
Basic contrast13 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 2.73.
Recommendations
Score-losing issues ordered by remediation priority, severity, and score impact.
4 fixes
4 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 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (18).
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
medium
Design
Priority 14
Improve rendered speed signals
-10 rule ptsWhat failed
The browser-rendered page shows slow or heavy speed signals.
Evidence
DOMContentLoaded: 469ms. Load complete: 983ms. First contentful paint: 616ms. Resources: 30. Scripts: 24. Images: 0. Third-party origins: 2. 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.
3
fail
medium
Accessibility
Priority 20
Improve detectable color contrast
-8 rule ptsWhat failed
The scanner found text/background color pairs that may be hard to read, or could not verify contrast.
Evidence
13 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 2.73.
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.
4
fail
medium
Design
Priority 21
Balance landing page copy
-10 rule ptsWhat failed
The page has too little or too much detectable text for a useful launch page.
Evidence
Detected about 2093 visible word(s).
Priority
Priority 21: lower-risk cleanup after urgent launch blockers.
Why it matters
Too little copy can leave visitors confused; too much copy can bury the value proposition.
How to fix it
Add concise sections for value, proof, how it works, and next steps, then remove repetitive copy.
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.
100/100
11 pass, 0 fail, 0 unknown
SEO / AEO
Severity mix: 0 critical, 6 high, 3 medium, 2 low.
No failed checks in this category.
100/100
6 pass, 0 fail, 0 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 rule ptsaxe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (18).
medium
Basic contrast
-8 rule pts13 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 2.73.
82/100
9 pass, 2 fail, 0 unknown
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
medium
Text density
-10 rule ptsDetected about 2093 visible word(s).
medium
Rendered speed signals
-10 rule ptsDOMContentLoaded: 469ms. Load complete: 983ms. First contentful paint: 616ms. Resources: 30. Scripts: 24. Images: 0. Third-party origins: 2. Transfer: not available.
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/813 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 2.73.
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 1 serious or critical rule(s). Top rules: color-contrast (18).
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
Text density
0/10Detected about 2093 visible word(s).
Failed: earned 0 of 10 points.
Priority: Priority 21: lower-risk cleanup after urgent launch blockers.
Why it matters: Too little copy can leave visitors confused; too much copy can bury the value proposition.
Fix: Add concise sections for value, proof, how it works, and next steps, then remove repetitive copy.
fail
medium
Design
Rendered speed signals
0/10DOMContentLoaded: 469ms. Load complete: 983ms. First contentful paint: 616ms. Resources: 30. Scripts: 24. Images: 0. Third-party origins: 2. 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.
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 2008 captured header(s)Checked: https://www.launchchair.io/build
Next/final: https://www.launchchair.io/build
Content type: text/html; charset=utf-8
Landing page
Step 2HTTP 2007 captured header(s)Checked: https://www.launchchair.io/build
Next/final: https://www.launchchair.io/build
Content type: text/html; charset=utf-8
Content hash: fd89366e70d8ca4896da0fc338a836377e70743fb2cbf09236af4de6b9c213b2
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: 14a43f8c1a63d939ab6056d61457f83b55810b38217277e93597d4e9f959c439
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: 5048aacb492f306691d2d0d9a75aa3e7310b0fb69afc0221eb6bc5625e56280f
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
365024
referrer-policy
strict-origin-when-cross-origin
x-frame-options
DENY
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 'none'; 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.hcaptcha.com https:/
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: 89/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.