Loading scan status...
completed
HTTP 200
0 redirects
36 checks
Website audit scorecard for yukieliot.com
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
Four-score result
Close to ready (Needs polish): 31 passed, 5 failed, and 0 unknown. Strongest area: SEO / AEO. Weakest area: Accessibility.
Overall
83
out of 100
SEO / AEO
100
out of 100
92/92 rule points
Security
76
out of 100
58/76 rule points
Accessibility
72
out of 100
68/94 rule points
Design
83
out of 100
91/110 rule points
Why this scored this way
Scores are deterministic: each category earns rule points for verified public signals and loses points for failed checks. Unknown checks are shown separately instead of guessed.
Category point breakdown
SEO / AEO92/92
Security58/76
Accessibility68/94
Design91/110
Biggest score-losing checks
high
Security
Common security headersDetected 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.
high
Accessibility
Rendered axe accessibility violationsaxe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (9).
medium
Design
Trust signalsDetected 0 trust-signal keyword occurrence(s).
medium
Design
Rendered layout ergonomicsHorizontal overflow: 0px. Small tap targets: 3.
Recommendations
Score-losing issues ordered by remediation priority, severity, and score impact.
5 fixes
6 opportunities
9 insights
1
fail
high
Security
Priority 5
Add common public security headers
-18 rule ptsWhat 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.
2
fail
high
Accessibility
Priority 5
Fix rendered axe accessibility violations
-18 rule ptsWhat 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.
3
fail
medium
Design
Priority 13
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: 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.
4
fail
medium
Design
Priority 16
Add trust signals
-10 rule ptsWhat 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.
5
fail
medium
Accessibility
Priority 20
Improve detectable color contrast
-8 rule ptsWhat 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.
Unknown and not detected states
FreeScan.app keeps partial public data explicit. It marks unverifiable signals as unknown or not detected instead of inventing evidence.
0 unknown
Safe public scans cannot see private cookies, authenticated content, browser-rendered state, or reliable contrast values unless they are present in static public markup.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.
Score aggregation details
Category scores come from earned rule points divided by available rule points. Failed checks are ordered by severity and score lost.
100/100
11 pass, 0 fail, 0 unknown
SEO / AEO
Severity mix: 0 critical, 6 high, 3 medium, 2 low.
No failed checks in this category.
76/100
5 pass, 1 fail, 0 unknown
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
high
Common security headers
-18 rule ptsDetected 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.
72/100
6 pass, 2 fail, 0 unknown
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
high
Rendered axe accessibility violations
-18 rule ptsaxe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (9).
medium
Basic contrast
-8 rule pts13 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
83/100
9 pass, 2 fail, 0 unknown
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
medium
Trust signals
-10 rule ptsDetected 0 trust-signal keyword occurrence(s).
medium
Rendered layout ergonomics
-9 rule ptsHorizontal overflow: 0px. Small tap targets: 3.
Full check list
Failed, unknown, and passed checks are all shown so the report is transparent even when public data is partial.
Showing failed checks.
Failed checks
These checks need attention.
fail
high
Security
Common security headers
0/18Detected 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.
fail
medium
Accessibility
Basic contrast
0/813 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.
fail
high
Accessibility
Rendered axe accessibility violations
0/18axe 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.
fail
medium
Design
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.
fail
medium
Design
Rendered layout ergonomics
0/9Horizontal 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.
Safe fetch metadata
Public headers and redirects captured during intake. Response bodies, cookies, and credentials are not stored.
Security and accessibility checks are basic automated public checks. They are not a complete security audit, penetration test, privacy review, or WCAG certification.
Landing page
Step 1HTTP 2001 captured header(s)Checked: https://yukieliot.com
Next/final: https://yukieliot.com
Content type: text/html; charset=UTF-8
Landing page
Step 2HTTP 2001 captured header(s)Checked: https://yukieliot.com
Next/final: https://yukieliot.com
Content type: text/html; charset=UTF-8
Content hash: 108c6acfc078d3657f632657551a743dbcc117d4e50e35634865c611ede59f89
robots.txt
Step 3HTTP 2002 captured header(s)Checked: https://yukieliot.com/robots.txt
Next/final: https://yukieliot.com/robots.txt
Content type: text/plain; charset=UTF-8
Content hash: 2ed89d990870dfcf96cafea521df665abac93308f003c2193348c09d06901db3
sitemap.xml
Step 4HTTP 2002 captured header(s)Checked: https://yukieliot.com/sitemap.xml
Next/final: https://yukieliot.com/sitemap.xml
Content type: application/xml
Content hash: 31bfbdbd506dd2cc3fb95e47141424ea67e59232bd817d6484ecae26e396da03
llms.txt
Step 5HTTP 2002 captured header(s)Checked: https://yukieliot.com/llms.txt
Next/final: https://yukieliot.com/llms.txt
Content type: text/plain; charset=UTF-8
Content hash: 1f3e86bafa75d863ac3beb887d2d8719b12499e7478ffbf33dbf3c23ab373bcf
Security probe
Step 6HTTP 4041 captured header(s)Checked: https://yukieliot.com/.env
Next/final: https://yukieliot.com/.env
Content type: text/html
Fetch result: HTTP 404 returned for security_probe.
Security probe
Step 7HTTP 4031 captured header(s)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.
Security probe
Step 8HTTP 4033 captured header(s)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.
Security probe
Step 9HTTP 4041 captured header(s)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
Public report link
Markdown export
Share the website audit report
Copy a public report link or a Markdown version with scores, fixes, opportunities, insights, and a normal link back to the scanned site.
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.
Rescan same URL
Rerun the full deterministic scanner for yukieliot.com without re-entering the URL. The previous report stays saved so the next result can be compared against it.