Website audit scorecard for narranta.com
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://narranta.com/
Final URL
https://narranta.com
Created
Jul 12, 2026, 7:52 PM
Safe fetch
379 ms
41
out of 100
49
out of 100
23/47 rule points
88
out of 100
46/52 rule points
0
out of 100
0/18 rule points
26
out of 100
10/38 rule points
Category point breakdown
Biggest score-losing checks
axe found 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (16), landmark-unique (1).
Could not fetch sitemap_xml.
No viewport meta tag was detected.
Horizontal overflow: 0px. Small tap targets: 23.
Fix rendered axe accessibility violations
-18 rule ptsWhat failed
The rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (16), 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.
Copyable agent prompt
Add responsive viewport metadata
-12 rule ptsWhat failed
The page is missing the viewport meta tag used for mobile layout.
Evidence
No viewport meta tag was detected.
Priority
Priority 3: fix before sharing the page publicly.
Why it matters
Launch traffic often comes from phones; missing viewport metadata can make the page render poorly.
How to fix it
Add a viewport meta tag with width=device-width and initial-scale=1.
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
Could not fetch 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 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
Add common public security headers
-6 rule ptsWhat failed
Several basic browser protection headers were not visible.
Evidence
Detected 4 of 5 common public security headers. Present: strict-transport-security, x-content-type-options, x-frame-options, referrer-policy. Missing: content-security-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 layout ergonomics
-9 rule ptsWhat failed
The browser-rendered page has layout or tap-target issues.
Evidence
Horizontal overflow: 0px. Small tap targets: 23.
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.
Copyable agent prompt
SEO / AEO
Severity mix: 1 critical, 2 high, 1 medium, 1 low.
sitemap.xml validity
-12 rule ptsCould not fetch sitemap_xml.
robots.txt reachability
-8 rule ptsCould not fetch robots_txt.
LLM-readable file
-4 rule ptsCould not fetch llms_txt.
Security
Severity mix: 2 critical, 1 high, 0 medium, 0 low.
Common security headers
-6 rule ptsDetected 4 of 5 common public security headers. Present: strict-transport-security, x-content-type-options, x-frame-options, referrer-policy. Missing: content-security-policy.
Accessibility
Severity mix: 0 critical, 1 high, 0 medium, 0 low.
Rendered axe accessibility violations
-18 rule ptsaxe found 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (16), landmark-unique (1).
Design
Severity mix: 0 critical, 1 high, 2 medium, 1 low.
Responsive viewport basics
-12 rule ptsNo viewport meta tag was detected.
Rendered layout ergonomics
-9 rule ptsHorizontal overflow: 0px. Small tap targets: 23.
Runtime console health
-7 rule ptsDetected 1 console error(s) and 0 uncaught page error(s) during render.
Showing failed checks.
Failed checks
These checks need attention.
robots.txt reachability
0/8Could not fetch robots_txt.
Failed: earned 0 of 8 points.
Priority: Priority 11: fix during launch polish.
Why it matters: A reachable robots.txt helps crawlers understand what they can index before launch traffic arrives.
Fix: Add a public /robots.txt file and make sure it returns HTTP 200 without blocking the landing page.
Copyable agent prompt
sitemap.xml validity
0/12Could not fetch 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 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
LLM-readable file
0/4Could not fetch 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
12/18Detected 4 of 5 common public security headers. Present: strict-transport-security, x-content-type-options, x-frame-options, referrer-policy. Missing: content-security-policy.
Failed: earned 12 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
Rendered axe accessibility violations
0/18axe found 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (16), 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.
Copyable agent prompt
Responsive viewport basics
0/12No viewport meta tag was detected.
Failed: earned 0 of 12 points.
Priority: Priority 3: fix before sharing the page publicly.
Why it matters: Launch traffic often comes from phones; missing viewport metadata can make the page render poorly.
Fix: Add a viewport meta tag with width=device-width and initial-scale=1.
Copyable agent prompt
Runtime console health
0/7Detected 1 console error(s) and 0 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.
Copyable agent prompt
Rendered layout ergonomics
0/9Horizontal overflow: 0px. Small tap targets: 23.
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
narranta.com website audit report
Needs fixes before launch: 41/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.