Speed Insights
Grade A
97% performance
https://www.intifyd.com
From www.intifyd.com
LCP
760ms
Largest paint
TBT
0ms
Blocking time
CLS
0.07
Layout shift
78
out of 100
91
out of 100
100/110 rule points
75
out of 100
54/72 rule points
61
out of 100
40/66 rule points
85
out of 100
93/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 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (21), meta-viewport (1).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
I. THE GAP
CASE FILE 01 · PRODUCTION READINESS
CONFIDENTIAL WORKING THESIS
Zooming and scaling must not be disabled
Fix any of the following: maximum-scale on <meta> tag disables zooming on mobile devices
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 180 characters.
Priority
Priority 3: fix before sharing the page publicly.
Fix Prompt
Add 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).
Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Improve detectable color 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
24 of 91 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.44.
Priority
Priority 20: lower-risk cleanup after urgent launch blockers.
Affected elements
01
CONFIDENTIAL WORKING THESIS
missing infrastructure
EXPLORE:
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 2 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 2 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.
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 180 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
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
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
24 of 91 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.44. 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
01
CONFIDENTIAL WORKING THESIS
missing infrastructure
EXPLORE:
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 (21), 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
I. THE GAP
CASE FILE 01 · PRODUCTION READINESS
CONFIDENTIAL WORKING THESIS
Zooming and scaling must not be disabled
Fix any of the following: maximum-scale on <meta> tag disables zooming on mobile devices
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
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 0 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
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.
Structured data
Semantic schema score 55/100. Detected 1 JSON-LD block(s), 0 parse error(s), 1 graph node(s), and types 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 74/100 for “Turn a screenplay or original IP into a clearer route to production.”. Title/H1 token overlap is 14%; description match detected; identity schema detected.
Answer-ready visible text
Answerability scored 80/100 from 197 main-content words, 4 concise answer block(s), 2 question heading(s), 2 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 91 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.
OAI-SearchBotAI search
Robots: allowed by oai-searchbot allow: / · line 63
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
GPTBotModel training
Robots: blocked by gptbot disallow: / · line 55
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: blocked by claudebot disallow: / · line 46
Probe: not tested for this control
Controls: robots meta: index,follow
Claude-SearchBotAI search
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
Claude-UserUser-requested fetch
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
GooglebotSearch and discovery
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
Google-ExtendedData-use policy control
Robots: blocked by google-extended disallow: / · line 52
Probe: not tested for this control
Controls: robots meta: index,follow
BingbotSearch and discovery
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
PerplexityBotAI search
Robots: allowed by * allow: / · line 31
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 31
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
Applebot-ExtendedData-use policy control
Robots: blocked by applebot-extended disallow: / · line 37
Probe: not tested for this control
Controls: robots meta: index,follow
MistralAI-IndexAI search
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
MistralAI-UserUser-requested fetch
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
meta-externalagentModel training
Robots: blocked by meta-externalagent disallow: / · line 58
Probe: not tested for this control
Controls: robots meta: index,follow
meta-externalfetcherUser-requested fetch
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
AmazonbotModel training
Robots: blocked by amazonbot disallow: / · line 34
Probe: not tested for this control
Controls: robots meta: index,follow
Amzn-SearchBotAI search
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
Amzn-UserUser-requested fetch
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
CCBotModel training
Robots: blocked by ccbot disallow: / · line 43
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.
