Speed Insights
Grade D
65% performance
https://www.pornhub.com
From https://pornhub.com
LCP
2.9s
Largest paint
TBT
935ms
Blocking time
CLS
0.000
Layout shift
53
out of 100
25
out of 100
25/102 rule points
85
out of 100
61/72 rule points
33
out of 100
31/94 rule points
70
out of 100
77/110 rule points
Category point breakdown
Biggest score-losing checks
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, Googlebot, and 5 more from AI search or discovery for this page path. AEO crawler readiness is 10%: discovery 0/45, index and snippet eligibility 10/25, synthetic reachability 0/20, sitemap freshness 0/10.
Priority
Priority 2: 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 4 violation rule(s), including 3 serious or critical rule(s). Top rules: button-name (1), frame-title (31), link-in-text-block (2), region (119).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Buttons must have discernible text
Fix any of the following: Element does not have inner 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 Element does not have an implicit (wrapped) <label> Element does not have an explicit <label> Element's default semantics were not overridden with role="none" or role="presentation"
Frames must have an accessible name
Fix any of the following: Element has no title attribute 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's default semantics were not overridden with role="none" or role="presentation"
Frames must have an accessible name
Fix any of the following: Element has no title attribute 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's default semantics were not overridden with role="none" or role="presentation"
Frames must have an accessible name
Fix any of the following: Element has no title attribute 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's default semantics were not overridden with role="none" or role="presentation"
Fix Prompt
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 2 of 5 common public security controls. Present: strict-transport-security, frame protection (x-frame-options). Missing: content-security-policy, x-content-type-options, referrer-policy.
Priority
Priority 5: fix before sharing the page publicly.
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
No meta description was detected.
Priority
Priority 3: fix before sharing the page publicly.
Fix Prompt
Remove noindex signals
Why this needs attention
The page appears to tell crawlers not to index it.
A noindex directive can prevent the launch page from appearing in search results.
Recommended correction
Evidence
A noindex directive was detected.
Priority
Priority 2: fix before sharing the page publicly.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 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.
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 2 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.
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, Googlebot, and 5 more from AI search or discovery for this page path. AEO crawler readiness is 10%: discovery 0/45, index and snippet eligibility 10/25, synthetic reachability 0/20, sitemap freshness 0/10. Failed: earned 1 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
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 7 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
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
No meta description was detected. 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 0 H1 heading(s) and 12 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
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 presence
Why this needs attention
No JSON-LD schema was detected on the page.
Structured data gives search and answer engines explicit facts about your product.
Recommended correction
Evidence
Detected 0 JSON-LD schema block(s). Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 12: fix during launch polish.
Fix Prompt
Open Graph basics
Why this needs attention
The page is missing several social preview fields.
Launch links on X, LinkedIn, Slack, and communities look less trustworthy without a strong preview.
Recommended correction
Evidence
Detected 0 of 4 Open Graph basics. Failed: earned 0 of 5 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 18: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Indexability signals
Why this needs attention
The page appears to tell crawlers not to index it.
A noindex directive can prevent the launch page from appearing in search results.
Recommended correction
Evidence
A noindex directive was detected. Failed: earned 0 of 9 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 2: 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 2 of 5 common public security controls. Present: strict-transport-security, frame protection (x-frame-options). Missing: content-security-policy, x-content-type-options, referrer-policy. Failed: earned 7 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
Image alt text
Why this needs attention
One or more images are missing alt text.
People using screen readers may miss product context, trust signals, or calls to action.
Recommended correction
Evidence
Detected 4 image(s) missing alt text out of 33. Failed: earned 0 of 14 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 11: 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: 3, 3, 5, 5, 5, 5, 5, 5, 5, 5, 5, 5. 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
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 main landmark(s) and 1 total 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
Semantic buttons and links
Why this needs attention
Interactive controls are not consistently represented as semantic buttons or links.
Non-semantic controls can be hard to use with keyboards and screen readers.
Recommended correction
Evidence
Detected 143 interactive control(s), including 1 custom ARIA control(s), and 1 clickable element(s) without native or declared control semantics. Custom controls require keyboard-behavior review. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 17: lower-risk cleanup after urgent launch blockers.
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 4 violation rule(s), including 3 serious or critical rule(s). Top rules: button-name (1), frame-title (31), link-in-text-block (2), region (119). 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
Buttons must have discernible text
Fix any of the following: Element does not have inner 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 Element does not have an implicit (wrapped) <label> Element does not have an explicit <label> Element's default semantics were not overridden with role="none" or role="presentation"
Frames must have an accessible name
Fix any of the following: Element has no title attribute 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's default semantics were not overridden with role="none" or role="presentation"
Frames must have an accessible name
Fix any of the following: Element has no title attribute 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's default semantics were not overridden with role="none" or role="presentation"
Frames must have an accessible name
Fix any of the following: Element has no title attribute 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's default semantics were not overridden with role="none" or role="presentation"
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 0 H1 heading(s) and 0 meta-description characters. Failed: earned 0 of 13 points.
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 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: 4184ms. Load complete: 4448ms. First contentful paint: 2888ms. Resources: 72. Scripts: 22. Images: 22. Third-party origins: 7. Transfer: not available. Potential render-blocking resources: 44. Exceeded thresholds: DOMContentLoaded 4184ms (threshold 2500ms); First contentful paint 2888ms (threshold 2200ms); Script requests 22 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.
DOMContentLoaded
1684ms over the rendered audit threshold.
First contentful paint
688ms over the rendered audit threshold.
Script requests
2 scripts over the rendered audit threshold.
vue.min.js
Fix Prompt
Page-level AEO readiness
Shared eligibility and content signals that affect every search and answer agent.
Index and citation eligibility
A general noindex directive prevents search indexing and citation eligibility.
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
Sitemap coverage could not be verified.
Structured data
Semantic schema score 0/100. Detected 0 JSON-LD block(s), 0 parse error(s), 0 graph node(s), and types none. No primary schema type matched the detected page role.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 20/100 for “Pornhub”. Title/H1 token overlap is 0%; description match not detected; identity schema not detected.
Answer-ready visible text
Answerability scored 40/100 from 280 main-content words, 0 concise answer block(s), 0 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 160 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-SearchBotAI search
Robots: unknown
Probe: not tested for this control
Controls: robots meta: noindex, nofollow
OpenAIOpenAI model trainingGPTBotModel training
Robots: unknown
Probe: not tested for this control
Controls: robots meta: noindex, nofollow
OpenAIChatGPT user fetchesChatGPT-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: noindex, nofollow
AnthropicClaude model trainingClaudeBotModel training
Robots: unknown
Probe: not tested for this control
Controls: robots meta: noindex, nofollow
AnthropicClaude searchClaude-SearchBotAI search
Robots: unknown
Probe: not tested for this control
Controls: robots meta: noindex, nofollow
AnthropicClaude user fetchesClaude-UserUser-requested fetch
Robots: unknown
Probe: not tested for this control
Controls: robots meta: noindex, nofollow
GoogleGoogle Search and AI featuresGooglebotSearch and discovery
Robots: unknown
Probe: not tested for this control
Controls: robots meta: noindex, nofollow
GoogleGemini data use and groundingGoogle-ExtendedData-use policy control
Robots: unknown
Probe: not tested for this control
Controls: robots meta: noindex, nofollow
MicrosoftBing and CopilotBingbotSearch and discovery
Robots: unknown
Probe: not tested for this control
Controls: robots meta: noindex, nofollow
PerplexityPerplexity searchPerplexityBotAI search
Robots: unknown
Probe: not tested for this control
Controls: robots meta: noindex, nofollow
PerplexityPerplexity user fetchesPerplexity-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: noindex, nofollow
AppleSiri, Spotlight, and Safari searchApplebotSearch and discovery
Robots: unknown
Probe: not tested for this control
Controls: robots meta: noindex, nofollow
AppleApple foundation-model trainingApplebot-ExtendedData-use policy control
Robots: unknown
Probe: not tested for this control
Controls: robots meta: noindex, nofollow
Mistral AIMistral searchMistralAI-IndexAI search
Robots: unknown
Probe: not tested for this control
Controls: robots meta: noindex, nofollow
Mistral AIMistral user fetchesMistralAI-UserUser-requested fetch
Robots: unknown
Probe: not tested for this control
Controls: robots meta: noindex, nofollow
MetaMeta AI model and product datameta-externalagentModel training
Robots: unknown
Probe: not tested for this control
Controls: robots meta: noindex, nofollow
MetaMeta AI user fetchesmeta-externalfetcherUser-requested fetch
Robots: unknown
Probe: not tested for this control
Controls: robots meta: noindex, nofollow
AmazonAmazon model trainingAmazonbotModel training
Robots: unknown
Probe: not tested for this control
Controls: robots meta: noindex, nofollow
AmazonAlexa and Rufus searchAmzn-SearchBotAI search
Robots: unknown
Probe: not tested for this control
Controls: robots meta: noindex, nofollow
AmazonAlexa user fetchesAmzn-UserUser-requested fetch
Robots: unknown
Probe: not tested for this control
Controls: robots meta: noindex, nofollow
Common CrawlOpen web datasetsCCBotModel training
Robots: unknown
Probe: not tested for this control
Controls: robots meta: noindex, nofollow
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.
