Website audit scorecard for sublimearts.io
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://sublimearts.io/en/shop/backdrop
Final URL
https://www.sublimearts.io/en/shop/backdrop
Created
Jul 24, 2026, 12:52 PM
Safe fetch
192 ms
78
out of 100
72
out of 100
82/114 rule points
100
out of 100
76/76 rule points
46
out of 100
43/94 rule points
92
out of 100
101/110 rule points
Category point breakdown
Biggest score-losing checks
axe found 5 violation rule(s), including 2 serious or critical rule(s). Top rules: label (4), color-contrast (16), heading-order (4), landmark-one-main (1), region (58).
Detected labels or accessible names for 0 of 4 form control(s).
Heading levels found: 1, 5, 5, 5, 5, 2, 3, 3, 3, 2, 2, 3, 3, 3, 3, 2, 4, 4, 4, 4, 4, 4, 4, 4, 3, 2, 2, 3, 3, 2, 4, 4, 4, 4, 2, 4, 4, 4, 4, 4, 4, 4, 2.
Title is 108 characters.
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 2 serious or critical rule(s). Top rules: label (4), color-contrast (16), heading-order (4), landmark-one-main (1), region (58).
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
Label public form fields
-14 rule ptsWhat failed
Some form controls do not have a detectable label or accessible name.
Evidence
Detected labels or accessible names for 0 of 4 form control(s).
Priority
Priority 7: fix during launch polish.
Why it matters
Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
How to fix it
Connect each input to a visible label or an accurate aria-label/aria-labelledby value.
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 206 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
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 108 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.
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, 5, 5, 5, 5, 2, 3, 3, 3, 2, 2, 3, 3, 3, 3, 2, 4, 4, 4, 4, 4, 4, 4, 4, 3, 2, 2, 3, 3, 2, 4, 4, 4, 4, 2, 4, 4, 4, 4, 4, 4, 4, 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, 7 high, 3 medium, 2 low.
Page title
-10 rule ptsTitle is 108 characters.
Meta description
-10 rule ptsMeta description is 206 characters.
Heading structure
-8 rule ptsDetected 1 H1 heading(s) and 43 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 5 violation rule(s), including 2 serious or critical rule(s). Top rules: label (4), color-contrast (16), heading-order (4), landmark-one-main (1), region (58).
Form labels
-14 rule ptsDetected labels or accessible names for 0 of 4 form control(s).
Heading order
-11 rule ptsHeading levels found: 1, 5, 5, 5, 5, 2, 3, 3, 3, 2, 2, 3, 3, 3, 3, 2, 4, 4, 4, 4, 4, 4, 4, 4, 3, 2, 2, 3, 3, 2, 4, 4, 4, 4, 2, 4, 4, 4, 4, 4, 4, 4, 2.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Rendered layout ergonomics
-9 rule ptsHorizontal overflow: 0px. Small tap targets: 46.
Showing failed checks.
Failed checks
These checks need attention.
Page title
0/10Title is 108 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.
Copyable agent prompt
Meta description
0/10Meta description is 206 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 43 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
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.
Copyable agent prompt
Form labels
0/14Detected labels or accessible names for 0 of 4 form control(s).
Failed: earned 0 of 14 points.
Priority: Priority 7: fix during launch polish.
Why it matters: Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
Fix: Connect each input to a visible label or an accurate aria-label/aria-labelledby value.
Copyable agent prompt
Heading order
0/11Heading levels found: 1, 5, 5, 5, 5, 2, 3, 3, 3, 2, 2, 3, 3, 3, 3, 2, 4, 4, 4, 4, 4, 4, 4, 4, 3, 2, 2, 3, 3, 2, 4, 4, 4, 4, 2, 4, 4, 4, 4, 4, 4, 4, 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
Basic contrast
0/824 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.
Copyable agent prompt
Rendered axe accessibility violations
0/18axe found 5 violation rule(s), including 2 serious or critical rule(s). Top rules: label (4), color-contrast (16), heading-order (4), landmark-one-main (1), region (58).
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
Rendered layout ergonomics
0/9Horizontal overflow: 0px. Small tap targets: 46.
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
sublimearts.io website audit report
Close to ready: 78/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.