Speed Insights
Grade A
99% performance
https://svglab.app
From svglab.app
LCP
696ms
Largest paint
TBT
12ms
Blocking time
CLS
0.000
Layout shift
80
out of 100
100
out of 100
110/110 rule points
92
out of 100
66/72 rule points
62
out of 100
52/84 rule points
67
out of 100
74/110 rule points
Category point breakdown
Biggest score-losing checks
Fix rendered axe accessibility violations
Why this needs attention
The rendered page has accessibility rule violations detected by axe-core.
axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
Recommended correction
Evidence
axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: target-size (21).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
All touch targets must be 24px large, or leave sufficient space
Fix any of the following: Target has insufficient size (40px by 21px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 22px instead of at least 24px.
All touch targets must be 24px large, or leave sufficient space
Fix any of the following: Target has insufficient size (40px by 21px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 22px instead of at least 24px.
All touch targets must be 24px large, or leave sufficient space
Fix any of the following: Target has insufficient size (40px by 21px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 22px instead of at least 24px.
Fix Prompt
Label public form fields
Why this needs attention
Some form controls do not have a detectable label or accessible name.
Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
Recommended correction
Evidence
Detected labels or accessible names for 33 of 40 eligible user-facing form control(s).
Priority
Priority 7: fix during launch polish.
Fix Prompt
Add common public security headers
Why this needs attention
Several basic browser protection headers were not visible.
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
Recommended correction
Evidence
Detected 4 of 5 common public security controls. Present: strict-transport-security, x-content-type-options, frame protection (x-frame-options), referrer-policy. Missing: content-security-policy.
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Fix rendered layout ergonomics
Why this needs attention
The browser-rendered page has layout or tap-target issues.
Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
Recommended correction
Evidence
Horizontal overflow: 0px. WCAG 2.2 AA target-size failures: 21. Targets smaller than 24×24px pass only when the required spacing or another WCAG exception applies.
Priority
Priority 13: fix during launch polish.
Affected elements
Interactive control
Target has insufficient size (40px by 21px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 22px instead of at least 24px.
Interactive control
Target has insufficient size (40px by 21px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 22px instead of at least 24px.
Interactive control
Target has insufficient size (40px by 21px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 22px instead of at least 24px.
Interactive control
Target has insufficient size (40px by 21px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 22px instead of at least 24px.
Fix Prompt
Improve rendered speed signals
Why this needs attention
The browser-rendered page shows slow or heavy speed signals.
Slow pages lose impatient visitors and make every SEO, social, and paid-traffic visit work harder.
Recommended correction
Evidence
DOMContentLoaded: 735ms. Load complete: 1002ms. First contentful paint: 696ms. Resources: 18. Scripts: 10. Images: 1. Third-party origins: 9. Transfer: not available. Potential render-blocking resources: 7. Exceeded thresholds: Third-party origins 9 origins (threshold 8 origins).
Priority
Priority 14: fix during launch polish.
Load contributors
Asset timings are observed request durations. They are not added together because browsers can load requests in parallel.
Third-party origins
1 origins over the rendered audit threshold.
app.js
css2
supabase.min.js
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low. Coverage: 0 review and 0 not applicable.
No failed checks in this category.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low. Coverage: 0 review and 1 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low. Coverage: 1 review and 0 not applicable.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low. Coverage: 0 review and 0 not applicable.
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low. Coverage: 0 review and 0 not applicable.
No failed checks in this category.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low. Coverage: 1 review and 0 not applicable.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low. Coverage: 0 review and 1 not applicable.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low. Coverage: 0 review and 0 not applicable.
Failed checks
These checks need attention.
Common security headers
Why this needs attention
Several basic browser protection headers were not visible.
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
Recommended correction
Evidence
Detected 4 of 5 common public security controls. Present: strict-transport-security, x-content-type-options, frame protection (x-frame-options), referrer-policy. Missing: content-security-policy. Failed: earned 12 of 18 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Form labels
Why this needs attention
Some form controls do not have a detectable label or accessible name.
Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
Recommended correction
Evidence
Detected labels or accessible names for 33 of 40 eligible user-facing form control(s). Failed: earned 0 of 14 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 7: fix during launch polish.
Fix Prompt
Rendered axe accessibility violations
Why this needs attention
The rendered page has accessibility rule violations detected by axe-core.
axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
Recommended correction
Evidence
axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: target-size (21). Failed: earned 0 of 18 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 5: fix before sharing the page publicly.
Affected elements
All touch targets must be 24px large, or leave sufficient space
Fix any of the following: Target has insufficient size (40px by 21px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 22px instead of at least 24px.
All touch targets must be 24px large, or leave sufficient space
Fix any of the following: Target has insufficient size (40px by 21px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 22px instead of at least 24px.
All touch targets must be 24px large, or leave sufficient space
Fix any of the following: Target has insufficient size (40px by 21px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 22px instead of at least 24px.
Fix Prompt
Trust signals
Why this needs attention
The page does not expose detectable proof, customer, review, security, or credibility signals.
Trust signals reduce hesitation when strangers see the product for the first time.
Recommended correction
Evidence
Detected 0 trust-signal keyword occurrence(s). Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Spacing consistency
Why this needs attention
The page exposes few consistent spacing signals in class or inline styles.
Consistent spacing helps the page feel deliberate and easier to scan.
Recommended correction
Evidence
Detected 0 spacing class/style signal(s). Failed: earned 0 of 7 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 25: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Rendered speed signals
Why this needs attention
The browser-rendered page shows slow or heavy speed signals.
Slow pages lose impatient visitors and make every SEO, social, and paid-traffic visit work harder.
Recommended correction
Evidence
DOMContentLoaded: 735ms. Load complete: 1002ms. First contentful paint: 696ms. Resources: 18. Scripts: 10. Images: 1. Third-party origins: 9. Transfer: not available. Potential render-blocking resources: 7. Exceeded thresholds: Third-party origins 9 origins (threshold 8 origins). Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 14: fix during launch polish.
Load contributors
Asset timings are observed request durations. They are not added together because browsers can load requests in parallel.
Third-party origins
1 origins over the rendered audit threshold.
app.js
css2
supabase.min.js
Fix Prompt
Rendered layout ergonomics
Why this needs attention
The browser-rendered page has layout or tap-target issues.
Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
Recommended correction
Evidence
Horizontal overflow: 0px. WCAG 2.2 AA target-size failures: 21. Targets smaller than 24×24px pass only when the required spacing or another WCAG exception applies. Failed: earned 0 of 9 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 13: fix during launch polish.
Affected elements
Interactive control
Target has insufficient size (40px by 21px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 22px instead of at least 24px.
Interactive control
Target has insufficient size (40px by 21px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 22px instead of at least 24px.
Interactive control
Target has insufficient size (40px by 21px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 22px instead of at least 24px.
Interactive control
Target has insufficient size (40px by 21px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 22px instead of at least 24px.
Fix Prompt
Page-level AEO readiness
Shared eligibility and content signals that affect every search and answer agent.
Index and citation eligibility
No general noindex directive was detected.
Snippet and answer controls
No general nosnippet or max-snippet:0 control was detected.
Canonical alignment
The canonical resolves to the scanned public URL.
Sitemap coverage and freshness
The exact URL appears in the fetched sitemap with lastmod 2026-08-03.
Structured data
Semantic schema score 100/100. Detected 1 JSON-LD block(s), 0 parse error(s), 15 graph node(s), and types Answer, FAQPage, ImageObject, Offer, Organization, Question, SoftwareApplication, WebApplication, WebSite. The schema type matches the detected page role.
Public or paywalled content
Structured data marks this content as accessible for free.
Entity clarity
Entity alignment scored 100/100 for “SVG Lab - Free Online SVG Editor”. Title/H1 token overlap is 100%; description match detected; identity schema detected.
Answer-ready visible text
Answerability scored 95/100 from 638 main-content words, 11 concise answer block(s), 9 question heading(s), 7 definition(s), 2 list(s), and 0 table(s).
Authorship and accountability
Authorship is not a universal requirement for the detected home page role.
Published or updated date
Freshness metadata is contextual for the detected home page role.
Supporting-source links
Supporting sources are contextual for the detected home page role and do not affect readiness.
Rendered content availability
Rendered audit completed with 155 visible text element(s).
Synthetic search-agent reachability
8 of 8 completed search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
https://svglab.app/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.
OpenAIChatGPT searchOAI-SearchBotAI search
Robots: allowed by * allow: / · line 7
Probe: reachable · HTTP 200 · 99% parity
OpenAIOpenAI model trainingGPTBotModel training
Robots: allowed by * allow: / · line 7
Probe: not tested for this control
OpenAIChatGPT user fetchesChatGPT-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
AnthropicClaude model trainingClaudeBotModel training
Robots: allowed by * allow: / · line 7
Probe: not tested for this control
AnthropicClaude searchClaude-SearchBotAI search
Robots: allowed by * allow: / · line 7
Probe: reachable · HTTP 200 · 99% parity
AnthropicClaude user fetchesClaude-UserUser-requested fetch
Robots: allowed by * allow: / · line 7
Probe: reachable · HTTP 200 · 99% parity
GoogleGoogle Search and AI featuresGooglebotSearch and discovery
Robots: allowed by * allow: / · line 7
Probe: reachable · HTTP 200 · 99% parity
GoogleGemini data use and groundingGoogle-ExtendedData-use policy control
Robots: allowed by * allow: / · line 7
Probe: not tested for this control
MicrosoftBing and CopilotBingbotSearch and discovery
Robots: allowed by * allow: / · line 7
Probe: reachable · HTTP 200 · 99% parity
PerplexityPerplexity searchPerplexityBotAI search
Robots: allowed by * allow: / · line 7
Probe: reachable · HTTP 200 · 99% parity
PerplexityPerplexity user fetchesPerplexity-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
AppleSiri, Spotlight, and Safari searchApplebotSearch and discovery
Robots: allowed by * allow: / · line 7
Probe: reachable · HTTP 200 · 99% parity
AppleApple foundation-model trainingApplebot-ExtendedData-use policy control
Robots: allowed by * allow: / · line 7
Probe: not tested for this control
Mistral AIMistral searchMistralAI-IndexAI search
Robots: allowed by * allow: / · line 7
Probe: reachable · HTTP 200 · 99% parity
Mistral AIMistral user fetchesMistralAI-UserUser-requested fetch
Robots: allowed by * allow: / · line 7
Probe: reachable · HTTP 200 · 99% parity
MetaMeta AI model and product datameta-externalagentModel training
Robots: allowed by * allow: / · line 7
Probe: not tested for this control
MetaMeta AI user fetchesmeta-externalfetcherUser-requested fetch
Robots: allowed by * allow: / · line 7
Probe: reachable · HTTP 200 · 99% parity
AmazonAmazon model trainingAmazonbotModel training
Robots: allowed by * allow: / · line 7
Probe: not tested for this control
AmazonAlexa and Rufus searchAmzn-SearchBotAI search
Robots: allowed by * allow: / · line 7
Probe: reachable · HTTP 200 · 99% parity
AmazonAlexa user fetchesAmzn-UserUser-requested fetch
Robots: allowed by * allow: / · line 7
Probe: reachable · HTTP 200 · 99% parity
Common CrawlOpen web datasetsCCBotModel training
Robots: allowed by * allow: / · line 7
Probe: not tested for this control
Ready combines robots policy, a bounded synthetic User-Agent fetch, indexability, and snippet eligibility. Synthetic probes do not prove vendor-origin traffic. Purple preference states are training or data-use choices and do not lower the AEO score.
The image refreshes from FreeScan after a completed rescan. Clicking it always opens the newest public report saved for this exact scanned URL.
Scan evidence is included as untrusted data. The implementation brief instructs agents to verify findings before editing and to avoid destructive or speculative changes.
