Speed Insights
Grade A
98% performance
https://pickuplineshub.com
LCP
1.3s
Largest paint
TBT
0ms
Blocking time
CLS
0.000
Layout shift
65
out of 100
78
out of 100
118/150 rule points
75
out of 100
54/72 rule points
86
out of 100
69/80 rule points
43
out of 100
47/92 rule points
Category point breakdown
- Material high-impact failures span 3 categories.
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. Non-robots access or indexing restrictions affect OAI-SearchBot, Claude-SearchBot, PerplexityBot, and 3 more. OAI-SearchBot: No matching robots.txt rule blocks OAI-SearchBot from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index. Claude-SearchBot: No matching robots.txt rule blocks Claude-SearchBot from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index. PerplexityBot: No matching robots.txt rule blocks PerplexityBot from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index. Applebot: No matching robots.txt rule blocks Applebot from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index. MistralAI-User: No matching robots.txt rule blocks MistralAI-User from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index. meta-externalfetcher: No matching robots.txt rule blocks meta-externalfetcher from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index. Search-agent policy or reachability was not verified for 5 crawler user agent(s); untested components are not evidence of blocked discovery. Index and snippet eligibility 25/25, sitemap freshness 5/10. robots.txt did not block the scored AI search or user-fetch agents for this page path.
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
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
Rendered CTA evidence: 0 desktop above-fold action(s) across 0 unique purpose(s); 0 mobile above-fold action(s) across 0 unique purpose(s). 0 repeated occurrence(s) were deduplicated and earned no extra credit.
Priority
Priority 4: fix before sharing the page publicly.
Fix Prompt
Strengthen 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 50/100, answer-ready text 30/100, semantic structured data 96/100. Detected role: home (high confidence).
Priority
Priority 6: fix during launch polish.
Fix Prompt
Review introductory clarity signals
Why this needs attention
One or more heading, introductory-copy, or next-action signals fell outside this heuristic's expected range; this does not by itself prove the page is vague.
The introduction should help visitors understand the purpose of this particular page.
Recommended correction
Evidence
Detected 0 visible H1 heading(s), 0 H1 characters, 0 introductory supporting-copy characters after excluding bylines and short labels, and 6 actionable CTA(s). Rendered evidence was used where available. The H1 text is treated as a subject label, so an appropriate short place, product, or page name does not lose points. Detected role: home (high confidence).
Priority
Priority 6: 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 1 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 low. Coverage: 1 review and 1 not applicable.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 low. Coverage: 1 review and 0 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: 1 review and 1 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, 7 medium, 1 low. Coverage: 1 review and 0 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. Non-robots access or indexing restrictions affect OAI-SearchBot, Claude-SearchBot, PerplexityBot, and 3 more. OAI-SearchBot: No matching robots.txt rule blocks OAI-SearchBot from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index. Claude-SearchBot: No matching robots.txt rule blocks Claude-SearchBot from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index. PerplexityBot: No matching robots.txt rule blocks PerplexityBot from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index. Applebot: No matching robots.txt rule blocks Applebot from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index. MistralAI-User: No matching robots.txt rule blocks MistralAI-User from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index. meta-externalfetcher: No matching robots.txt rule blocks meta-externalfetcher from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index. Search-agent policy or reachability was not verified for 5 crawler user agent(s); untested components are not evidence of blocked discovery. Index and snippet eligibility 25/25, sitemap freshness 5/10. robots.txt did not block the scored AI search or user-fetch agents for this page path. Failed: earned 8 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 50/100, answer-ready text 30/100, semantic structured data 96/100. Detected role: home (high confidence). Failed: earned 22 of 40 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 6: fix during launch polish.
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 0 visible H1 heading(s) and 25 visible heading(s) in the rendered page. Heading-level order is assessed separately under Accessibility. 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 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
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 82 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 1.71. Mobile 390px viewport: 0 of 34 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
Pick up lines Hub CategoriesExpand Fruit Food Movie Sports TV Series Superhero P
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); 2 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: page-has-heading-one (1), image-redundant-alt (1). Failed: earned 15 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
Page should contain a level-one heading
Fix all of the following: Page must have a level-one heading
Alternative text of images should not be repeated as text
Fix all of the following: Element contains <img> element with alt text that duplicates existing text
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
Rendered CTA evidence: 0 desktop above-fold action(s) across 0 unique purpose(s); 0 mobile above-fold action(s) across 0 unique purpose(s). 0 repeated occurrence(s) were deduplicated and earned no extra credit. 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
One or more heading, introductory-copy, or next-action signals fell outside this heuristic's expected range; this does not by itself prove the page is vague.
The introduction should help visitors understand the purpose of this particular page.
Recommended correction
Evidence
Detected 0 visible H1 heading(s), 0 H1 characters, 0 introductory supporting-copy characters after excluding bylines and short labels, and 6 actionable CTA(s). Rendered evidence was used where available. The H1 text is treated as a subject label, so an appropriate short place, product, or page name does not lose points. Detected role: home (high confidence). Failed: earned 2 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
Credibility and proof
Why this needs attention
The page does not expose enough verifiable credibility for its detected role.
Trust signals reduce hesitation when strangers see the product for the first time.
Recommended correction
Evidence
Detected 0 commercial proof signal(s) and 0 source or methodology signal(s) for this home page. 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
Runtime console health
Why this needs attention
The rendered page produced console or uncaught JavaScript errors.
Runtime errors can break forms, CTAs, animations, tracking, or responsive behavior even when the static HTML looks fine.
Recommended correction
Evidence
Detected 0 site-authored console error(s) and 1 uncaught page error(s) during render. Samples: Cannot read properties of null (reading 'addEventListener') Failed: earned 0 of 7 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 15: fix during launch polish.
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 96/100. Detected 1 JSON-LD block(s), 0 parse error(s), 4 graph node(s), and primary types CollectionPage, Organization, WebSite. Completeness: 92/100. Graph connectivity: 85/100. A primary schema type matches the detected page role. The schema entity is supported by visible page content. Retired search feature: SearchAction; no coverage credit is awarded.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 50/100 for “Pick up lines Hub”. Title/H1 token overlap is 0%; description match detected; identity schema detected.
Answer-ready visible text
Answerability scored 30/100 from 243 main-content words, 0 concise answer block(s), 0 question heading(s), 0 definition(s), 1 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 38 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: allowed
Synthetic probe: challenged · HTTP 403 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
Controls: robots meta: follow, index
OpenAIOpenAI model trainingGPTBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: follow, index
OpenAIChatGPT user fetchesChatGPT-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: not applicable to user-requested fetches
Synthetic probe: not tested · access is unverified
Controls: robots meta: follow, index
AnthropicClaude model trainingClaudeBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: follow, index
AnthropicClaude searchClaude-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: challenged · HTTP 403 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
Controls: robots meta: follow, index
AnthropicClaude user fetchesClaude-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: follow, index
GoogleGoogle Search and AI featuresGooglebotUNKNOWN · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: unknown
Synthetic User-Agent probe timed out.
Controls: robots meta: follow, index
GoogleGemini data use and groundingGoogle-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: follow, index
MicrosoftBing and CopilotBingbotUNKNOWN · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: unknown
Synthetic User-Agent probe timed out.
Controls: robots meta: follow, index
PerplexityPerplexity searchPerplexityBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: challenged · HTTP 403 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
Controls: robots meta: follow, index
PerplexityPerplexity user fetchesPerplexity-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: not applicable to user-requested fetches
Synthetic probe: not tested · access is unverified
Controls: robots meta: follow, index
AppleSiri, Spotlight, and Safari searchApplebotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: challenged · HTTP 403 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
Controls: robots meta: follow, index
AppleApple foundation-model trainingApplebot-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: follow, index
Mistral AIMistral searchMistralAI-IndexUNKNOWN · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: unknown
Synthetic User-Agent probe timed out.
Controls: robots meta: follow, index
Mistral AIMistral user fetchesMistralAI-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: challenged · HTTP 403 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
Controls: robots meta: follow, index
MetaMeta AI model and product datameta-externalagentPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: follow, index
MetaMeta AI user fetchesmeta-externalfetcherFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: challenged · HTTP 403 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
Controls: robots meta: follow, index
AmazonAmazon model trainingAmazonbotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: follow, index
AmazonAlexa and Rufus searchAmzn-SearchBotUNKNOWN · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: unknown
Synthetic User-Agent probe timed out.
Controls: robots meta: follow, index
AmazonAlexa user fetchesAmzn-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: unknown
Synthetic User-Agent probe timed out.
Controls: robots meta: follow, index
Common CrawlOpen web datasetsCCBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: follow, index
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.
To refresh your Pro site score and fixes, open your Pro dashboard and run a site audit.
