Website audit scorecard for grenishrai.vercel.app
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://grenishrai.vercel.app/
Final URL
https://grenishrai.vercel.app
Created
Jul 4, 2026, 8:26 PM
Safe fetch
97 ms
73
out of 100
74
out of 100
68/92 rule points
82
out of 100
62/76 rule points
70
out of 100
66/94 rule points
65
out of 100
71/110 rule points
Category point breakdown
Biggest score-losing checks
axe found 4 violation rule(s), including 2 serious or critical rule(s). Top rules: button-name (1), color-contrast (5), landmark-one-main (1), region (24).
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 0 CTA candidate(s).
No canonical link tag was detected.
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.
Fix rendered axe accessibility violations
-18 rule ptsWhat failed
The rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 4 violation rule(s), including 2 serious or critical rule(s). Top rules: button-name (1), color-contrast (5), landmark-one-main (1), region (24).
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.
Make the primary CTA obvious
-14 rule ptsWhat failed
The page does not have a detectable call to action.
Evidence
Detected 0 CTA candidate(s).
Priority
Priority 4: fix before sharing the page publicly.
Why it matters
Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
How to fix it
Add one prominent CTA above the fold with action-oriented text such as Start, Join, Try, Book, or Get started.
Add a canonical URL
-10 rule ptsWhat failed
The page does not declare which public URL is the preferred version.
Evidence
No canonical link tag was detected.
Priority
Priority 9: fix during launch polish.
Why it matters
A canonical tag reduces duplicate URL confusion before marketing links start spreading.
How to fix it
Add a canonical link tag that points to the final public landing page URL.
Add basic structured data
-10 rule ptsWhat failed
No JSON-LD schema was detected on the page.
Evidence
Detected 0 JSON-LD schema block(s).
Priority
Priority 12: fix during launch polish.
Why it matters
Structured data gives search and answer engines explicit facts about your product.
How to fix it
Add JSON-LD for SoftwareApplication, Product, Organization, or WebSite using only accurate public facts.
SEO / AEO
Severity mix: 0 critical, 6 high, 3 medium, 2 low.
Canonical tag
-10 rule ptsNo canonical link tag was detected.
Schema presence
-10 rule ptsDetected 0 JSON-LD schema block(s).
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 4 violation rule(s), including 2 serious or critical rule(s). Top rules: button-name (1), color-contrast (5), landmark-one-main (1), region (24).
Landmark presence
-10 rule ptsDetected 1 landmark element(s) or roles.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Visible primary CTA
-14 rule ptsDetected 0 CTA candidate(s).
Visual hierarchy
-9 rule ptsDetected 2 hierarchy signal(s) from headings, CTA, and emphasized text.
Rendered layout ergonomics
-9 rule ptsHorizontal overflow: 0px. Small tap targets: 31.
Showing failed checks.
Failed checks
These checks need attention.
Canonical tag
0/10No canonical link tag was detected.
Failed: earned 0 of 10 points.
Priority: Priority 9: fix during launch polish.
Why it matters: A canonical tag reduces duplicate URL confusion before marketing links start spreading.
Fix: Add a canonical link tag that points to the final public landing page URL.
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.
Schema presence
0/10Detected 0 JSON-LD schema block(s).
Failed: earned 0 of 10 points.
Priority: Priority 12: fix during launch polish.
Why it matters: Structured data gives search and answer engines explicit facts about your product.
Fix: Add JSON-LD for SoftwareApplication, Product, Organization, or WebSite using only accurate public facts.
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.
Landmark presence
0/10Detected 1 landmark element(s) or roles.
Failed: earned 0 of 10 points.
Priority: Priority 18: lower-risk cleanup after urgent launch blockers.
Why it matters: Landmarks make the page easier to navigate for assistive technology and keyboard users.
Fix: Use semantic elements such as header, nav, main, and footer around the appropriate page areas.
Rendered axe accessibility violations
0/18axe found 4 violation rule(s), including 2 serious or critical rule(s). Top rules: button-name (1), color-contrast (5), landmark-one-main (1), region (24).
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.
Visible primary CTA
0/14Detected 0 CTA candidate(s).
Failed: earned 0 of 14 points.
Priority: Priority 4: fix before sharing the page publicly.
Why it matters: Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
Fix: Add one prominent CTA above the fold with action-oriented text such as Start, Join, Try, Book, or Get started.
Visual hierarchy
0/9Detected 2 hierarchy signal(s) from headings, CTA, and emphasized text.
Failed: earned 0 of 9 points.
Priority: Priority 12: fix during launch polish.
Why it matters: Hierarchy tells visitors what to read first and what action to take next.
Fix: Create a clear H1, supportive section headings, emphasized proof, and one visually prominent primary CTA.
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.
Rendered layout ergonomics
0/9Horizontal overflow: 0px. Small tap targets: 31.
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
grenishrai.vercel.app website audit report
Close to ready: 73/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.