Website audit scorecard for taishikato.com
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
taishikato.com
Final URL
https://taishikato.com
Created
Jul 4, 2026, 8:32 PM
Safe fetch
92 ms
62
out of 100
36
out of 100
33/92 rule points
83
out of 100
63/76 rule points
61
out of 100
57/94 rule points
67
out of 100
74/110 rule points
Category point breakdown
Biggest score-losing checks
axe found 5 violation rule(s), including 4 serious or critical rule(s). Top rules: color-contrast (5), frame-title (1), link-name (5), svg-img-alt (1), heading-order (1).
Detected 2 of 5 common public security headers. Present: x-content-type-options, referrer-policy. Missing: strict-transport-security, content-security-policy, x-frame-options.
HTTP 404 returned for sitemap_xml.
Heading levels found: 1, 3, 2, 3, 3, 3, 2, 2, 2, 2.
Fix rendered axe accessibility violations
-18 rule ptsWhat failed
The rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 5 violation rule(s), including 4 serious or critical rule(s). Top rules: color-contrast (5), frame-title (1), link-name (5), svg-img-alt (1), heading-order (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.
Add common public security headers
-13 rule ptsWhat failed
Several basic browser protection headers were not visible.
Evidence
Detected 2 of 5 common public security headers. Present: x-content-type-options, referrer-policy. Missing: strict-transport-security, content-security-policy, x-frame-options.
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.
Publish sitemap.xml
-12 rule ptsWhat failed
The sitemap file was not reachable.
Evidence
HTTP 404 returned for sitemap_xml.
Priority
Priority 7: fix during launch polish.
Why it matters
A sitemap helps search engines discover the landing page and related public pages sooner.
How to fix it
Add /sitemap.xml with your public URLs and confirm it returns HTTP 200.
Write a clear page title
-10 rule ptsWhat failed
The browser title is missing, too short, or too long for a reliable search result headline.
Evidence
Title is 6 characters.
Priority
Priority 8: fix during launch polish.
Why it matters
Search engines, social previews, and saved browser tabs use the title to tell people what your product is.
How to fix it
Set one concise title tag, ideally 10 to 70 characters, that includes the product name and the main promise.
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.
SEO / AEO
Severity mix: 0 critical, 6 high, 3 medium, 2 low.
sitemap.xml reachability
-12 rule ptsHTTP 404 returned for sitemap_xml.
Page title
-10 rule ptsTitle is 6 characters.
Canonical tag
-10 rule ptsNo canonical link tag was detected.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Common security headers
-13 rule ptsDetected 2 of 5 common public security headers. Present: x-content-type-options, referrer-policy. Missing: strict-transport-security, content-security-policy, x-frame-options.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Rendered axe accessibility violations
-18 rule ptsaxe found 5 violation rule(s), including 4 serious or critical rule(s). Top rules: color-contrast (5), frame-title (1), link-name (5), svg-img-alt (1), heading-order (1).
Heading order
-11 rule ptsHeading levels found: 1, 3, 2, 3, 3, 3, 2, 2, 2, 2.
Basic contrast
-8 rule pts5 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 2.83.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Trust signals
-10 rule ptsDetected 0 trust-signal keyword occurrence(s).
Rendered speed signals
-10 rule ptsDOMContentLoaded: 467ms. Load complete: 5745ms. First contentful paint: 528ms. Resources: 28. Scripts: 11. Images: 5. Third-party origins: 5. Transfer: not available.
Rendered layout ergonomics
-9 rule ptsHorizontal overflow: 0px. Small tap targets: 13.
Showing failed checks.
Failed checks
These checks need attention.
Page title
0/10Title is 6 characters.
Failed: earned 0 of 10 points.
Priority: Priority 8: fix during launch polish.
Why it matters: Search engines, social previews, and saved browser tabs use the title to tell people what your product is.
Fix: Set one concise title tag, ideally 10 to 70 characters, that includes the product name and the main promise.
Heading structure
0/8Detected 1 H1 heading(s) and 10 total headings.
Failed: earned 0 of 8 points.
Priority: Priority 9: fix during launch polish.
Why it matters: Clear headings help visitors, search engines, and assistive technology understand the page quickly.
Fix: Keep one H1 for the main promise, then use H2 and H3 headings in order for sections below it.
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.
sitemap.xml reachability
0/12HTTP 404 returned for sitemap_xml.
Failed: earned 0 of 12 points.
Priority: Priority 7: fix during launch polish.
Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.
Fix: Add /sitemap.xml with your public URLs and confirm it returns HTTP 200.
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.
Open Graph basics
0/5Detected 0 of 4 Open Graph basics.
Failed: earned 0 of 5 points.
Priority: Priority 18: lower-risk cleanup after urgent launch blockers.
Why it matters: Launch links on X, LinkedIn, Slack, and communities look less trustworthy without a strong preview.
Fix: Add og:title, og:description, og:image, and og:url that match the landing page content.
Common security headers
5/18Detected 2 of 5 common public security headers. Present: x-content-type-options, referrer-policy. Missing: strict-transport-security, content-security-policy, x-frame-options.
Failed: earned 5 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.
Heading order
0/11Heading levels found: 1, 3, 2, 3, 3, 3, 2, 2, 2, 2.
Failed: earned 0 of 11 points.
Priority: Priority 13: fix during launch polish.
Why it matters: A clean heading outline helps visitors scan the page and helps assistive technology navigate it.
Fix: Use headings in order: one H1, then H2 for major sections, then H3 for subsections.
Basic contrast
0/85 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 2.83.
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.
Rendered axe accessibility violations
0/18axe found 5 violation rule(s), including 4 serious or critical rule(s). Top rules: color-contrast (5), frame-title (1), link-name (5), svg-img-alt (1), heading-order (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.
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.
Rendered speed signals
0/10DOMContentLoaded: 467ms. Load complete: 5745ms. First contentful paint: 528ms. Resources: 28. Scripts: 11. Images: 5. Third-party origins: 5. 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.
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: 13.
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
taishikato.com website audit report
Needs fixes before launch: 62/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.