Website audit scorecard for nuvoki.co
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
nuvoki.co
Final URL
https://nuvoki.co
Created
Jul 17, 2026, 6:54 AM
Safe fetch
247 ms
74
out of 100
89
out of 100
102/114 rule points
82
out of 100
62/76 rule points
61
out of 100
57/94 rule points
63
out of 100
69/110 rule points
Category point breakdown
Biggest score-losing checks
axe found 5 violation rule(s), including 3 serious or critical rule(s). Top rules: button-name (1), link-name (13), role-img-alt (1), heading-order (2), image-redundant-alt (5).
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.
Detected 2 H1 heading(s) and 145 meta-description characters.
Heading levels found: 3, 3, 3, 3, 1, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 1, 6, 6, 6, 6, 6, 6, 6, 6, 2, 3, 3, 3.
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.
Copyable agent prompt
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 3 serious or critical rule(s). Top rules: button-name (1), link-name (13), role-img-alt (1), heading-order (2), image-redundant-alt (5).
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
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 145 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
Fix heading order
-11 rule ptsWhat failed
Heading levels appear to jump or start without a clear hierarchy.
Evidence
Heading levels found: 3, 3, 3, 3, 1, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 1, 6, 6, 6, 6, 6, 6, 6, 6, 2, 3, 3, 3.
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.
Copyable agent prompt
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 2 H1 heading(s) and 29 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.
Copyable agent prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 2 low.
Heading structure
-8 rule ptsDetected 2 H1 heading(s) and 29 total headings.
LLM-readable file
-4 rule ptsHTTP 404 returned for llms_txt.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
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.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Rendered axe accessibility violations
-18 rule ptsaxe found 5 violation rule(s), including 3 serious or critical rule(s). Top rules: button-name (1), link-name (13), role-img-alt (1), heading-order (2), image-redundant-alt (5).
Heading order
-11 rule ptsHeading levels found: 3, 3, 3, 3, 1, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 1, 6, 6, 6, 6, 6, 6, 6, 6, 2, 3, 3, 3.
Basic contrast
-8 rule pts8 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.01.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Hero clarity signals
-13 rule ptsDetected 2 H1 heading(s) and 145 meta-description characters.
Trust signals
-10 rule ptsDetected 0 trust-signal keyword occurrence(s).
Readability signals
-9 rule ptsAverage sentence length is about 33 word(s).
Showing failed checks.
Failed checks
These checks need attention.
Heading structure
0/8Detected 2 H1 heading(s) and 29 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
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.
Copyable agent prompt
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.
Copyable agent prompt
Heading order
0/11Heading levels found: 3, 3, 3, 3, 1, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 1, 6, 6, 6, 6, 6, 6, 6, 6, 2, 3, 3, 3.
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.
Copyable agent prompt
Basic contrast
0/88 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.01.
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 5 violation rule(s), including 3 serious or critical rule(s). Top rules: button-name (1), link-name (13), role-img-alt (1), heading-order (2), image-redundant-alt (5).
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 145 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
Trust signals
0/10Detected 0 trust-signal keyword occurrence(s).
Failed: earned 0 of 10 points.
Priority: Priority 16: lower-risk cleanup after urgent launch blockers.
Why it matters: Trust signals reduce hesitation when strangers see the product for the first time.
Fix: Add honest proof such as customer quotes, usage stats, founder credibility, security notes, or relevant logos.
Copyable agent prompt
Readability signals
0/9Average sentence length is about 33 word(s).
Failed: earned 0 of 9 points.
Priority: Priority 23: lower-risk cleanup after urgent launch blockers.
Why it matters: Launch visitors often skim; long sentences make the offer harder to understand.
Fix: Shorten long sentences, use direct language, and break dense paragraphs into smaller sections.
Copyable agent prompt
Rendered layout ergonomics
0/9Horizontal overflow: 0px. Small tap targets: 11.
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
nuvoki.co website audit report
Close to ready: 74/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.