The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
yukieliot.com
Final URL
https://yukieliot.com
Created
Jun 30, 2026, 6:19 AM
Safe fetch
371 ms
83
out of 100
100
out of 100
92/92 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 0 of 5 common public security headers. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (9).
Detected 0 trust-signal keyword occurrence(s).
Horizontal overflow: 0px. Small tap targets: 3.
What failed
Several basic browser protection headers were not visible.
Evidence
Detected 0 of 5 common public security headers. Present: none. Missing: strict-transport-security, 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.
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 (9).
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: 3.
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
The scanner found text/background color pairs that may be hard to read, or could not verify contrast.
Evidence
13 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
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.
How to fix it
Review key text, buttons, and links against a 4.5:1 contrast target for normal text.
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, 6 high, 3 medium, 2 low.
No failed checks in this category.
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Detected 0 of 5 common public security headers. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
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 (9).
13 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: 3.
Showing failed checks.
These checks need attention.
Detected 0 of 5 common public security headers. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
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.
13 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 (9).
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: 3.
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://yukieliot.com
Next/final: https://yukieliot.com
Content type: text/html; charset=UTF-8
Checked: https://yukieliot.com
Next/final: https://yukieliot.com
Content type: text/html; charset=UTF-8
Content hash: 108c6acfc078d3657f632657551a743dbcc117d4e50e35634865c611ede59f89
Checked: https://yukieliot.com/robots.txt
Next/final: https://yukieliot.com/robots.txt
Content type: text/plain; charset=UTF-8
Content hash: 2ed89d990870dfcf96cafea521df665abac93308f003c2193348c09d06901db3
Checked: https://yukieliot.com/sitemap.xml
Next/final: https://yukieliot.com/sitemap.xml
Content type: application/xml
Content hash: 31bfbdbd506dd2cc3fb95e47141424ea67e59232bd817d6484ecae26e396da03
Checked: https://yukieliot.com/llms.txt
Next/final: https://yukieliot.com/llms.txt
Content type: text/plain; charset=UTF-8
Content hash: 1f3e86bafa75d863ac3beb887d2d8719b12499e7478ffbf33dbf3c23ab373bcf
Checked: https://yukieliot.com/.env
Next/final: https://yukieliot.com/.env
Content type: text/html
Fetch result: HTTP 404 returned for security_probe.
Checked: https://yukieliot.com/.git/config
Next/final: https://yukieliot.com/.git/config
Content type: text/html
Fetch result: HTTP 403 returned for security_probe.
Checked: https://yukieliot.com/wp-config.php
Next/final: https://yukieliot.com/wp-config.php
Content type: text/html; charset=UTF-8
Fetch result: HTTP 403 returned for security_probe.
Checked: https://yukieliot.com/backup.zip
Next/final: https://yukieliot.com/backup.zip
Content type: text/html
Fetch result: HTTP 404 returned for security_probe.
Captured public headers
content-type
text/html; charset=UTF-8
Share preview
yukieliot.com website audit report
Close to ready: 83/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.