Speed Insights
Grade A
96% performance
https://app.laterpress.com/auth/login
From https://app.laterpress.com/
LCP
372ms
Largest paint
TBT
186ms
Blocking time
CLS
0.003
Layout shift
39
out of 100
58
out of 100
72/125 rule points
72
out of 100
55/76 rule points
53
out of 100
42/80 rule points
82
out of 100
56/68 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
Improve AI search and crawler readiness
Why this needs attention
One or more AI discovery, user-fetch, indexability, snippet, synthetic reachability, or sitemap signals need attention.
AI search systems need crawlable, reachable, indexable, and quotable public content. Training and data-use choices remain neutral publisher preferences.
Recommended correction
Evidence
FreeScan.app reached the public page with HTTP 200. robots.txt blocks OAI-SearchBot, Claude-SearchBot, Claude-User, and 9 more for this page path. GPTBot, ClaudeBot, Google-Extended, and 4 more are explicit training or data-use opt-outs and do not reduce the AEO score. AEO crawler readiness is 20%: discovery 0/45, index and snippet eligibility 20/25, synthetic reachability 0/20, sitemap freshness 0/10.
Priority
Priority 2: fix before sharing the page publicly.
Fix Prompt
Add common public security headers
Why this needs attention
Several browser protection headers are missing or present only as weak, narrow policies.
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. Needs strengthening: none.
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 eligible user-facing form control(s).
Priority
Priority 7: fix during launch polish.
Fix Prompt
Shorten the meta description
Why this needs attention
The meta description is 203 characters, so it is longer than the recommended maximum.
Long descriptions are likely to be truncated or rewritten, which can hide the most useful part of the message.
Recommended correction
Evidence
Meta description is 203 characters, above the 170-character maximum.
Priority
Priority 3: fix before sharing the page publicly.
Fix Prompt
Publish a valid sitemap
Why this needs attention
The sitemap file was not reachable or did not look like valid sitemap XML.
A sitemap helps search engines discover the landing page and related public pages sooner.
Recommended correction
Evidence
HTTP 404 returned for sitemap_xml.
Priority
Priority 7: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 8 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 0 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 low. Coverage: 0 review and 2 not applicable.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 low. Coverage: 2 review and 2 not applicable.
SEO / AEO
Severity mix: 1 critical, 8 high, 3 medium, 1 low. Coverage: 0 review and 1 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 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 0 not applicable.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 low. Coverage: 2 review and 2 not applicable.
Failed checks
These checks need attention.
Crawler access
Why this needs attention
One or more AI discovery, user-fetch, indexability, snippet, synthetic reachability, or sitemap signals need attention.
AI search systems need crawlable, reachable, indexable, and quotable public content. Training and data-use choices remain neutral publisher preferences.
Recommended correction
Evidence
FreeScan.app reached the public page with HTTP 200. robots.txt blocks OAI-SearchBot, Claude-SearchBot, Claude-User, and 9 more for this page path. GPTBot, ClaudeBot, Google-Extended, and 4 more are explicit training or data-use opt-outs and do not reduce the AEO score. AEO crawler readiness is 20%: discovery 0/45, index and snippet eligibility 20/25, synthetic reachability 0/20, sitemap freshness 0/10. Failed: earned 3 of 14 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 2: fix before sharing the page publicly.
Fix Prompt
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 55/100. Detected role: utility (high confidence). Failed: earned 8 of 15 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 6: fix during launch polish.
Fix Prompt
Meta description
Why this needs attention
The meta description is 203 characters, so it is longer than the recommended maximum.
Long descriptions are likely to be truncated or rewritten, which can hide the most useful part of the message.
Recommended correction
Evidence
Meta description is 203 characters, above the 170-character maximum. 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
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 visible H1 heading(s) and 1 visible heading(s) in the rendered page. Heading-level order is assessed separately under Accessibility. Failed: earned 6 of 8 points from partial coverage.
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
Sitemap validity
Why this needs attention
The sitemap file was not reachable or did not look like valid sitemap XML.
A sitemap helps search engines discover the landing page and related public pages sooner.
Recommended correction
Evidence
HTTP 404 returned for sitemap_xml. Failed: earned 0 of 12 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 7: 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
2 of 2 JSON-LD block(s) parsed. Semantic quality is 85/100: completeness 100/100, graph connectivity 0/100, primary types Organization, WebSite, currently useful search-feature types Organization, WebSite. 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
Common security headers
Why this needs attention
Several browser protection headers are missing or present only as weak, narrow policies.
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. Needs strengthening: none. 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
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 4 cookie(s) without storing names or values. Secure: 3/4. HttpOnly: 2/4. SameSite: 3/4. SameSite=None without Secure: 0. Failed: earned 1 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
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 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
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 visible main landmark(s) and 0 visible landmark element(s) or roles. A page should expose one main landmark. 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
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
1 of 11 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 2.06. Mobile 390px viewport: 0 of 5 failed. 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
Log in
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); 3 non-contrast rule(s) are scored here, including 0 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 0 result(s) require review. Top rules: landmark-one-main (1), meta-viewport (1), region (4). Failed: earned 12 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.
Affected elements
Document should have one main landmark
Fix all of the following: Document does not have a main landmark
Zooming and scaling must not be disabled
Fix any of the following: maximum-scale on <meta> tag disables zooming on mobile devices
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
Fix Prompt
Text density
Why this needs attention
The page may not provide enough useful context for its detected role, or its rendered structure needs review.
Too little copy can leave visitors confused; too much copy can bury the value proposition.
Recommended correction
Evidence
Detected about 12 visible word(s) in the rendered page. The contextual range is 30-1000 words for the detected utility page role. Failed: earned 4 of 10 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 21: 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: 799ms. Load complete: 806ms. First contentful paint: 372ms. Largest contentful paint: 372ms. Total blocking time: 186ms. Cumulative layout shift: 0.003. Resources: 44. Scripts: 35. Images: 0. Third-party origins: 3. Transfer: 967KB. Potential render-blocking resources: 4. Metrics outside the good range: Script requests 35 scripts (good at or below 20 scripts). Failed: earned 8 of 10 points from partial coverage.
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
15 scripts over the rendered audit threshold.
css2
0n6pc4m_.0~y-.css
03.tegem_pz34.css
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
Sitemap coverage could not be verified.
Structured data
Semantic schema score 85/100. Detected 2 JSON-LD block(s), 0 parse error(s), 2 graph node(s), and primary types Organization, WebSite. Completeness: 100/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 55/100 for “Log into author account”. Title/H1 token overlap is 0%; description match not detected; identity schema detected.
Answer-ready visible text
Answerability is contextual for the detected utility page role and does not affect readiness.
Authorship and accountability
Authorship is not a universal requirement for the detected utility page role.
Published or updated date
Freshness metadata is contextual for the detected utility page role.
Supporting-source links
Supporting sources are contextual for the detected utility page role and do not affect readiness.
Rendered content availability
Rendered audit completed with 6 visible text element(s).
Synthetic search-agent reachability
0 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-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
OpenAIOpenAI model trainingGPTBotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by * disallow: / · line 2
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 trainingClaudeBotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by * disallow: / · line 2
Synthetic probe: not applicable to this policy control
AnthropicClaude searchClaude-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
AnthropicClaude user fetchesClaude-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
GoogleGoogle Search and AI featuresGooglebotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
GoogleGemini data use and groundingGoogle-ExtendedOPTED OUT · Toggle crawler details
Data-use policy control
Robots: blocked by * disallow: / · line 2
Synthetic probe: not applicable to this policy control
MicrosoftBing and CopilotBingbotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
PerplexityPerplexity searchPerplexityBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
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 searchApplebotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
AppleApple foundation-model trainingApplebot-ExtendedOPTED OUT · Toggle crawler details
Data-use policy control
Robots: blocked by * disallow: / · line 2
Synthetic probe: not applicable to this policy control
Mistral AIMistral searchMistralAI-IndexFAIL · BLOCKED · Toggle crawler details
AI search
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
Mistral AIMistral user fetchesMistralAI-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
MetaMeta AI model and product datameta-externalagentOPTED OUT · Toggle crawler details
Model training
Robots: blocked by * disallow: / · line 2
Synthetic probe: not applicable to this policy control
MetaMeta AI user fetchesmeta-externalfetcherFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
AmazonAmazon model trainingAmazonbotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by * disallow: / · line 2
Synthetic probe: not applicable to this policy control
AmazonAlexa and Rufus searchAmzn-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
AmazonAlexa user fetchesAmzn-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
Common CrawlOpen web datasetsCCBotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by * disallow: / · line 2
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.
