Speed Insights
Grade B
88% performance
https://www.healmeup.com
LCP
1.3s
Largest paint
TBT
348ms
Blocking time
CLS
0.03
Layout shift
69
out of 100
93
out of 100
102/110 rule points
81
out of 100
58/72 rule points
46
out of 100
43/94 rule points
57
out of 100
63/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 1 of 5 common public security controls. Present: strict-transport-security. Missing: 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 5 violation rule(s), including 3 serious or critical rule(s). Top rules: color-contrast (16), link-name (4), target-size (9), heading-order (2), region (1).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Görü
Görüşmeye Başla</but
Görüşmeye Başla</but
Links must have discernible text
Fix all of the following: Element is in tab order and does not have accessible text Fix any of the following: Element does not have 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
Fix Prompt
Make the primary CTA obvious
Why this needs attention
The page does not have a detectable call to action.
Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
Recommended correction
Evidence
No actionable link or button with a clear CTA label was detected.
Priority
Priority 4: 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 1 eligible user-facing 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 1 H1 heading(s), 52 H1 characters, 134 supporting-copy characters, and 0 actionable CTA(s).
Priority
Priority 6: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low. Coverage: 0 review and 1 not applicable.
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: 0 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 1 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low. Coverage: 0 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.
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 1 H1 heading(s) and 56 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 1 of 5 common public security controls. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy. Failed: earned 4 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 0 of 1 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
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, 3, 3, 2, 2, 2, 2, 2, 2, 2, 3, 3, 3, 3, 3, 3, 2, 2, 2, 2, 2, 3, 3, 3, 3, 3, 3, 3, 3, 2, 3, 3, 3, 3, 2, 2, 2, 2, 3, 3, 3, 3, 3, 3, 3, 2, 4, 4, 4, 4, 4, 4, 4, 4, 4. 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
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
15 of 100 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.
Affected elements
Heally
Kendini Tanıma Araçları
Şirketler İçin
Blog
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 5 violation rule(s), including 3 serious or critical rule(s). Top rules: color-contrast (16), link-name (4), target-size (9), heading-order (2), 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.
Affected elements
Görü
Görüşmeye Başla</but
Görüşmeye Başla</but
Links must have discernible text
Fix all of the following: Element is in tab order and does not have accessible text Fix any of the following: Element does not have 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
Fix Prompt
Visible primary CTA
Why this needs attention
The page does not have a detectable call to action.
Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
Recommended correction
Evidence
No actionable link or button with a clear CTA label was detected. Failed: earned 0 of 14 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 4: 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 1 H1 heading(s), 52 H1 characters, 134 supporting-copy characters, and 0 actionable CTA(s). Failed: earned 11 of 13 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 6: fix during launch polish.
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 strong, specific trust or proof signal(s). Generic words such as “security” do not count by themselves. 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
Visual hierarchy
Why this needs attention
The page does not expose enough hierarchy signals from headings, emphasis, or CTA structure.
Hierarchy tells visitors what to read first and what action to take next.
Recommended correction
Evidence
Detected 3 of 4 hierarchy signals from one H1, supporting headings, an actionable CTA, and emphasized text. Failed: earned 7 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: 1450ms. Load complete: 1656ms. First contentful paint: 1340ms. Resources: 100. Scripts: 40. Images: 14. Third-party origins: 13. Transfer: not available. Potential render-blocking resources: 3. Exceeded thresholds: Script requests 40 scripts (threshold 20 scripts); Third-party origins 13 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.
Script requests
20 scripts over the rendered audit threshold.
Third-party origins
5 origins over the rendered audit threshold.
e9bc2acb63f320ad.css
567b3ff538293f0c.css
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: 9. 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
Go to page 1
Target has insufficient size (12px by 12px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 20px instead of at least 24px.
Go to page 2
Target has insufficient size (12px by 12px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 20px instead of at least 24px.
Go to page 3
Target has insufficient size (12px by 12px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 20px instead of at least 24px.
Go to page 4
Target has insufficient size (12px by 12px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 20px 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
A sitemap index was found; this safe scan did not recursively fetch child sitemaps.
Structured data
Semantic schema score 65/100. Detected 1 JSON-LD block(s), 0 parse error(s), 4 graph node(s), and types Organization, Person, Place, PostalAddress. The schema type matches the detected page role.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 82/100 for “Online Psikolog İyi olma yolculuğunda yanındayız”. Title/H1 token overlap is 40%; description match detected; identity schema detected.
Answer-ready visible text
Answerability scored 40/100 from 230 main-content words, 0 concise answer block(s), 11 question heading(s), 0 definition(s), 0 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 216 visible text element(s).
Synthetic search-agent reachability
8 of 8 completed 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
Probe: reachable · HTTP 200 · 99% parity
Controls: robots meta: index, follow
OpenAIOpenAI model trainingGPTBotModel training
Robots: allowed
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
Probe: not tested for this control
Controls: robots meta: index, follow
AnthropicClaude searchClaude-SearchBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 99% parity
Controls: robots meta: index, follow
AnthropicClaude user fetchesClaude-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 99% parity
Controls: robots meta: index, follow
GoogleGoogle Search and AI featuresGooglebotSearch and discovery
Robots: allowed
Probe: reachable · HTTP 200 · 99% parity
Controls: robots meta: index, follow
GoogleGemini data use and groundingGoogle-ExtendedData-use policy control
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow
MicrosoftBing and CopilotBingbotSearch and discovery
Robots: allowed
Probe: reachable · HTTP 200 · 99% parity
Controls: robots meta: index, follow
PerplexityPerplexity searchPerplexityBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 99% 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
Probe: reachable · HTTP 200 · 99% parity
Controls: robots meta: index, follow
AppleApple foundation-model trainingApplebot-ExtendedData-use policy control
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow
Mistral AIMistral searchMistralAI-IndexAI search
Robots: allowed
Probe: reachable · HTTP 200 · 99% parity
Controls: robots meta: index, follow
Mistral AIMistral user fetchesMistralAI-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 99% parity
Controls: robots meta: index, follow
MetaMeta AI model and product datameta-externalagentModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow
MetaMeta AI user fetchesmeta-externalfetcherUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 99% parity
Controls: robots meta: index, follow
AmazonAmazon model trainingAmazonbotModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow
AmazonAlexa and Rufus searchAmzn-SearchBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 99% parity
Controls: robots meta: index, follow
AmazonAlexa user fetchesAmzn-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 99% parity
Controls: robots meta: index, follow
Common CrawlOpen web datasetsCCBotModel training
Robots: allowed
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.
