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 9, 2026, 1:48 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
60/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability69%Agent Easeof Use69%Security& Trust76%GEO, AIO, AEO67%SEO100%Performance71%Accessibility0%
  • AI Discoverability 69 out of 100
  • Agent Ease of Use 69 out of 100
  • Security & Trust 76 out of 100
  • GEO, AIO and AEO 67 out of 100
  • SEO 100 out of 100
  • Performance 71 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Playboy Official Store | Apparel, Lingerie & Collectibles favicon

Playboy Official Store | Apparel, Lingerie & Collectibles

Shop official Playboy apparel, collectibles & lifestyle products. Men's & women's clothing, lingerie, accessories & exclusive collaborations.

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
69
Needs work3000
Discoverability
67
Needs work800
Content Readiness
79
Mostly ready1900
Bot Access Control
63
Needs work300
Agent Ease of Use
69
Needs work1900
Auth
68
Needs work1000
Agent Commerce
93
Strong600
Google Agentic Browsing
100
Strong300
GEO, AIO and AEO
67
Needs work900
GEO Readiness
Not Applicable
Not Applicable300
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable300
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
76
Mostly ready1922View details
Security & Trust
76
Mostly ready1922View details
Performance
71
Needs work1210View details
Performance
71
Needs work1210View 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".

50 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

CSP does not define default-src; several fetch directives may have no restrictive fallback.

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

50/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

    CSP does not define default-src; several fetch directives may have no restrictive fallback.

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

    No script-src or default-src directive constrains script execution.

    CSP script execution policy is unsafe
  3. Review hardening directives

    CSP is missing recommended hardening directives: object-src, base-uri, form-action.

    CSP hardening directives are missing or weak
  4. Review CSP reporting

    CSP does not define a reporting endpoint.

    CSP reporting is missing or incomplete
Evidence log4 steps · 16 lines
Evaluate fetch baseline [fail]! CSP does not define default-src; several fetch directives may have no restrictive fallback.INFOEvaluate fetch baselineINFOEvaluate resource loading fallback explicitFetchDirectives=[]FAILCompare fetch baseline actual="0 explicit fetch directives" expected="restricted default-src or broad explicit fetch coverage" issue="CSP does not define default-src; several fetch directives may have no restrictive fallback."FAILCSP does not define default-src; several fetch directives may have no restrictive fallback.Evaluate script execution [fail]! No script-src or default-src directive constrains script execution.INFOEvaluate script executionINFOInspect effective script directive FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":false,"hasUnsafeEval":false,"hasWildcardHost":false,"hasBroadScheme":false,"dangerousSchemes":[]} expected="constrained script sources without unsafe execution allowances" issue="No script-src or default-src directive constrains script execution."FAILNo script-src or default-src directive constrains script execution.Review hardening directives [warning]! CSP is missing recommended hardening directives: object-src, base-uri, form-action.INFOReview hardening directivesINFOInspect CSP hardening directives frameAncestors=["'none'"] formCount=11WARNCompare recommended hardening coverage actual=["object-src","base-uri","form-action"] expected="no missing object-src/base-uri/form-action requirements" issue="CSP is missing recommended hardening directives: object-src, base-uri, form-action."WARNCSP is missing recommended hardening directives: object-src, base-uri, form-action.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.

PerformancePerformanceBrowser audit

Forced reflow

100 Fail

Check name

Forced reflow

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations.

Evidence
{
  "description": "A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations."
}

AccessibilityAccessibilityBrowser audit

Form elements must have labels

100 Fail

Check name

Form elements must have labels

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Form elements must have labels

Evidence
{
  "ruleId": "label",
  "impact": "critical",
  "description": "Ensure every form element has a label",
  "tags": [
    "cat.forms",
    "wcag2a",
    "wcag412",
    "section508",
    "section508.22.n",
    "TTv5",
    "TT5.c",
    "EN-301-549",
    {
      "truncated": true,
      "omittedCount": 4,
      "originalCount": 12
    }
  ],
  "affectedNodeCount": 1,
  "nodes": [
    {
      "target": [
        "body > input"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 110
      },
      "failureSummary": "Fix any of the following:\n  Element does not have an implicit (wrapped) <label>\n  Element does not have an explicit <label>\n  aria-label attribute does not exist or is empty\n  aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty\n  Element has no title attribute\n  Element has no placeholder attribute\n  Element's default semantics were not overridden with role=\"none\" or role=\"presentation\""
    }
  ]
}

Sign in to see 38 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
60/100Level 3, Bot-AwareCurrent report