Speed Insights
Grade A
100% performance
https://sayscroll.com
LCP
324ms
Largest paint
TBT
0ms
Blocking time
CLS
0.000
Layout shift
79
out of 100
91
out of 100
100/110 rule points
81
out of 100
58/72 rule points
63
out of 100
54/86 rule points
82
out of 100
90/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 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (8), region (2).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
You lose your place.
The text runs away.
You sound robotic.
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
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
Write a clear page title
Why this needs attention
The browser title is missing, too short, or too long for a reliable search result headline.
Search engines, social previews, and saved browser tabs use the title to tell people what your product is.
Recommended correction
Evidence
Title is 73 characters.
Priority
Priority 8: 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: 390ms. Load complete: 461ms. First contentful paint: 324ms. Resources: 46. Scripts: 25. Images: 0. Third-party origins: 2. Transfer: not available. Potential render-blocking resources: 2. Exceeded thresholds: Script requests 25 scripts (threshold 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.
Script requests
5 scripts over the rendered audit threshold.
44alv_61ar2zf.css
0cz1d0mv5g_q7.js
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 7 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 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 0 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.
Page title
Why this needs attention
The browser title is missing, too short, or too long for a reliable search result headline.
Search engines, social previews, and saved browser tabs use the title to tell people what your product is.
Recommended correction
Evidence
Title is 73 characters. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 8: 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
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 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (8), region (2). 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
You lose your place.
The text runs away.
You sound robotic.
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
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
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: 390ms. Load complete: 461ms. First contentful paint: 324ms. Resources: 46. Scripts: 25. Images: 0. Third-party origins: 2. Transfer: not available. Potential render-blocking resources: 2. Exceeded thresholds: Script requests 25 scripts (threshold 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.
Script requests
5 scripts over the rendered audit threshold.
44alv_61ar2zf.css
0cz1d0mv5g_q7.js
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-30T08:31:46.311Z.
Structured data
Semantic schema score 80/100. Detected 2 JSON-LD block(s), 0 parse error(s), 27 graph node(s), and types AggregateOffer, AggregateRating, Answer, ContactPoint, FAQPage, Offer, Organization, Question, SoftwareApplication, UnitPriceSpecification, WebSite. The schema type matches the detected page role.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 100/100 for “The AI Teleprompter that scrolls as you speak”. Title/H1 token overlap is 100%; description match detected; identity schema detected.
Answer-ready visible text
Answerability scored 85/100 from 296 main-content words, 8 concise answer block(s), 3 question heading(s), 0 definition(s), 3 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 0 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://sayscroll.com/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.
OAI-SearchBotAI search
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
GPTBotModel training
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index, follow
ChatGPT-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: index, follow
ClaudeBotModel training
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index, follow
Claude-SearchBotAI search
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
Claude-UserUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
GooglebotSearch and discovery
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow; Googlebot meta: index, follow, max-video-preview:-1, max-image-preview:large, max-snippet:-1
Google-ExtendedData-use policy control
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index, follow
BingbotSearch and discovery
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
PerplexityBotAI search
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
Perplexity-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: index, follow
ApplebotSearch and discovery
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
Applebot-ExtendedData-use policy control
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index, follow
MistralAI-IndexAI search
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
MistralAI-UserUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
meta-externalagentModel training
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index, follow
meta-externalfetcherUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
AmazonbotModel training
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index, follow
Amzn-SearchBotAI search
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
Amzn-UserUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
CCBotModel 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.
