Website audit scorecard for livingpage.app
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://livingpage.app/
Final URL
https://livingpage.app
Created
Jul 30, 2026, 11:53 AM
Safe fetch
182 ms
71
out of 100
82
out of 100
94/114 rule points
91
out of 100
69/76 rule points
32
out of 100
30/94 rule points
80
out of 100
88/110 rule points
Category point breakdown
Biggest score-losing checks
axe found 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (14), landmark-one-main (1), region (66).
Detected 7 image(s) missing alt text out of 53.
Detected labels or accessible names for 0 of 1 form control(s).
Detected 2 H1 heading(s) and 154 meta-description characters.
Fix rendered axe accessibility violations
-18 rule ptsWhat failed
The rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (14), landmark-one-main (1), region (66).
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.
Copyable agent prompt
Label public form fields
-14 rule ptsWhat failed
Some form controls do not have a detectable label or accessible name.
Evidence
Detected labels or accessible names for 0 of 1 form control(s).
Priority
Priority 7: fix during launch polish.
Why it matters
Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
How to fix it
Connect each input to a visible label or an accurate aria-label/aria-labelledby value.
Copyable agent prompt
Clarify the hero promise
-13 rule ptsWhat failed
The hero area does not provide enough clear product context.
Evidence
Detected 2 H1 heading(s) and 154 meta-description characters.
Priority
Priority 6: fix during launch polish.
Why it matters
Visitors decide quickly whether the product is relevant; a vague hero weakens every acquisition channel.
How to fix it
Use one clear H1 plus supporting copy that names the audience, problem, and outcome.
Copyable agent prompt
Add common public security headers
-7 rule ptsWhat failed
Several basic browser protection headers were not visible.
Evidence
Detected 3 of 5 common public security headers. Present: content-security-policy, x-content-type-options, referrer-policy. Missing: strict-transport-security, 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.
Copyable agent prompt
Publish a valid sitemap.xml
-12 rule ptsWhat failed
The sitemap file was not reachable or did not look like valid sitemap XML.
Evidence
sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.
Priority
Priority 7: fix during launch polish.
Why it matters
A sitemap helps search engines discover the landing page and related public pages sooner.
How to fix it
Add a static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.
Copyable agent prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 2 low.
sitemap.xml validity
-12 rule ptssitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.
Heading structure
-8 rule ptsDetected 2 H1 heading(s) and 13 total headings.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Common security headers
-7 rule ptsDetected 3 of 5 common public security headers. Present: content-security-policy, x-content-type-options, referrer-policy. Missing: strict-transport-security, x-frame-options.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Rendered axe accessibility violations
-18 rule ptsaxe found 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (14), landmark-one-main (1), region (66).
Image alt text
-14 rule ptsDetected 7 image(s) missing alt text out of 53.
Form labels
-14 rule ptsDetected labels or accessible names for 0 of 1 form control(s).
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Hero clarity signals
-13 rule ptsDetected 2 H1 heading(s) and 154 meta-description characters.
Rendered layout ergonomics
-9 rule ptsHorizontal overflow: 0px. Small tap targets: 39.
Showing failed checks.
Failed checks
These checks need attention.
Heading structure
0/8Detected 2 H1 heading(s) and 13 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.
Copyable agent prompt
sitemap.xml validity
0/12sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.
Failed: earned 0 of 12 points.
Priority: Priority 7: fix during launch polish.
Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.
Fix: Add a static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.
Copyable agent prompt
Common security headers
11/18Detected 3 of 5 common public security headers. Present: content-security-policy, x-content-type-options, referrer-policy. Missing: strict-transport-security, x-frame-options.
Failed: earned 11 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.
Copyable agent prompt
Image alt text
0/14Detected 7 image(s) missing alt text out of 53.
Failed: earned 0 of 14 points.
Priority: Priority 11: fix during launch polish.
Why it matters: People using screen readers may miss product context, trust signals, or calls to action.
Fix: Add concise alt text for informative images and use empty alt text only for decorative images.
Copyable agent prompt
Form labels
0/14Detected labels or accessible names for 0 of 1 form control(s).
Failed: earned 0 of 14 points.
Priority: Priority 7: fix during launch polish.
Why it matters: Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
Fix: Connect each input to a visible label or an accurate aria-label/aria-labelledby value.
Copyable agent prompt
Semantic buttons and links
0/10Detected 1 semantic control(s) out of 2.
Failed: earned 0 of 10 points.
Priority: Priority 17: lower-risk cleanup after urgent launch blockers.
Why it matters: Non-semantic controls can be hard to use with keyboards and screen readers.
Fix: Use button for actions and anchor links for navigation, with clear accessible names.
Copyable agent prompt
Basic contrast
0/87 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.
Copyable agent prompt
Rendered axe accessibility violations
0/18axe found 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (14), landmark-one-main (1), region (66).
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.
Copyable agent prompt
Hero clarity signals
0/13Detected 2 H1 heading(s) and 154 meta-description characters.
Failed: earned 0 of 13 points.
Priority: Priority 6: fix during launch polish.
Why it matters: Visitors decide quickly whether the product is relevant; a vague hero weakens every acquisition channel.
Fix: Use one clear H1 plus supporting copy that names the audience, problem, and outcome.
Copyable agent prompt
Rendered layout ergonomics
0/9Horizontal overflow: 0px. Small tap targets: 39.
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.
Copyable agent prompt
Share preview
livingpage.app website audit report
Close to ready: 71/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.