Speed Insights
Grade F
43% performance
https://be1st.ai/en
From Be1st.ai
LCP
4.3s
Largest paint
TBT
1980ms
Blocking time
CLS
0.10
Layout shift
84
out of 100
96
out of 100
144/150 rule points
98
out of 100
75/76 rule points
72
out of 100
68/94 rule points
70
out of 100
78/110 rule points
Category point breakdown
Biggest score-losing checks
For your AI agent
Share this audit’s URL with ChatGPT, Claude, or your coding agent to turn findings into fixes. Your agent can open the saved evidence below when it needs more detail; these files never start a new scan.
Agent-readable files
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 6 violation rule(s); 5 non-contrast rule(s) are scored here, including 3 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 2 result(s) require review. Top rules: aria-allowed-attr (1), color-contrast (18), nested-interactive (1), target-size (13), meta-viewport (1).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Elements must only use supported ARIA attributes
Fix all of the following: ARIA attribute is not allowed: aria-pressed="false"
Log in
Elements must meet minimum color contrast ratio thresholds
<button type="button" aria-expanded="false" class="inline-flex items-center gap-1 rounded-full px-2 py-0.5 text-[10px] font-semibold bg-[#FDE9E3] text-[#F06B3C] dark:bg-[#F06B3C]/1
Fix Prompt
Strengthen answer-engine content quality
Why this needs attention
The page is technically discoverable, but its entity clarity, answer-ready copy, structured data, evidence, authorship, or freshness is not yet complete.
Search and answer systems need clear, extractable, verifiable facts in addition to crawl access and metadata.
Recommended correction
Evidence
Role-aware AEO content components: entity clarity 95/100, answer-ready text 83/100, semantic structured data 80/100. Detected role: home (high confidence).
Priority
Priority 6: fix during launch polish.
Fix Prompt
Improve schema quality and validity
Why this needs attention
The JSON-LD may parse, but its required facts, page-role relevance, visible-content agreement, or graph connections are incomplete.
Invalid structured data can be ignored by search and answer systems, even when visible page content is strong.
Recommended correction
Evidence
1 of 1 JSON-LD block(s) parsed. Semantic quality is 80/100: completeness 75/100, graph connectivity 0/100, primary types Organization, currently useful search-feature types Organization. Nested types do not count as separate schema coverage.
Priority
Priority 10: fix during launch polish.
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
Desktop horizontal overflow: 0px. Mobile horizontal overflow at 390px: 0px. WCAG 2.2 AA target-size failures: 13. Targets smaller than 24×24px pass only when the required spacing or another WCAG exception applies.
Priority
Priority 13: fix during launch polish.
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: 766ms. Load complete: 3960ms. First contentful paint: 528ms. Largest contentful paint: 4264ms. Total blocking time: 1980ms. Cumulative layout shift: 0.097. Resources: 59. Scripts: 24. Images: 6. Third-party origins: 3. Transfer: 6303KB. Potential render-blocking resources: 4. Metrics outside the good range: Largest contentful paint 4264ms (good at or below 2500ms; poor range); Total blocking time 1980ms (good at or below 200ms; poor range); Transfer size 6303KB (good at or below 2200KB); Script requests 24 scripts (good at or below 20 scripts).
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.
Largest contentful paint
1764ms over the rendered audit threshold.
Total blocking time
1780ms over the rendered audit threshold.
Transfer size
4103KB over the rendered audit threshold.
Script requests
4 scripts over the rendered audit threshold.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 8 high, 3 medium, 1 low. Coverage: 0 review and 0 not applicable.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low. Coverage: 0 review and 0 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 low. Coverage: 1 review and 0 not applicable.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 low. Coverage: 0 review and 0 not applicable.
SEO / AEO
Severity mix: 1 critical, 8 high, 3 medium, 1 low. Coverage: 0 review and 0 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 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 0 not applicable.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 low. Coverage: 0 review and 0 not applicable.
Failed checks
These checks need attention.
Answer-engine content quality
Why this needs attention
The page is technically discoverable, but its entity clarity, answer-ready copy, structured data, evidence, authorship, or freshness is not yet complete.
Search and answer systems need clear, extractable, verifiable facts in addition to crawl access and metadata.
Recommended correction
Evidence
Role-aware AEO content components: entity clarity 95/100, answer-ready text 83/100, semantic structured data 80/100. Detected role: home (high confidence). Failed: earned 35 of 40 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 6: fix during launch polish.
Fix Prompt
Schema quality and validity
Why this needs attention
The JSON-LD may parse, but its required facts, page-role relevance, visible-content agreement, or graph connections are incomplete.
Invalid structured data can be ignored by search and answer systems, even when visible page content is strong.
Recommended correction
Evidence
1 of 1 JSON-LD block(s) parsed. Semantic quality is 80/100: completeness 75/100, graph connectivity 0/100, primary types Organization, currently useful search-feature types Organization. Nested types do not count as separate schema coverage. Failed: earned 7 of 8 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 10: fix during launch polish.
Fix Prompt
Visible cookie flags
Why this needs attention
The safe public scan could not inspect private or browser-set cookies, so cookie flag coverage was not verified.
Session and preference cookies should avoid unnecessary exposure before early users sign in or submit forms.
Recommended correction
Evidence
Observed 1 cookie(s) without storing names or values. Secure: 1/1. HttpOnly: 0/1. SameSite: 1/1. SameSite=None without Secure: 0. Failed: earned 3 of 4 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 20: lower-risk cleanup after urgent launch blockers.
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
30 of 274 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 2.14. Mobile 390px viewport: 16 of 161 failed; worst ratio 2.14:1. 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
View all 15
View all 7
View all 7
View all 14
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 6 violation rule(s); 5 non-contrast rule(s) are scored here, including 3 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 2 result(s) require review. Top rules: aria-allowed-attr (1), color-contrast (18), nested-interactive (1), target-size (13), meta-viewport (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
Elements must only use supported ARIA attributes
Fix all of the following: ARIA attribute is not allowed: aria-pressed="false"
Log in
Elements must meet minimum color contrast ratio thresholds
<button type="button" aria-expanded="false" class="inline-flex items-center gap-1 rounded-full px-2 py-0.5 text-[10px] font-semibold bg-[#FDE9E3] text-[#F06B3C] dark:bg-[#F06B3C]/1
Fix Prompt
Credibility and proof
Why this needs attention
The page does not expose enough verifiable credibility for its detected role.
Trust signals reduce hesitation when strangers see the product for the first time.
Recommended correction
Evidence
Detected 0 commercial proof signal(s) and 1 source or methodology signal(s) for this home page. Failed: earned 5 of 10 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Rendered composition and spacing
Why this needs attention
Rendered geometry found cramped text, overly long lines, undersized body copy, or too many competing actions in the first viewport.
Consistent spacing helps the page feel deliberate and easier to scan.
Recommended correction
Evidence
Desktop 1366px: 2 unique above-fold action(s), 1 body sample(s) below 14px, 0 cramped line-height sample(s), and 0 overlong line sample(s). Mobile 390px: 3 unique above-fold action(s), 1 body sample(s) below 14px, 0 cramped line-height sample(s), and 0 overlong line sample(s). Repeated CTA labels are deduplicated and do not earn extra credit. Failed: earned 2 of 7 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 25: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Visual hierarchy
Why this needs attention
Rendered typography, geometry, and contrast show that the main heading is not distinct or legible enough, or that the hierarchy needs manual review.
Hierarchy tells visitors what to read first and what action to take next.
Recommended correction
Evidence
The rendered H1 is 60px/700 weight versus a 15px/400 median body style (4× size). Captured 12 supporting heading(s) and 63 action(s). The main heading has a clear rendered emphasis over body copy. 30 of 274 rendered text samples missed contrast targets, so hierarchy is not considered fully legible. Failed: earned 6 of 9 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 12: fix during launch polish.
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: 766ms. Load complete: 3960ms. First contentful paint: 528ms. Largest contentful paint: 4264ms. Total blocking time: 1980ms. Cumulative layout shift: 0.097. Resources: 59. Scripts: 24. Images: 6. Third-party origins: 3. Transfer: 6303KB. Potential render-blocking resources: 4. Metrics outside the good range: Largest contentful paint 4264ms (good at or below 2500ms; poor range); Total blocking time 1980ms (good at or below 200ms; poor range); Transfer size 6303KB (good at or below 2200KB); Script requests 24 scripts (good at or below 20 scripts). 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.
Largest contentful paint
1764ms over the rendered audit threshold.
Total blocking time
1780ms over the rendered audit threshold.
Transfer size
4103KB over the rendered audit threshold.
Script requests
4 scripts over the rendered audit threshold.
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
Desktop horizontal overflow: 0px. Mobile horizontal overflow at 390px: 0px. WCAG 2.2 AA target-size failures: 13. 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.
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-09-14T03:09:17.749Z.
Structured data
Semantic schema score 80/100. Detected 1 JSON-LD block(s), 0 parse error(s), 2 graph node(s), and primary types Organization. Completeness: 75/100. Graph connectivity: 0/100. A primary schema type matches the detected page role. The schema entity is supported by visible page content.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 95/100 for “The Website Control Layerfor Humans and AI Agents.”. Title/H1 token overlap is 83%; description match detected; identity schema detected.
Answer-ready visible text
Answerability scored 83/100 from 274 main-content words, 8 concise answer block(s), 2 question heading(s), 1 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 143 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://be1st.ai/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.
OpenAIChatGPT searchOAI-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by oai-searchbot allow: / · line 40
Synthetic probe: reachable · HTTP 200 · 31% sampled-content parity
OpenAIOpenAI model trainingGPTBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by gptbot allow: / · line 34
Synthetic probe: not applicable to this policy control
OpenAIChatGPT user fetchesChatGPT-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: not applicable to user-requested fetches
Synthetic probe: not tested · access is unverified
AnthropicClaude model trainingClaudeBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by claudebot allow: / · line 44
Synthetic probe: not applicable to this policy control
AnthropicClaude searchClaude-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by claude-searchbot allow: / · line 53
Synthetic probe: reachable · HTTP 200 · 31% sampled-content parity
AnthropicClaude user fetchesClaude-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by claude-user allow: / · line 56
Synthetic probe: reachable · HTTP 200 · 31% sampled-content parity
GoogleGoogle Search and AI featuresGooglebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 21
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
GoogleGemini data use and groundingGoogle-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed by google-extended allow: / · line 67
Synthetic probe: not applicable to this policy control
MicrosoftBing and CopilotBingbotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 21
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
PerplexityPerplexity searchPerplexityBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by perplexitybot allow: / · line 60
Synthetic probe: reachable · HTTP 200 · 31% sampled-content parity
PerplexityPerplexity user fetchesPerplexity-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: not applicable to user-requested fetches
Synthetic probe: not tested · access is unverified
AppleSiri, Spotlight, and Safari searchApplebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by applebot allow: / · line 92
Synthetic probe: reachable · HTTP 200 · 31% sampled-content parity
AppleApple foundation-model trainingApplebot-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed by applebot allow: / · line 92
Synthetic probe: not applicable to this policy control
Mistral AIMistral searchMistralAI-IndexPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 21
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
Mistral AIMistral user fetchesMistralAI-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by mistralai-user allow: / · line 104
Synthetic probe: reachable · HTTP 200 · 31% sampled-content parity
MetaMeta AI model and product datameta-externalagentPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by meta-externalagent allow: / · line 78
Synthetic probe: not applicable to this policy control
MetaMeta AI user fetchesmeta-externalfetcherPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by meta-externalfetcher allow: / · line 81
Synthetic probe: reachable · HTTP 200 · 31% sampled-content parity
AmazonAmazon model trainingAmazonbotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by amazonbot allow: / · line 96
Synthetic probe: not applicable to this policy control
AmazonAlexa and Rufus searchAmzn-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 21
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
AmazonAlexa user fetchesAmzn-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 21
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
Common CrawlOpen web datasetsCCBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by ccbot allow: / · line 74
Synthetic probe: not applicable to this policy control
Ready combines robots policy, a bounded synthetic User-Agent fetch, indexability, and snippet eligibility. Synthetic probes do not prove vendor-origin traffic. 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.
