Website audit scorecard for cartlens.co
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://cartlens.co/
Final URL
https://www.cartlens.co
Created
Jul 21, 2026, 4:11 PM
Safe fetch
163 ms
78
out of 100
100
out of 100
114/114 rule points
100
out of 100
76/76 rule points
62
out of 100
58/94 rule points
50
out of 100
55/110 rule points
Category point breakdown
Biggest score-losing checks
axe found 4 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (16), heading-order (2), landmark-unique (1), region (122).
Detected 1 landmark element(s) or roles.
Detected about 45 visible word(s).
Detected 0 trust-signal keyword occurrence(s).
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 1 serious or critical rule(s). Top rules: color-contrast (16), heading-order (2), landmark-unique (1), region (122).
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
Strengthen visual hierarchy
-9 rule ptsWhat failed
The page does not expose enough hierarchy signals from headings, emphasis, or CTA structure.
Evidence
Detected 2 hierarchy signal(s) from headings, CTA, and emphasized text.
Priority
Priority 12: fix during launch polish.
Why it matters
Hierarchy tells visitors what to read first and what action to take next.
How to fix it
Create a clear H1, supportive section headings, emphasized proof, and one visually prominent primary CTA.
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: 48.
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
Improve rendered speed signals
-10 rule ptsWhat failed
The browser-rendered page shows slow or heavy speed signals.
Evidence
DOMContentLoaded: 1416ms. Load complete: 1417ms. First contentful paint: 2160ms. Resources: 49. Scripts: 14. Images: 11. Third-party origins: 12. Transfer: not available.
Priority
Priority 14: fix during launch polish.
Why it matters
Slow pages lose impatient visitors and make every SEO, social, and paid-traffic visit work harder.
How to fix it
Reduce render-blocking scripts/styles, compress and size images, defer non-critical JavaScript, reduce third-party tags, and keep above-the-fold content quick to paint.
Copyable agent prompt
Add page landmarks
-10 rule ptsWhat failed
The page is missing common landmarks such as header, nav, main, or footer.
Evidence
Detected 1 landmark element(s) or roles.
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.
How to fix it
Use semantic elements such as header, nav, main, and footer around the appropriate page areas.
Copyable agent prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 2 low.
No failed checks in this category.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
No failed checks in this category.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Rendered axe accessibility violations
-18 rule ptsaxe found 4 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (16), heading-order (2), landmark-unique (1), region (122).
Landmark presence
-10 rule ptsDetected 1 landmark element(s) or roles.
Basic contrast
-8 rule pts61 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.
Text density
-10 rule ptsDetected about 45 visible word(s).
Trust signals
-10 rule ptsDetected 0 trust-signal keyword occurrence(s).
Rendered speed signals
-10 rule ptsDOMContentLoaded: 1416ms. Load complete: 1417ms. First contentful paint: 2160ms. Resources: 49. Scripts: 14. Images: 11. Third-party origins: 12. Transfer: not available.
Showing failed checks.
Failed checks
These checks need attention.
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.
Copyable agent prompt
Basic contrast
0/861 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 4 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (16), heading-order (2), landmark-unique (1), region (122).
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
Text density
0/10Detected about 45 visible word(s).
Failed: earned 0 of 10 points.
Priority: Priority 21: lower-risk cleanup after urgent launch blockers.
Why it matters: Too little copy can leave visitors confused; too much copy can bury the value proposition.
Fix: Add concise sections for value, proof, how it works, and next steps, then remove repetitive copy.
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
Spacing consistency
0/7Detected 2 spacing class/style signal(s).
Failed: earned 0 of 7 points.
Priority: Priority 25: lower-risk cleanup after urgent launch blockers.
Why it matters: Consistent spacing helps the page feel deliberate and easier to scan.
Fix: Use consistent section padding, gaps, and margins across repeated content blocks.
Copyable agent prompt
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.
Copyable agent prompt
Rendered speed signals
0/10DOMContentLoaded: 1416ms. Load complete: 1417ms. First contentful paint: 2160ms. Resources: 49. Scripts: 14. Images: 11. Third-party origins: 12. Transfer: not available.
Failed: earned 0 of 10 points.
Priority: Priority 14: fix during launch polish.
Why it matters: Slow pages lose impatient visitors and make every SEO, social, and paid-traffic visit work harder.
Fix: Reduce render-blocking scripts/styles, compress and size images, defer non-critical JavaScript, reduce third-party tags, and keep above-the-fold content quick to paint.
Copyable agent prompt
Rendered layout ergonomics
0/9Horizontal overflow: 0px. Small tap targets: 48.
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
cartlens.co website audit report
Close to ready: 78/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.