Website audit scorecard for shipcheck.fyi
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://shipcheck.fyi/
Final URL
https://shipcheck.fyi
Created
Jul 22, 2026, 2:51 AM
Safe fetch
167 ms
77
out of 100
74
out of 100
78/106 rule points
100
out of 100
76/76 rule points
50
out of 100
47/94 rule points
83
out of 100
91/110 rule points
Category point breakdown
Biggest score-losing checks
axe found 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (42), heading-order (1).
Heading levels found: 1, 3, 3, 3, 3, 3, 3, 3, 3, 3, 2, 2.
Meta description is 208 characters.
Detected 0 JSON-LD schema block(s).
Fix rendered axe accessibility violations
-18 rule ptsWhat failed
The rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (42), 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.
Copyable agent prompt
Add a useful meta description
-10 rule ptsWhat failed
The page does not expose a strong short summary for search and answer engines.
Evidence
Meta description is 208 characters.
Priority
Priority 3: fix before sharing the page publicly.
Why it matters
A missing description makes previews weaker when early users share or find the page.
How to fix it
Add a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.
Copyable agent prompt
Add basic structured data
-10 rule ptsWhat failed
No JSON-LD schema was detected on the page.
Evidence
Detected 0 JSON-LD schema block(s).
Priority
Priority 12: fix during launch polish.
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.
Copyable agent prompt
Use one clear H1 and ordered headings
-8 rule ptsWhat failed
The page heading structure is either missing a single main heading or skips heading levels.
Evidence
Detected 1 H1 heading(s) and 12 total headings.
Priority
Priority 9: fix during launch polish.
Why it matters
Clear headings help visitors, search engines, and assistive technology understand the page quickly.
How to fix it
Keep one H1 for the main promise, then use H2 and H3 headings in order for sections below it.
Copyable agent prompt
Fix heading order
-11 rule ptsWhat failed
Heading levels appear to jump or start without a clear hierarchy.
Evidence
Heading levels found: 1, 3, 3, 3, 3, 3, 3, 3, 3, 3, 2, 2.
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.
How to fix it
Use headings in order: one H1, then H2 for major sections, then H3 for subsections.
Copyable agent prompt
SEO / AEO
Severity mix: 1 critical, 6 high, 3 medium, 2 low.
Meta description
-10 rule ptsMeta description is 208 characters.
Schema presence
-10 rule ptsDetected 0 JSON-LD schema block(s).
Heading structure
-8 rule ptsDetected 1 H1 heading(s) and 12 total headings.
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 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (42), heading-order (1).
Heading order
-11 rule ptsHeading levels found: 1, 3, 3, 3, 3, 3, 3, 3, 3, 3, 2, 2.
Semantic buttons and links
-10 rule ptsDetected 4 semantic control(s) out of 13.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Trust signals
-10 rule ptsDetected 0 trust-signal keyword occurrence(s).
Rendered layout ergonomics
-9 rule ptsHorizontal overflow: 0px. Small tap targets: 17.
Showing failed checks.
Failed checks
These checks need attention.
Meta description
0/10Meta description is 208 characters.
Failed: earned 0 of 10 points.
Priority: Priority 3: fix before sharing the page publicly.
Why it matters: A missing description makes previews weaker when early users share or find the page.
Fix: Add a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.
Copyable agent prompt
Heading structure
0/8Detected 1 H1 heading(s) and 12 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.
Copyable agent prompt
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.
Copyable agent prompt
Heading order
0/11Heading levels found: 1, 3, 3, 3, 3, 3, 3, 3, 3, 3, 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.
Copyable agent prompt
Semantic buttons and links
0/10Detected 4 semantic control(s) out of 13.
Failed: earned 0 of 10 points.
Priority: Priority 17: lower-risk cleanup after urgent launch blockers.
Why it matters: Non-semantic controls can be hard to use with keyboards and screen readers.
Fix: Use button for actions and anchor links for navigation, with clear accessible names.
Copyable agent prompt
Basic contrast
0/824 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 3.62.
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 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (42), 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.
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
Rendered layout ergonomics
0/9Horizontal overflow: 0px. Small tap targets: 17.
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
shipcheck.fyi website audit report
Close to ready: 77/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.