Speed Insights
Grade A
100% performance
https://amazingplugins.com
LCP
328ms
Largest paint
TBT
0ms
Blocking time
CLS
0.000
Layout shift
56
out of 100
87
out of 100
131/150 rule points
81
out of 100
59/72 rule points
82
out of 100
66/80 rule points
89
out of 100
98/110 rule points
Category point breakdown
- Search discovery is materially blocked.
- 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, Claude-User, and 9 more. OAI-SearchBot: Allowed by oai-searchbot allow: / on line 7. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. Claude-SearchBot: Allowed by claude-searchbot allow: / on line 14. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. Claude-User: Allowed by claude-user allow: / on line 18. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. Googlebot: Allowed by googlebot allow: / on line 28. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. Bingbot: Allowed by bingbot allow: / on line 31. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. PerplexityBot: Allowed by perplexitybot allow: / on line 21. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. Applebot: Allowed by applebot allow: / on line 34. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. MistralAI-Index: Allowed by * allow: / on line 69. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. MistralAI-User: Allowed by * allow: / on line 69. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. meta-externalfetcher: Allowed by * allow: / on line 69. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. Amzn-SearchBot: Allowed by * allow: / on line 69. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. Amzn-User: Allowed by * allow: / on line 69. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. AEO crawler readiness is 30%: discovery 0/45, index and snippet eligibility 25/25, synthetic reachability 0/20, 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 2 of 5 common public security controls. Present: x-content-type-options, referrer-policy. Missing: strict-transport-security, content-security-policy, frame protection (x-frame-options or content-security-policy frame-ancestors). Needs strengthening: none.
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Add meaningful 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 0 image(s) with no alt attribute and 1 image(s) with empty alt text that appear informative, out of 49. 1 empty-alt image(s) looked decorative and were not counted as failures.
Priority
Priority 11: fix during launch polish.
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 90/100, answer-ready text 70/100, semantic structured data 80/100. Detected role: home (high confidence).
Priority
Priority 6: fix during launch polish.
Fix Prompt
Improve 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 80/100: completeness 75/100, graph connectivity 0/100, primary types FAQPage, Organization, currently useful search-feature types Organization, and limited-eligibility types FAQPage. Nested types do not count as separate schema coverage.
Priority
Priority 10: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 8 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, 6 medium, 0 low. Coverage: 2 review and 1 not applicable.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 low. Coverage: 0 review and 0 not applicable.
SEO / AEO
Severity mix: 1 critical, 8 high, 3 medium, 1 low. Coverage: 0 review and 0 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 low. Coverage: 2 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: 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. Non-robots access or indexing restrictions affect OAI-SearchBot, Claude-SearchBot, Claude-User, and 9 more. OAI-SearchBot: Allowed by oai-searchbot allow: / on line 7. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. Claude-SearchBot: Allowed by claude-searchbot allow: / on line 14. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. Claude-User: Allowed by claude-user allow: / on line 18. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. Googlebot: Allowed by googlebot allow: / on line 28. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. Bingbot: Allowed by bingbot allow: / on line 31. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. PerplexityBot: Allowed by perplexitybot allow: / on line 21. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. Applebot: Allowed by applebot allow: / on line 34. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. MistralAI-Index: Allowed by * allow: / on line 69. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. MistralAI-User: Allowed by * allow: / on line 69. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. meta-externalfetcher: Allowed by * allow: / on line 69. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. Amzn-SearchBot: Allowed by * allow: / on line 69. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. Amzn-User: Allowed by * allow: / on line 69. Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge. AEO crawler readiness is 30%: discovery 0/45, index and snippet eligibility 25/25, synthetic reachability 0/20, sitemap freshness 5/10. robots.txt did not block the scored AI search or user-fetch agents for this page path. Failed: earned 4 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 90/100, answer-ready text 70/100, semantic structured data 80/100. Detected role: home (high confidence). Failed: earned 32 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
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 80/100: completeness 75/100, graph connectivity 0/100, primary types FAQPage, Organization, currently useful search-feature types Organization, and limited-eligibility types FAQPage. 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 2 of 5 common public security controls. Present: x-content-type-options, referrer-policy. Missing: strict-transport-security, content-security-policy, frame protection (x-frame-options or content-security-policy frame-ancestors). Needs strengthening: none. Failed: earned 5 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 0 image(s) with no alt attribute and 1 image(s) with empty alt text that appear informative, out of 49. 1 empty-alt image(s) looked decorative and were not counted as failures. 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
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
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: 313ms. Load complete: 0ms. First contentful paint: 328ms. Largest contentful paint: 328ms. Total blocking time: 0ms. Cumulative layout shift: 0. Resources: 32. Scripts: 3. Images: 23. Third-party origins: 23. Transfer: 1493KB. Potential render-blocking resources: 0. Metrics outside the good range: Third-party origins 23 origins (good at or below 8 origins). 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.
Third-party origins
15 origins over the rendered audit threshold.
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 80/100. Detected 2 JSON-LD block(s), 0 parse error(s), 7 graph node(s), and primary types FAQPage, Organization. Completeness: 75/100. Graph connectivity: 0/100. A primary schema type matches the detected page role. The schema entity is supported by visible page content. Limited search eligibility: FAQPage.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 90/100 for “A house of plugins for WooCommerce.”. Title/H1 token overlap is 67%; description match detected; identity schema detected.
Answer-ready visible text
Answerability scored 70/100 from 384 main-content words, 4 concise answer block(s), 0 question heading(s), 4 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 98 visible text element(s).
Synthetic search-agent reachability
0 of 8 completed search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
https://amazingplugins.com/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.
OpenAIChatGPT searchOAI-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed by oai-searchbot allow: / · line 7
Synthetic probe: challenged · HTTP 429 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge.
OpenAIOpenAI model trainingGPTBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by gptbot allow: / · line 41
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 trainingClaudeBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by claudebot allow: / · line 45
Synthetic probe: not applicable to this policy control
AnthropicClaude searchClaude-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed by claude-searchbot allow: / · line 14
Synthetic probe: challenged · HTTP 429 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge.
AnthropicClaude user fetchesClaude-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed by claude-user allow: / · line 18
Synthetic probe: challenged · HTTP 429 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge.
GoogleGoogle Search and AI featuresGooglebotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: allowed by googlebot allow: / · line 28
Synthetic probe: challenged · HTTP 429 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge.
GoogleGemini data use and groundingGoogle-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed by google-extended allow: / · line 49
Synthetic probe: not applicable to this policy control
MicrosoftBing and CopilotBingbotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: allowed by bingbot allow: / · line 31
Synthetic probe: challenged · HTTP 429 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge.
PerplexityPerplexity searchPerplexityBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed by perplexitybot allow: / · line 21
Synthetic probe: challenged · HTTP 429 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge.
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: allowed by applebot allow: / · line 34
Synthetic probe: challenged · HTTP 429 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge.
AppleApple foundation-model trainingApplebot-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed by applebot-extended allow: / · line 53
Synthetic probe: not applicable to this policy control
Mistral AIMistral searchMistralAI-IndexFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 69
Synthetic probe: challenged · HTTP 429 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge.
Mistral AIMistral user fetchesMistralAI-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 69
Synthetic probe: challenged · HTTP 429 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge.
MetaMeta AI model and product datameta-externalagentPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by meta-externalagent allow: / · line 61
Synthetic probe: not applicable to this policy control
MetaMeta AI user fetchesmeta-externalfetcherFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 69
Synthetic probe: challenged · HTTP 429 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge.
AmazonAmazon model trainingAmazonbotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by amazonbot allow: / · line 37
Synthetic probe: not applicable to this policy control
AmazonAlexa and Rufus searchAmzn-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 69
Synthetic probe: challenged · HTTP 429 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge.
AmazonAlexa user fetchesAmzn-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 69
Synthetic probe: challenged · HTTP 429 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 429 bot or security challenge.
Common CrawlOpen web datasetsCCBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by ccbot allow: / · line 57
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.
To refresh your Pro site score and fixes, open your Pro dashboard and run a site audit.
