Website audit scorecard for rolenavigator.com
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://rolenavigator.com
Final URL
https://rolenavigator.com
Created
Jul 5, 2026, 6:07 PM
Safe fetch
194 ms
76
out of 100
61
out of 100
56/92 rule points
84
out of 100
64/76 rule points
72
out of 100
68/94 rule points
85
out of 100
94/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: aria-hidden-focus (1), color-contrast (81), landmark-main-is-top-level (1), landmark-no-duplicate-main (1), landmark-unique (1).
HTTP 404 returned for sitemap_xml.
Detected 1 of 5 common public security headers. Present: content-security-policy. Missing: strict-transport-security, x-content-type-options, x-frame-options, referrer-policy.
Title is 86 characters.
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: aria-hidden-focus (1), color-contrast (81), landmark-main-is-top-level (1), landmark-no-duplicate-main (1), landmark-unique (1).
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.
Add common public security headers
-12 rule ptsWhat failed
Several basic browser protection headers were not visible.
Evidence
Detected 1 of 5 common public security headers. Present: content-security-policy. Missing: strict-transport-security, 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.
Add a useful meta description
-10 rule ptsWhat failed
The page does not expose a strong short summary for search and answer engines.
Evidence
Meta description is 189 characters.
Priority
Priority 3: fix before sharing the page publicly.
Why it matters
A missing description makes previews weaker when early users share or find the page.
How to fix it
Add a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.
Publish sitemap.xml
-12 rule ptsWhat failed
The sitemap file was not reachable.
Evidence
HTTP 404 returned for sitemap_xml.
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 /sitemap.xml with your public URLs and confirm it returns HTTP 200.
Write a clear page title
-10 rule ptsWhat failed
The browser title is missing, too short, or too long for a reliable search result headline.
Evidence
Title is 86 characters.
Priority
Priority 8: fix during launch polish.
Why it matters
Search engines, social previews, and saved browser tabs use the title to tell people what your product is.
How to fix it
Set one concise title tag, ideally 10 to 70 characters, that includes the product name and the main promise.
SEO / AEO
Severity mix: 0 critical, 6 high, 3 medium, 2 low.
sitemap.xml reachability
-12 rule ptsHTTP 404 returned for sitemap_xml.
Page title
-10 rule ptsTitle is 86 characters.
Meta description
-10 rule ptsMeta description is 189 characters.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Common security headers
-12 rule ptsDetected 1 of 5 common public security headers. Present: content-security-policy. Missing: strict-transport-security, x-content-type-options, x-frame-options, referrer-policy.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Rendered axe accessibility violations
-18 rule ptsaxe found 5 violation rule(s), including 2 serious or critical rule(s). Top rules: aria-hidden-focus (1), color-contrast (81), landmark-main-is-top-level (1), landmark-no-duplicate-main (1), landmark-unique (1).
Basic contrast
-8 rule pts49 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Rendered layout ergonomics
-9 rule ptsHorizontal overflow: 1px. Small tap targets: 35.
Runtime console health
-7 rule ptsDetected 0 console error(s) and 3 uncaught page error(s) during render.
Showing failed checks.
Failed checks
These checks need attention.
Page title
0/10Title is 86 characters.
Failed: earned 0 of 10 points.
Priority: Priority 8: fix during launch polish.
Why it matters: Search engines, social previews, and saved browser tabs use the title to tell people what your product is.
Fix: Set one concise title tag, ideally 10 to 70 characters, that includes the product name and the main promise.
Meta description
0/10Meta description is 189 characters.
Failed: earned 0 of 10 points.
Priority: Priority 3: fix before sharing the page publicly.
Why it matters: A missing description makes previews weaker when early users share or find the page.
Fix: Add a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.
sitemap.xml reachability
0/12HTTP 404 returned for sitemap_xml.
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 /sitemap.xml with your public URLs and confirm it returns HTTP 200.
LLM-readable file
0/4HTTP 404 returned for llms_txt.
Failed: earned 0 of 4 points.
Priority: Priority 24: lower-risk cleanup after urgent launch blockers.
Why it matters: A short LLM-readable file can help answer engines and AI tools summarize your product accurately.
Fix: Add /llms.txt or /.well-known/llms.txt with the product name, audience, value proposition, and key public links.
Common security headers
6/18Detected 1 of 5 common public security headers. Present: content-security-policy. Missing: strict-transport-security, x-content-type-options, x-frame-options, referrer-policy.
Failed: earned 6 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.
Basic contrast
0/849 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.
Rendered axe accessibility violations
0/18axe found 5 violation rule(s), including 2 serious or critical rule(s). Top rules: aria-hidden-focus (1), color-contrast (81), landmark-main-is-top-level (1), landmark-no-duplicate-main (1), landmark-unique (1).
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.
Runtime console health
0/7Detected 0 console error(s) and 3 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.
Rendered layout ergonomics
0/9Horizontal overflow: 1px. Small tap targets: 35.
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.
Share preview
rolenavigator.com website audit report
Close to ready: 76/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.