The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://uniquel.io/
Final URL
https://uniquel.io
Created
Jun 29, 2026, 1:51 PM
Safe fetch
148 ms
79
out of 100
85
out of 100
70/82 rule points
76
out of 100
58/76 rule points
72
out of 100
68/94 rule points
83
out of 100
91/110 rule points
Category point breakdown
Biggest score-losing checks
Detected 1 of 5 common public security headers.
axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (1).
Detected 0 trust-signal keyword occurrence(s).
Horizontal overflow: 0px. Small tap targets: 15.
What failed
Several basic browser protection headers were not visible.
Evidence
Detected 1 of 5 common public security headers.
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.
What failed
The rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (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.
What failed
The browser-rendered page has layout or tap-target issues.
Evidence
Horizontal overflow: 0px. Small tap targets: 15.
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.
What failed
The page does not expose detectable proof, customer, review, security, or credibility signals.
Evidence
Detected 0 trust-signal keyword occurrence(s).
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.
How to fix it
Add honest proof such as customer quotes, usage stats, founder credibility, security notes, or relevant logos.
What failed
No JSON-LD schema was detected on the page.
Evidence
Detected 0 JSON-LD schema block(s).
Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
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.
This scan did not produce unknown checks. If a future page has partial public data, the report will show those checks here instead of guessing.
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Detected 0 JSON-LD schema block(s).
HTTP 404 returned for llms_txt.
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Detected 1 of 5 common public security headers.
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (1).
10 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Detected 0 trust-signal keyword occurrence(s).
Horizontal overflow: 0px. Small tap targets: 15.
Showing failed checks.
These checks need attention.
HTTP 404 returned for llms_txt.
Failed: earned 0 of 5 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.
Detected 0 JSON-LD schema block(s).
Failed: earned 0 of 7 points.
Priority: Priority 16: lower-risk cleanup after urgent launch blockers.
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.
Detected 1 of 5 common public security headers.
Failed: earned 0 of 18 points.
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.
10 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.
axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (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.
Detected 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.
Horizontal overflow: 0px. Small tap targets: 15.
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.
Security and accessibility checks are basic automated public checks. They are not a complete security audit, penetration test, privacy review, or WCAG certification.
Checked: https://uniquel.io
Next/final: https://uniquel.io
Content type: text/html; charset=utf-8
Checked: https://uniquel.io
Next/final: https://uniquel.io
Content type: text/html; charset=utf-8
Content hash: f9c89e9e52db7d0e36efd45b8ea813b69079a36141967faf9b317393763d88e9
Checked: https://uniquel.io/robots.txt
Next/final: https://uniquel.io/robots.txt
Content type: text/plain; charset=utf-8
Content hash: 45fc8aa556ac8dde6b1b67856d1e2fd4800be281b2b0959a126dcb26ce645918
Checked: https://uniquel.io/sitemap.xml
Next/final: https://uniquel.io/sitemap.xml
Content type: application/xml
Content hash: 8746b4c2bf31d8761d26f524ea37017a68a1db52b5feae77528042f1a2c21428
Checked: https://uniquel.io/llms.txt
Next/final: https://uniquel.io/llms.txt
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for llms_txt.
Checked: https://uniquel.io/.env
Next/final: https://uniquel.io/.env
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Checked: https://uniquel.io/.git/config
Next/final: https://uniquel.io/.git/config
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Checked: https://uniquel.io/wp-config.php
Next/final: https://uniquel.io/wp-config.php
Content type: text/html; charset=utf-8
Fetch result: HTTP 403 returned for security_probe.
Checked: https://uniquel.io/backup.zip
Next/final: https://uniquel.io/backup.zip
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Captured public headers
content-type
text/html; charset=utf-8
content-length
67864
strict-transport-security
max-age=63072000
Share preview
uniquel.io website audit report
Close to ready: 79/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.