Speed Insights
Incomplete capture
Missing LCP, TBT, CLS
https://bizconnectus.com
LCP
N/A
Largest paint
TBT
N/A
Blocking time
CLS
N/A
Layout shift
61
out of 100
79
out of 100
88/111 rule points
76
out of 100
58/76 rule points
10
out of 100
9/94 rule points
79
out of 100
87/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 headers. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, x-frame-options, 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 3 violation rule(s), including 0 serious or critical rule(s). Top rules: landmark-one-main (1), page-has-heading-one (1), region (1).
Priority
Priority 5: fix before sharing the page publicly.
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 0 of 2 form control(s).
Priority
Priority 7: fix during launch polish.
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 12 H1 heading(s) and 164 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 82 image(s) missing alt text out of 161.
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.
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 12 H1 heading(s) and 190 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
Canonical tag
Why this needs attention
The page does not declare which public URL is the preferred version.
A canonical tag reduces duplicate URL confusion before marketing links start spreading.
Recommended correction
Evidence
No canonical link tag was detected. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 9: fix during launch polish.
Fix Prompt
Open Graph basics
Why this needs attention
The page is missing several social preview fields.
Launch links on X, LinkedIn, Slack, and communities look less trustworthy without a strong preview.
Recommended correction
Evidence
Detected 0 of 4 Open Graph basics. Failed: earned 0 of 5 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 18: lower-risk cleanup after urgent launch blockers.
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 headers. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, x-frame-options, 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 82 image(s) missing alt text out of 161. 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
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 0 of 2 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
Heading order
Why this needs attention
Heading levels appear to jump or start without a clear hierarchy.
A clean heading outline helps visitors scan the page and helps assistive technology navigate it.
Recommended correction
Evidence
Heading levels found: 1, 3, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 1, 1, 2, 3, 2, 4, 1, 2, 3, 2, 4, 1, 1, 1, 1, 2, 3, 3, 3, 3, 2, 3, 3, 3, 3, 3, 3, 3, 1, 2, 2, 2, 2, 1, 2, 2, 2, 2, 1, 2, 3, 2, 3, 2, 3, 2, 3, 2, 3, 2, 3, 2, 3, 2, 3, 2, 3, 2, 3, 1, 2, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 2, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 2, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 2, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 2, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 2, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 3, 3, 3, 3, 3, 3, 3. Failed: earned 0 of 11 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 13: fix during launch polish.
Fix Prompt
Landmark presence
Why this needs attention
The page is missing common landmarks such as header, nav, main, or footer.
Landmarks make the page easier to navigate for assistive technology and keyboard users.
Recommended correction
Evidence
Detected 0 landmark element(s) or roles. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 18: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Semantic buttons and links
Why this needs attention
Interactive controls are not consistently represented as semantic buttons or links.
Non-semantic controls can be hard to use with keyboards and screen readers.
Recommended correction
Evidence
Detected 1 semantic control(s) out of 13. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 17: 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
2 of 3 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 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.
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 3 violation rule(s), including 0 serious or critical rule(s). Top rules: landmark-one-main (1), page-has-heading-one (1), region (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.
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 12 H1 heading(s) and 164 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
Text density
Why this needs attention
The page has too little or too much detectable text for a useful launch page.
Too little copy can leave visitors confused; too much copy can bury the value proposition.
Recommended correction
Evidence
Detected about 5062 visible word(s). Long-form article range: 80-5000 words. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 21: lower-risk cleanup after urgent launch blockers.
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
No canonical URL was detected.
Sitemap coverage and freshness
The exact URL appears in sitemap.xml with lastmod 2022-07-07T11:21:30+00:00.
Structured data
Detected 1 JSON-LD block(s), 0 parse error(s), and types Answer, FAQPage, Question.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Detected 2 of 3 core identity signals across the title, description, and H1.
Answer-ready visible text
Detected 5062 visible words and 161 audience, use-case, pricing, or integration signals.
Authorship and accountability
No author meta value or structured-data author was detected.
Published or updated date
No datePublished or dateModified value was detected in structured data.
Supporting-source links
Detected 27 external source or reference link(s); link quality still requires editorial review.
Rendered content availability
Rendered audit completed with 3 visible text element(s).
Synthetic search-agent reachability
8 of 8 search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
No llms.txt file was found; this is optional and does not reduce core AEO readiness.
OpenAIChatGPT searchOAI-SearchBotAI search
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 2% parity
Controls: robots meta: index, follow
OpenAIOpenAI model trainingGPTBotModel training
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index, follow
OpenAIChatGPT user fetchesChatGPT-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: index, follow
AnthropicClaude model trainingClaudeBotModel training
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index, follow
AnthropicClaude searchClaude-SearchBotAI search
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 2% parity
Controls: robots meta: index, follow
AnthropicClaude user fetchesClaude-UserUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 2% parity
Controls: robots meta: index, follow
GoogleGoogle Search and AI featuresGooglebotSearch and discovery
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 2% parity
Controls: robots meta: index, follow
GoogleGemini data use and groundingGoogle-ExtendedData-use policy control
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index, follow
MicrosoftBing and CopilotBingbotSearch and discovery
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 2% parity
Controls: robots meta: index, follow
PerplexityPerplexity searchPerplexityBotAI search
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 2% parity
Controls: robots meta: index, follow
PerplexityPerplexity user fetchesPerplexity-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: index, follow
AppleSiri, Spotlight, and Safari searchApplebotSearch and discovery
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 2% parity
Controls: robots meta: index, follow
AppleApple foundation-model trainingApplebot-ExtendedData-use policy control
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index, follow
Mistral AIMistral searchMistralAI-IndexAI search
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 2% parity
Controls: robots meta: index, follow
Mistral AIMistral user fetchesMistralAI-UserUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 2% parity
Controls: robots meta: index, follow
MetaMeta AI model and product datameta-externalagentModel training
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index, follow
MetaMeta AI user fetchesmeta-externalfetcherUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 2% parity
Controls: robots meta: index, follow
AmazonAmazon model trainingAmazonbotModel training
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index, follow
AmazonAlexa and Rufus searchAmzn-SearchBotAI search
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 2% parity
Controls: robots meta: index, follow
AmazonAlexa user fetchesAmzn-UserUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 2% parity
Controls: robots meta: index, follow
Common CrawlOpen web datasetsCCBotModel training
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index, follow
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.
