Speed Insights
Grade B
88% performance
https://auraplusplus.com
LCP
1.4s
Largest paint
TBT
378ms
Blocking time
CLS
0.003
Layout shift
78
out of 100
75
out of 100
83/111 rule points
100
out of 100
76/76 rule points
55
out of 100
47/86 rule points
83
out of 100
91/110 rule points
Category point breakdown
Biggest score-losing checks
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 7 violation rule(s), including 2 serious or critical rule(s). Top rules: color-contrast (78), nested-interactive (23), heading-order (1), landmark-main-is-top-level (1), landmark-no-duplicate-main (1).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
<a title="Artificial Intelligence" class="bg-secondary hover:bg-secondary/80 inline-flex items-center gap-1 rounded-full px-2 py-0.5 text-xs transition-colors" href="/categories?ca
<a title="Marketing Tools" class="bg-secondary hover:bg-secondary/80 inline-flex items-center gap-1 rounded-full px-2 py-0.5 text-xs transition-colors" href="/categories?category=m
<a title="Platforms" class="bg-secondary hover:bg-secondary/80 inline-flex items-center gap-1 rounded-full px-2 py-0.5 text-xs transition-colors" href="/categories?category=platfor
Interactive controls must not be nested
Fix any of the following: Element has focusable descendants
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
Meta description is 183 characters.
Priority
Priority 3: fix before sharing the page publicly.
Fix Prompt
Write a clear 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.
Priority
Priority 8: fix during launch polish.
Fix Prompt
Fix 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, 3, 3, 1, 3, 2, 4, 4, 4, 3, 3, 3, 3, 3, 2, 3, 3, 3, 2, 3, 3, 3, 2, 3, 3, 3, 2, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 2.
Priority
Priority 13: fix during launch polish.
Fix Prompt
Use one clear H1 and ordered headings
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 H1 heading(s) and 43 total headings.
Priority
Priority 9: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
No failed checks in this category.
Accessibility
Severity mix: 0 critical, 3 high, 4 medium, 0 low.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low.
Accessibility
Severity mix: 0 critical, 3 high, 4 medium, 0 low.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
No failed checks in this category.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Failed checks
These checks need attention.
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
Meta description is 183 characters. 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 H1 heading(s) and 43 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
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, 3, 3, 1, 3, 2, 4, 4, 4, 3, 3, 3, 3, 3, 2, 3, 3, 3, 2, 3, 3, 3, 2, 3, 3, 3, 2, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 2. 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
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 42 semantic control(s) out of 65. 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 7 violation rule(s), including 2 serious or critical rule(s). Top rules: color-contrast (78), nested-interactive (23), heading-order (1), landmark-main-is-top-level (1), landmark-no-duplicate-main (1). 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
<a title="Artificial Intelligence" class="bg-secondary hover:bg-secondary/80 inline-flex items-center gap-1 rounded-full px-2 py-0.5 text-xs transition-colors" href="/categories?ca
<a title="Marketing Tools" class="bg-secondary hover:bg-secondary/80 inline-flex items-center gap-1 rounded-full px-2 py-0.5 text-xs transition-colors" href="/categories?category=m
<a title="Platforms" class="bg-secondary hover:bg-secondary/80 inline-flex items-center gap-1 rounded-full px-2 py-0.5 text-xs transition-colors" href="/categories?category=platfor
Interactive controls must not be nested
Fix any of the following: Element has focusable descendants
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: 1562ms. Load complete: 1617ms. First contentful paint: 512ms. Resources: 105. Scripts: 48. Images: 41. Third-party origins: 8. Transfer: not available. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 14: fix during launch polish.
Fix Prompt
Rendered layout ergonomics
Why this needs attention
The browser-rendered page has layout or tap-target issues.
Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
Recommended correction
Evidence
Horizontal overflow: 0px. Small tap targets: 193. Failed: earned 0 of 9 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 13: fix during launch polish.
Affected elements
Skip to main content
Aura++
Browse
Submit
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-18T16:38:23.959Z.
Structured data
Detected 2 JSON-LD block(s), 0 parse error(s), and types EntryPoint, ImageObject, Organization, SearchAction, WebPage, WebSite.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Detected 3 of 3 core identity signals across the title, description, and H1.
Answer-ready visible text
Detected 1771 visible words and 44 audience, use-case, pricing, or integration signals.
Authorship and accountability
No author meta value or structured-data author was detected.
Published or updated date
Structured data reports dateModified 2026-08-18T16:55:38.010Z.
Supporting-source links
Detected 50 external source or reference link(s); link quality still requires editorial review.
Rendered content availability
Rendered audit completed with 0 visible text element(s).
Synthetic search-agent reachability
8 of 8 search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
https://auraplusplus.com/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.
OAI-SearchBotAI search
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 97% parity
Controls: robots meta: index, follow
GPTBotModel training
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index, follow
ChatGPT-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: index, follow
ClaudeBotModel training
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index, follow
Claude-SearchBotAI search
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 97% parity
Controls: robots meta: index, follow
Claude-UserUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 97% parity
Controls: robots meta: index, follow
GooglebotSearch and discovery
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 97% parity
Controls: robots meta: index, follow; Googlebot meta: index, follow, max-video-preview:-1, max-image-preview:large, max-snippet:-1
Google-ExtendedData-use policy control
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index, follow
BingbotSearch and discovery
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 93% parity
Controls: robots meta: index, follow
PerplexityBotAI search
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 97% parity
Controls: robots meta: index, follow
Perplexity-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: index, follow
ApplebotSearch and discovery
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 93% parity
Controls: robots meta: index, follow
Applebot-ExtendedData-use policy control
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index, follow
MistralAI-IndexAI search
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 97% parity
Controls: robots meta: index, follow
MistralAI-UserUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 97% parity
Controls: robots meta: index, follow
meta-externalagentModel training
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index, follow
meta-externalfetcherUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 97% parity
Controls: robots meta: index, follow
AmazonbotModel training
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index, follow
Amzn-SearchBotAI search
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 97% parity
Controls: robots meta: index, follow
Amzn-UserUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 97% parity
Controls: robots meta: index, follow
CCBotModel training
Robots: allowed by * allow: / · line 2
Probe: not tested for this 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. 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.
