CanAgentUse tools

UCP Suite

Validate Universal Commerce Protocol discovery, then test product search, carts, checkout links, and merchant handoff flows.

MCP Playground

Connect to remote MCP servers, inspect tools and resources, test prompts, auth, headers, notifications, and JSON-RPC responses.

A2A Playground

Inspect Agent Cards, validate advertised endpoints, and prepare safe requests for agent-to-agent workflows.

Agent Website Viewer

Enter a public URL and see the roles, names, landmarks, controls, and blockers that shape how AI agents understand the page.

SCANNED
Jul 2, 2026, 7:04 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
54/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability68%Agent Easeof Use65%Security& Trust78%GEO, AIO, AEO58%SEO92%Performance38%Accessibility0%
  • AI Discoverability 68 out of 100
  • Agent Ease of Use 65 out of 100
  • Security & Trust 78 out of 100
  • GEO, AIO and AEO 58 out of 100
  • SEO 92 out of 100
  • Performance 38 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Cybersecurity & Data Protection Solutions - Acronis favicon

Cybersecurity & Data Protection Solutions - Acronis

Acronis provides award-winning backup software & data protection solutions for consumers, businesses & MSPs. Protect your sensitive information!

Open Agent View

Next step

Turn this report into a fix workflow

1 failed check is ready to move into MCP or CLI remediation. Generate a repair prompt, connect the scanner to your coding agent, or open the integration docs before your next rescan.

Fix with MCP / CLI
Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
68
Needs work3700
Discoverability
43
Priority fix500
Content Readiness
92
Strong2800
Bot Access Control
69
Needs work400
Agent Ease of Use
65
Needs work800
API
67
Needs work100
Agent Commerce
80
Mostly ready400
Google Agentic Browsing
100
Strong300
GEO, AIO and AEO
58
Needs work600
GEO Readiness
Not Applicable
Not Applicable100
AIO Readiness
Not Applicable
Not Applicable200
AEO Readiness
Not Applicable
Not Applicable300
SEO
92
Strong900
SEO
92
Strong900
Security & Trust
78
Mostly ready2112View details
Security & Trust
78
Mostly ready2112View details
Performance
38
Priority fix1210View details
Performance
38
Priority fix1210View details
Accessibility
0
Priority fix010View details
Accessibility
0
Priority fix010View details

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Evaluate fetch baseline".

30 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

default-src is present but not meaningfully restrictive.

Details

02

Why it matters

Content Security Policy reduces the impact of injection bugs by limiting where scripts, styles, frames, forms, and other browser resources can load or execute.

Check name

Content-Security-Policy

Score

70/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Constrain browser resource loading and script execution with an enforcing Content-Security-Policy header.

Result

Content-Security-Policy failed at "Evaluate fetch baseline".

Validation steps

  1. Evaluate fetch baseline

    default-src is present but not meaningfully restrictive.

    CSP fetch baseline is too broad or missing
  2. Evaluate script execution

    script-src allows unsafe-eval.

    CSP script execution policy is unsafe
  3. Review CSP reporting

    CSP does not define a reporting endpoint.

    CSP reporting is missing or incomplete
Evidence log3 steps · 12 lines
Evaluate fetch baseline [fail]! default-src is present but not meaningfully restrictive.INFOEvaluate fetch baselineINFOEvaluate resource loading fallback defaultSrc=["https:"] explicitFetchDirectives=["connect-src","font-src","frame-src","img-src","object-src","script-src","script-src-elem","style-src","worker-src"]FAILCompare fetch baseline actual=["https:"] expected="restricted default-src or broad explicit fetch coverage" issue="default-src is present but not meaningfully restrictive."FAILdefault-src is present but not meaningfully restrictive.Evaluate script execution [warning]! script-src allows unsafe-eval.INFOEvaluate script executionINFOInspect effective script directive effectiveDirective="script-src" sources=["'unsafe-inline'","'unsafe-eval'","'nonce-d8ea914fd49546f000efc65640bbc7d3'","*.recaptcha.net","*.acronis.com","*.googletagmanager.com","widget.trustpilot.com","tagmanager.google.com","*.visualize-roi.com","optimize.google.com","www.google-analytics.com","www.googleadservices.com","www.googleanalytics.com","www.googleoptimize.com","*.visualwebsiteoptimizer.com","app.vwo.com","unboundcrm.com","*.demandbase.com"]WARNCompare script execution posture actual={"hasNonce":true,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":true,"hasUnsafeEval":true,"hasWildcardHost":true,"hasBroadScheme":false,"dangerousSchemes":[]} expected="constrained script sources without unsafe execution allowances" issue="script-src allows unsafe-eval."WARNscript-src allows unsafe-eval.Review CSP reporting [warning]! CSP does not define a reporting endpoint.INFOReview CSP reportingINFOInspect CSP reporting directives reportOnlyHeaderPresent=false reportOnlyDirectives=[]WARNCompare violation reporting configuration actual="no reporting endpoint" expected="report-to or report-uri present" issue="CSP does not define a reporting endpoint."WARNCSP does not define a reporting endpoint.

AccessibilityAccessibilityBrowser audit

Accessibility audit

100 Fail

Check name

Accessibility audit

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Make sure the page can load in Chrome and run Accessibility checks.

Evidence
{
  "error": "__name is not defined"
}

PerformancePerformanceBrowser audit

Font display

100 Fail

Check name

Font display

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 60 ms

Fix guidance

Consider setting [font-display](https://developer.chrome.com/docs/performance/insights/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).

Evidence
{
  "displayValue": "Est savings of 60 ms",
  "description": "Consider setting [font-display](https://developer.chrome.com/docs/performance/insights/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks)."
}

Sign in to see 39 other issues and the full report

Create a free account to unlock every issue, evidence details, exports, and higher free limits.

Email code

Fix with MCP or CLI

Use this report as the handoff into remediation. Generate a coding-agent prompt with the failing checks attached, or jump to the MCP and CLI setup docs before your next rescan.

Fix with MCP / CLI

Score history

Public scan score over time

Public reports for this website origin. Select any point or report link to open that canonical report.

1 reports
Public score history report links
Scan dateScoreReadinessReport
54/100Level 3, Bot-AwareCurrent report