The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://lighthouse.build
Final URL
https://lighthouse.build
Created
Jun 29, 2026, 3:30 PM
Safe fetch
993 ms
82
out of 100
91
out of 100
84/92 rule points
82
out of 100
62/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 5 violation rule(s), including 2 serious or critical rule(s). Top rules: color-contrast (7), nested-interactive (1), heading-order (1), landmark-one-main (1), region (29).
Detected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
Heading levels found: 1, 2, 2, 3, 3, 3, 3, 3, 2, 2, 2, 5, 5, 5, 5.
Horizontal overflow: 0px. Small tap targets: 27.
What failed
Several basic browser protection headers were not visible.
Evidence
Detected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
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 rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 5 violation rule(s), including 2 serious or critical rule(s). Top rules: color-contrast (7), nested-interactive (1), heading-order (1), landmark-one-main (1), region (29).
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
The page heading structure is either missing a single main heading or skips heading levels.
Evidence
Detected 1 H1 heading(s) and 15 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, 2, 3, 3, 3, 3, 3, 2, 2, 2, 5, 5, 5, 5.
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: 27.
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 15 total headings.
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Detected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
axe found 5 violation rule(s), including 2 serious or critical rule(s). Top rules: color-contrast (7), nested-interactive (1), heading-order (1), landmark-one-main (1), region (29).
Heading levels found: 1, 2, 2, 3, 3, 3, 3, 3, 2, 2, 2, 5, 5, 5, 5.
3 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.08.
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Horizontal overflow: 0px. Small tap targets: 27.
Showing failed checks.
These checks need attention.
Detected 1 H1 heading(s) and 15 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.
Detected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
Failed: earned 4 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, 2, 3, 3, 3, 3, 3, 2, 2, 2, 5, 5, 5, 5.
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.
3 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.08.
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 2 serious or critical rule(s). Top rules: color-contrast (7), nested-interactive (1), heading-order (1), landmark-one-main (1), region (29).
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.
Horizontal overflow: 0px. Small tap targets: 27.
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://lighthouse.build
Next/final: https://lighthouse.build
Content type: text/html; charset=utf-8
Checked: https://lighthouse.build
Next/final: https://lighthouse.build
Content type: text/html; charset=utf-8
Content hash: 21f54b82e5e477938e1877625b01329146062464f6d95b9ad7a55954ba5ff281
Checked: https://lighthouse.build/robots.txt
Next/final: https://lighthouse.build/robots.txt
Content type: text/plain
Content hash: 801c79a5f3b96c702e9f2324f1855bfce6a70a3a635caf550de04042f84b8bde
Checked: https://lighthouse.build/sitemap.xml
Next/final: https://lighthouse.build/sitemap.xml
Content type: application/xml
Content hash: 28e47150fd3b5f3601336bf47b2e02cc709c6c840d23c9ab4ae70e0770a456ec
Checked: https://lighthouse.build/llms.txt
Next/final: https://lighthouse.build/llms.txt
Content type: text/plain; charset=utf-8
Content hash: d016b96fcd017a798a99fe3136878717ddac3d43244949cdb743f21b9222d4d7
Checked: https://lighthouse.build/.env
Next/final: https://lighthouse.build/.env
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Checked: https://lighthouse.build/.git/config
Next/final: https://lighthouse.build/.git/config
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Checked: https://lighthouse.build/wp-config.php
Next/final: https://lighthouse.build/wp-config.php
Content type: text/html; charset=utf-8
Fetch result: HTTP 403 returned for security_probe.
Checked: https://lighthouse.build/backup.zip
Next/final: https://lighthouse.build/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
strict-transport-security
max-age=63072000
Share preview
lighthouse.build website audit report
Close to ready: 82/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.