Loading scan status...
completed
HTTP 200
0 redirects
36 checks
Website audit scorecard for lighthouse.build
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
Four-score result
Close to ready (Needs polish): 30 passed, 6 failed, and 0 unknown. Strongest area: Design. Weakest area: Accessibility.
Overall
82
out of 100
SEO / AEO
91
out of 100
84/92 rule points
Security
82
out of 100
62/76 rule points
Accessibility
61
out of 100
57/94 rule points
Design
92
out of 100
101/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 / AEO84/92
Security62/76
Accessibility57/94
Design101/110
Biggest score-losing checks
high
Accessibility
Rendered axe accessibility violationsaxe 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).
high
Security
Common security headersDetected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
medium
Accessibility
Heading orderHeading levels found: 1, 2, 2, 3, 3, 3, 3, 3, 2, 2, 2, 5, 5, 5, 5.
medium
Design
Rendered layout ergonomicsHorizontal overflow: 0px. Small tap targets: 27.
Recommendations
Score-losing issues ordered by remediation priority, severity, and score impact.
5 fixes
4 opportunities
9 insights
1
fail
high
Security
Priority 5
Add common public security headers
-14 rule ptsWhat 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.
2
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 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.
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 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.
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, 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.
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: 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.
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.
91/100
10 pass, 1 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 15 total headings.
82/100
5 pass, 1 fail, 0 unknown
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
high
Common security headers
-14 rule ptsDetected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
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 2 serious or critical rule(s). Top rules: color-contrast (7), nested-interactive (1), heading-order (1), landmark-one-main (1), region (29).
medium
Heading order
-11 rule ptsHeading levels found: 1, 2, 2, 3, 3, 3, 3, 3, 2, 2, 2, 5, 5, 5, 5.
medium
Basic contrast
-8 rule pts3 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.08.
92/100
10 pass, 1 fail, 0 unknown
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
medium
Rendered layout ergonomics
-9 rule ptsHorizontal overflow: 0px. Small tap targets: 27.
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 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.
fail
high
Security
Common security headers
4/18Detected 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.
fail
medium
Accessibility
Heading order
0/11Heading 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.
fail
medium
Accessibility
Basic contrast
0/83 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.
fail
high
Accessibility
Rendered axe accessibility violations
0/18axe 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.
fail
medium
Design
Rendered layout ergonomics
0/9Horizontal 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.
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 2002 captured header(s)Checked: https://lighthouse.build
Next/final: https://lighthouse.build
Content type: text/html; charset=utf-8
Landing page
Step 2HTTP 2002 captured header(s)Checked: https://lighthouse.build
Next/final: https://lighthouse.build
Content type: text/html; charset=utf-8
Content hash: 21f54b82e5e477938e1877625b01329146062464f6d95b9ad7a55954ba5ff281
robots.txt
Step 3HTTP 2002 captured header(s)Checked: https://lighthouse.build/robots.txt
Next/final: https://lighthouse.build/robots.txt
Content type: text/plain
Content hash: 801c79a5f3b96c702e9f2324f1855bfce6a70a3a635caf550de04042f84b8bde
sitemap.xml
Step 4HTTP 2002 captured header(s)Checked: https://lighthouse.build/sitemap.xml
Next/final: https://lighthouse.build/sitemap.xml
Content type: application/xml
Content hash: 28e47150fd3b5f3601336bf47b2e02cc709c6c840d23c9ab4ae70e0770a456ec
llms.txt
Step 5HTTP 2002 captured header(s)Checked: https://lighthouse.build/llms.txt
Next/final: https://lighthouse.build/llms.txt
Content type: text/plain; charset=utf-8
Content hash: d016b96fcd017a798a99fe3136878717ddac3d43244949cdb743f21b9222d4d7
Security probe
Step 6HTTP 4042 captured header(s)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.
Security probe
Step 7HTTP 4042 captured header(s)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.
Security probe
Step 8HTTP 4031 captured header(s)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.
Security probe
Step 9HTTP 4042 captured header(s)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
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
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.
Rescan same URL
Rerun the full deterministic scanner for lighthouse.build without re-entering the URL. The previous report stays saved so the next result can be compared against it.