Speed Insights
Grade B
83% performance
https://varlock.dev
From Varlock.dev
LCP
664ms
Largest paint
TBT
212ms
Blocking time
CLS
0.20
Layout shift
73
out of 100
84
out of 100
93/111 rule points
76
out of 100
58/76 rule points
57
out of 100
54/94 rule points
74
out of 100
81/110 rule points
Category point breakdown
Biggest score-losing checks
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 0 of 5 common public security controls. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy.
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
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 7 violation rule(s), including 4 serious or critical rule(s). Top rules: button-name (1), image-alt (14), color-contrast (10), link-in-text-block (1), landmark-main-is-top-level (1).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Buttons must have discernible text
Fix any of the following: Element does not have inner text that is visible to screen readers aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute Element does not have an implicit (wrapped) <label> Element does not have an explicit <label> Element's default semantics were not overridden with role="none" or role="presentation"
Images must have alternative text
Fix any of the following: Element does not have an alt attribute aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute Element's default semantics were not overridden with role="none" or role="presentation"
Images must have alternative text
Fix any of the following: Element does not have an alt attribute aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute Element's default semantics were not overridden with role="none" or role="presentation"
Images must have alternative text
Fix any of the following: Element does not have an alt attribute aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute Element's default semantics were not overridden with role="none" or role="presentation"
Fix Prompt
Add a useful meta description
Why this needs attention
The page does not expose a strong short summary for search and answer engines.
A missing description makes previews weaker when early users share or find the page.
Recommended correction
Evidence
Meta description is 197 characters.
Priority
Priority 3: fix before sharing the page publicly.
Fix Prompt
Clarify the hero promise
Why this needs attention
The hero area does not provide enough clear product context.
Visitors decide quickly whether the product is relevant; a vague hero weakens every acquisition channel.
Recommended correction
Evidence
Detected 2 H1 heading(s) and 197 meta-description characters.
Priority
Priority 6: fix during launch polish.
Fix Prompt
Add meaningful image alt text
Why this needs attention
One or more images are missing alt text.
People using screen readers may miss product context, trust signals, or calls to action.
Recommended correction
Evidence
Detected 17 image(s) missing alt text out of 89.
Priority
Priority 11: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Failed checks
These checks need attention.
Meta description
Why this needs attention
The page does not expose a strong short summary for search and answer engines.
A missing description makes previews weaker when early users share or find the page.
Recommended correction
Evidence
Meta description is 197 characters. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 3: fix before sharing the page publicly.
Fix Prompt
Heading structure
Why this needs attention
The page heading structure is either missing a single main heading or skips heading levels.
Clear headings help visitors, search engines, and assistive technology understand the page quickly.
Recommended correction
Evidence
Detected 2 H1 heading(s) and 13 total headings. Failed: earned 0 of 8 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 9: fix during launch polish.
Fix Prompt
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 0 of 5 common public security controls. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy. 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.
Fix Prompt
Image alt text
Why this needs attention
One or more images are missing alt text.
People using screen readers may miss product context, trust signals, or calls to action.
Recommended correction
Evidence
Detected 17 image(s) missing alt text out of 89. Failed: earned 0 of 14 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 11: fix during launch polish.
Fix Prompt
Basic contrast
Why this needs attention
The scanner found text/background color pairs that may be hard to read, or could not verify contrast.
Low contrast makes a launch page feel less polished and can exclude users with low vision.
Recommended correction
Evidence
6 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 3.89. Failed: earned 0 of 8 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 20: lower-risk cleanup after urgent launch blockers.
Affected elements
GitHub
Discord
Get Started
Reference Docs
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 7 violation rule(s), including 4 serious or critical rule(s). Top rules: button-name (1), image-alt (14), color-contrast (10), link-in-text-block (1), landmark-main-is-top-level (1). 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
Buttons must have discernible text
Fix any of the following: Element does not have inner text that is visible to screen readers aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute Element does not have an implicit (wrapped) <label> Element does not have an explicit <label> Element's default semantics were not overridden with role="none" or role="presentation"
Images must have alternative text
Fix any of the following: Element does not have an alt attribute aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute Element's default semantics were not overridden with role="none" or role="presentation"
Images must have alternative text
Fix any of the following: Element does not have an alt attribute aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute Element's default semantics were not overridden with role="none" or role="presentation"
Images must have alternative text
Fix any of the following: Element does not have an alt attribute aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute Element's default semantics were not overridden with role="none" or role="presentation"
Fix Prompt
Hero clarity signals
Why this needs attention
The hero area does not provide enough clear product context.
Visitors decide quickly whether the product is relevant; a vague hero weakens every acquisition channel.
Recommended correction
Evidence
Detected 2 H1 heading(s) and 197 meta-description characters. Failed: earned 0 of 13 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 6: fix during launch polish.
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 1 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 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. Small tap targets: 12. 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
Skip to content
Docs
Blog
...
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
A sitemap index was found; this safe scan did not recursively fetch child sitemaps.
Structured data
Semantic schema score 100/100. Detected 1 JSON-LD block(s), 0 parse error(s), 6 graph node(s), and types ContactPoint, CreativeWork, Offer, Organization, SoftwareApplication, 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 “Varlock - AI-safe .env files”. Title/H1 token overlap is 100%; description match detected; identity schema detected.
Answer-ready visible text
Answerability scored 75/100 from 533 main-content words, 9 concise answer block(s), 0 question heading(s), 6 definition(s), 1 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 166 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://varlock.dev/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.
OpenAIChatGPT searchOAI-SearchBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
OpenAIOpenAI model trainingGPTBotModel training
Robots: allowed
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
Probe: not tested for this control
AnthropicClaude searchClaude-SearchBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
AnthropicClaude user fetchesClaude-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
GoogleGoogle Search and AI featuresGooglebotSearch and discovery
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
GoogleGemini data use and groundingGoogle-ExtendedData-use policy control
Robots: allowed
Probe: not tested for this control
MicrosoftBing and CopilotBingbotSearch and discovery
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
PerplexityPerplexity searchPerplexityBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% 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
Probe: reachable · HTTP 200 · 100% parity
AppleApple foundation-model trainingApplebot-ExtendedData-use policy control
Robots: allowed
Probe: not tested for this control
Mistral AIMistral searchMistralAI-IndexAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Mistral AIMistral user fetchesMistralAI-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
MetaMeta AI model and product datameta-externalagentModel training
Robots: allowed
Probe: not tested for this control
MetaMeta AI user fetchesmeta-externalfetcherUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
AmazonAmazon model trainingAmazonbotModel training
Robots: allowed
Probe: not tested for this control
AmazonAlexa and Rufus searchAmzn-SearchBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
AmazonAlexa user fetchesAmzn-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Common CrawlOpen web datasetsCCBotModel training
Robots: allowed
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.
