Speed Insights
Grade A
92% performance
https://findrightplugin.com
LCP
304ms
Largest paint
TBT
262ms
Blocking time
CLS
0.07
Layout shift
72
out of 100
91
out of 100
137/150 rule points
75
out of 100
54/72 rule points
60
out of 100
48/80 rule points
85
out of 100
94/110 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 Claude-SearchBot, Claude-User, PerplexityBot, and 1 more. Claude-SearchBot: Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: index, follow. Claude-User: Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: index, follow. PerplexityBot: Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: index, follow. MistralAI-User: Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: index, follow. 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 82%: discovery 34/45, index and snippet eligibility 25/25, synthetic reachability 13/20, sitemap freshness 10/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
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 3 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: color-contrast (2), landmark-one-main (1), region (14).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Data sourced from vendor pricing pages, verified July 2026. Install counts and ratings verified August 2026. Not affiliated with WordPress.org or Automattic.
Elements must meet minimum color contrast ratio thresholds
Document should have one main landmark
Fix all of the following: Document does not have a main landmark
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
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 100/100, answer-ready text 95/100, semantic structured data 65/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 65/100: completeness 100/100, graph connectivity 0/100, primary types FAQPage, WebApplication, currently useful search-feature types WebApplication, 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 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 Claude-SearchBot, Claude-User, PerplexityBot, and 1 more. Claude-SearchBot: Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: index, follow. Claude-User: Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: index, follow. PerplexityBot: Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: index, follow. MistralAI-User: Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: index, follow. 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 82%: discovery 34/45, index and snippet eligibility 25/25, synthetic reachability 13/20, sitemap freshness 10/10. robots.txt did not block the scored AI search or user-fetch agents for this page path. Failed: earned 11 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 100/100, answer-ready text 95/100, semantic structured data 65/100. Detected role: home (high confidence). Failed: earned 36 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
Relevant schema coverage
Why this needs attention
The page is missing a primary JSON-LD entity that matches its actual role, or its named entity is not supported by visible content.
Structured data gives search and answer engines explicit facts about your product.
Recommended correction
Evidence
Detected 2 JSON-LD block(s). Primary types: FAQPage, WebApplication. No primary type matches the page role. The named entity is supported by visible page content. Failed: earned 6 of 10 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 12: 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 65/100: completeness 100/100, graph connectivity 0/100, primary types FAQPage, WebApplication, currently useful search-feature types WebApplication, and limited-eligibility types FAQPage. Nested types do not count as separate schema coverage. Failed: earned 6 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
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
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 100 interactive control(s), including 0 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
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
4 of 182 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 2.3. Mobile 390px viewport: 2 of 93 failed; worst ratio 2.3:1. 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
Data sourced from vendor pricing pages, verified July 2026. Install counts and r
About · Articles · Reviews · Comparisons · Methodology · Jira Plugin Finder · Co
Data sourced from vendor pricing pages, verified July 2026. Install counts and r
· · · · · · · ·
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); 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: color-contrast (2), landmark-one-main (1), region (14). Failed: earned 14 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
Data sourced from vendor pricing pages, verified July 2026. Install counts and ratings verified August 2026. Not affiliated with WordPress.org or Automattic.
Elements must meet minimum color contrast ratio thresholds
Document should have one main landmark
Fix all of the following: Document does not have a main landmark
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
Fix Prompt
Rendered composition and spacing
Why this needs attention
Rendered geometry found cramped text, overly long lines, undersized body copy, or too many competing actions in the first viewport.
Consistent spacing helps the page feel deliberate and easier to scan.
Recommended correction
Evidence
Desktop 1366px: 14 unique above-fold action(s), 19 body sample(s) below 14px, 0 cramped line-height sample(s), and 0 overlong line sample(s). Mobile 390px: 9 unique above-fold action(s), 19 body sample(s) below 14px, 0 cramped line-height sample(s), and 0 overlong line sample(s). Repeated CTA labels are deduplicated and do not earn extra credit. More than three distinct actions compete in a captured first viewport. Failed: earned 2 of 7 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 25: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Visual hierarchy
Why this needs attention
Rendered typography, geometry, and contrast show that the main heading is not distinct or legible enough, or that the hierarchy needs manual review.
Hierarchy tells visitors what to read first and what action to take next.
Recommended correction
Evidence
The rendered H1 is 36px/400 weight versus a 13.5px/400 median body style (2.67× size). Captured 6 supporting heading(s) and 21 action(s). The main heading has a clear rendered emphasis over body copy. 4 of 182 rendered text samples missed contrast targets, so hierarchy is not considered fully legible. Failed: earned 6 of 9 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 12: fix during launch polish.
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: 480ms. Load complete: 1174ms. First contentful paint: 304ms. Largest contentful paint: 304ms. Total blocking time: 262ms. Cumulative layout shift: 0.067. Resources: 31. Scripts: 4. Images: 18. Third-party origins: 26. Transfer: 1710KB. Potential render-blocking resources: 3. Metrics outside the good range: Total blocking time 262ms (good at or below 200ms); Third-party origins 26 origins (good at or below 8 origins). Failed: earned 6 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.
Total blocking time
62ms over the rendered audit threshold.
Third-party origins
18 origins over the rendered audit threshold.
tabler-icons.min.css
css2
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 with lastmod 2026-08-21.
Structured data
Semantic schema score 65/100. Detected 2 JSON-LD block(s), 0 parse error(s), 8 graph node(s), and primary types FAQPage, WebApplication. Completeness: 100/100. Graph connectivity: 0/100. No primary schema type matched 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 100/100 for “Find the right WordPress plugin in 60 seconds”. Title/H1 token overlap is 100%; description match detected; identity schema detected.
Answer-ready visible text
Answerability scored 95/100 from 411 main-content words, 6 concise answer block(s), 3 question heading(s), 8 definition(s), 2 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 89 visible text element(s).
Synthetic search-agent reachability
6 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-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
OpenAIOpenAI model trainingGPTBotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by gptbot disallow: / · line 55
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow
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: index, follow
AnthropicClaude model trainingClaudeBotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by claudebot disallow: / · line 46
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow
AnthropicClaude searchClaude-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 31
Synthetic probe: blocked · HTTP 403
Controls: robots meta: index, follow
AnthropicClaude user fetchesClaude-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 31
Synthetic probe: blocked · HTTP 403
Controls: robots meta: index, follow
GoogleGoogle Search and AI featuresGooglebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
GoogleGemini data use and groundingGoogle-ExtendedOPTED OUT · Toggle crawler details
Data-use policy control
Robots: blocked by google-extended disallow: / · line 52
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow
MicrosoftBing and CopilotBingbotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
PerplexityPerplexity searchPerplexityBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 31
Synthetic probe: blocked · HTTP 403
Controls: robots meta: index, follow
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: index, follow
AppleSiri, Spotlight, and Safari searchApplebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
AppleApple foundation-model trainingApplebot-ExtendedOPTED OUT · Toggle crawler details
Data-use policy control
Robots: blocked by applebot-extended disallow: / · line 37
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow
Mistral AIMistral searchMistralAI-IndexPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
Mistral AIMistral user fetchesMistralAI-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 31
Synthetic probe: blocked · HTTP 403
Controls: robots meta: index, follow
MetaMeta AI model and product datameta-externalagentOPTED OUT · Toggle crawler details
Model training
Robots: blocked by meta-externalagent disallow: / · line 58
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow
MetaMeta AI user fetchesmeta-externalfetcherPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
AmazonAmazon model trainingAmazonbotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by amazonbot disallow: / · line 34
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow
AmazonAlexa and Rufus searchAmzn-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
AmazonAlexa user fetchesAmzn-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
Common CrawlOpen web datasetsCCBotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by ccbot disallow: / · line 43
Synthetic probe: not applicable to this policy 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. 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.
