Rescan Report
Share Report
Copy Report Link
Rescan Report
Share Report
Copy Report Link
Export Report
50/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability47%Agent Easeof Use49%Security& Trust78%GEO, AIO, AEO67%SEO85%Performance48%Accessibility0%
  • AI Discoverability 47 out of 100
  • Agent Ease of Use 49 out of 100
  • Security & Trust 78 out of 100
  • GEO, AIO and AEO 67 out of 100
  • SEO 85 out of 100
  • Performance 48 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

technical apparel + athletic shoes | lululemon favicon

technical apparel + athletic shoes | lululemon

lululemon activewear, loungewear and footwear for all the ways you love to move. Sweat, grow & connect in performance apparel.

Next step

Turn this report into a fix workflow

12 failed checks are 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.

Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
47
Priority fix23196View details
Discoverability
20
Priority fix270View details
Content Readiness
53
Needs work18123View details
Bot Access Control
63
Needs work303
Agent Ease of Use
49
Priority fix1110View details
Auth
48
Priority fix112View details
MCP
50
Needs work003
Skill Discovery
50
Needs work005
GEO, AIO and AEO
67
Needs work927View details
GEO Readiness
61
Needs work312View details
AIO Readiness
82
Mostly ready303
AEO Readiness
59
Needs work312View details
SEO
85
Mostly ready820View details
SEO
85
Mostly ready820View details
Security & Trust
78
Mostly ready2024View details
Security & Trust
78
Mostly ready2024View details
Performance
48
Priority fix1394View details
Performance
48
Priority fix1394View details
Accessibility
0
Priority fix063View details
Accessibility
0
Priority fix063View details

Prioritized recommendations

Issues ranked by score impact

60 items need attention

AI DiscoverabilityDiscoverabilityEstablished

Link headers

Link headers failed at "Find useful Link headers".

33 Fail

Needs attention

Link headers

Failed check
01

Issue

No useful agent discovery Link headers were found.

02

Why it matters

Link headers let automated clients discover API catalogs, documentation, and machine-readable alternates without parsing page markup first.

Check name

Link headers

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Include Link response headers for agent discovery using RFC 8288.

Result

Link headers failed at "Find useful Link headers".

Validation steps

  1. Find useful Link headers

    No useful agent discovery Link headers were found.

  2. Fetch same-origin Link header targets

    Link headers did not expose any same-origin targets to validate.

Evidence log2 steps · 9 lines
Find useful Link headers [fail]! No useful agent discovery Link headers were found.INFOFind useful Link headersINFOParse response Link header linkCount=0FAILCompare registered agent-useful relation count actual=0 expected="> 0"FAILCompare community relation count actual=0 expected="accepted as weaker evidence"FAILNo useful agent discovery Link headers were found.Fetch same-origin Link header targets [fail]! Link headers did not expose any same-origin targets to validate.INFOFetch same-origin Link header targetsINFOFetch same-origin Link header targets and record external skipsFAILCompare same-origin Link target failures actual=1 expected=0FAILLink headers did not expose any same-origin targets to validate.

AI DiscoverabilityDiscoverabilityEstablished

Sitemap

Sitemap failed at "Fetch a sitemap candidate".

27 Fail

Needs attention

Sitemap

Failed check
01

Issue

No sitemap candidate returned a successful HTTP response.

02

Why it matters

Sitemaps help crawlers and agents discover canonical URLs, update timestamps, and deeper content that may not be obvious from homepage navigation alone.

Check name

Sitemap

Score

20/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Publish a standards-aligned sitemap or sitemap index at a discoverable URL.

Result

Sitemap failed at "Fetch a sitemap candidate".

Validation steps

  1. Fetch a sitemap candidate

    No sitemap candidate returned a successful HTTP response.

  2. Parse sitemap

    Fetched sitemap content was not a valid sitemap with absolute HTTP(S) URL entries.

  3. Validate sitemap field quality

    No valid sitemap was available for field-quality validation.

  4. Validate URL scope

    No valid sitemap was available for URL scope validation.

Evidence log4 steps · 21 lines
Fetch a sitemap candidate [fail]! No sitemap candidate returned a successful HTTP response.INFOFetch sitemap candidateINFOTrying sitemap candidates in discovery order candidateCount=4INFOTrying to fetch /sitemap.xml url="https://shop.lululemon.com/sitemap.xml"FAIL/sitemap.xml did not return a successful response url="https://shop.lululemon.com/sitemap.xml" statusCode=403INFOTrying to fetch /sitemap.txt url="https://shop.lululemon.com/sitemap.txt"FAIL/sitemap.txt did not return a successful response url="https://shop.lululemon.com/sitemap.txt" statusCode=404INFOTrying to fetch /sitemap_index.xml url="https://shop.lululemon.com/sitemap_index.xml"FAIL/sitemap_index.xml did not return a successful response url="https://shop.lululemon.com/sitemap_index.xml" statusCode=403INFOTrying to fetch /sitemap-index.xml url="https://shop.lululemon.com/sitemap-index.xml"FAIL/sitemap-index.xml did not return a successful response url="https://shop.lululemon.com/sitemap-index.xml" statusCode=403FAILNo sitemap candidate returned HTTP 2xxParse sitemap [fail]! Fetched sitemap content was not a valid sitemap with absolute HTTP(S) URL entries.INFOParse sitemapINFOInspecting fetched sitemap content url="https://shop.lululemon.com/sitemap.xml" contentType="text/html" statusCode=403FAILCheck sitemap contains at least one URL entry or child sitemap entry actual=0 expected="> 0"PASSCheck loc values are absolute HTTP(S) URLs actual=0 expected=0 invalidLocs=[]FAILFetched content was not a valid sitemap format="unknown"Validate sitemap field quality [fail]! No valid sitemap was available for field-quality validation.INFOValidate sitemap field qualitySKIPSkipped field-quality checks because no valid sitemap was availableValidate URL scope [fail]! No valid sitemap was available for URL scope validation.INFOValidate URL scope origin="https://shop.lululemon.com"INFOChecking listed URLs against the scanned origin hostSKIPSkipped URL-scope checks because no valid sitemap was available

Agent Ease of UseMCPEmerging recommendation

MCP Server Card

MCP Server Card has a validation warning at "Discover MCP server card".

25 Warning

Needs attention

MCP Server Card

Warning
01

Issue

No MCP server card was found at current, transitional, or linked discovery paths.

02

Why it matters

MCP server cards give agents a stable, public pre-connection discovery surface for server identity, remote transports, protocol compatibility, and safe routing without guessing endpoints.

Check name

MCP Server Card

Score

50/100

Status

warning

Category

MCP

Maturity

Emerging recommendation

Goal

Publish an MCP Server Card that helps agents discover remote MCP server transports before opening a session.

Result

MCP Server Card has a validation warning at "Discover MCP server card".

Validation steps

  1. Discover MCP server card

    No MCP server card was found at current, transitional, or linked discovery paths.

Evidence log1 step · 14 lines
Discover MCP server card [warning]! No MCP server card was found at current, transitional, or linked discovery paths.INFODiscover MCP server card candidateCount=5INFOBuild MCP server-card candidate list currentPath="/.well-known/mcp-server-card" transitionalPaths=["/.well-known/mcp/server-card.json","/.well-known/mcp/server-cards.json","/mcp.json","/.well-known/mcp.json"] linkedPaths=[]PASSCheck whether page claims MCP support actual=false expected="true only when HTML or Link headers mention MCP" textMatches=[] headerLinkCount=0INFOTrying to fetch /.well-known/mcp-server-card url="https://shop.lululemon.com/.well-known/mcp-server-card" source="current"FAIL/.well-known/mcp-server-card did not return a usable server card statusCode=403 contentType="text/html"INFOTrying to fetch /.well-known/mcp/server-card.json url="https://shop.lululemon.com/.well-known/mcp/server-card.json" source="transitional"FAIL/.well-known/mcp/server-card.json did not return a usable server card statusCode=403 contentType="text/html"INFOTrying to fetch /.well-known/mcp/server-cards.json url="https://shop.lululemon.com/.well-known/mcp/server-cards.json" source="transitional"FAIL/.well-known/mcp/server-cards.json did not return a usable server card statusCode=403 contentType="text/html"INFOTrying to fetch /mcp.json url="https://shop.lululemon.com/mcp.json" source="transitional"FAIL/mcp.json did not return a usable server card statusCode=403 contentType="text/html"INFOTrying to fetch /.well-known/mcp.json url="https://shop.lululemon.com/.well-known/mcp.json" source="transitional"FAIL/.well-known/mcp.json did not return a usable server card statusCode=403 contentType="text/html"WARNNo MCP server card was found reason="No MCP server card was found at current, transitional, or linked discovery paths."

Agent Ease of UseMCPEmerging recommendation

WebMCP

WebMCP has a validation warning at "Probe WebMCP operability".

25 Warning

Needs attention

WebMCP

Warning
01

Issue

No WebMCP surface was found to probe.

Details

02

Why it matters

WebMCP gives agents structured page and browser tool hints so they can understand actions without relying only on screen scraping.

Check name

WebMCP

Score

50/100

Status

warning

Category

MCP

Maturity

Emerging recommendation

Goal

Expose browser/page WebMCP tools and compatible static WebMCP metadata when a site wants agents to understand in-page actions.

Result

WebMCP has a validation warning at "Probe WebMCP operability".

Validation steps

  1. Detect WebMCP runtime API

    Expose current WebMCP tools through document.modelContext.registerTool(), or clearly document navigator.modelContext as a compatibility/polyfill profile.

  2. Probe WebMCP operability

    No WebMCP surface was found to probe.

    WebMCP operability findings
    • No WebMCP surface was found to probe.
  3. Validate declarative WebMCP form tools

    No W3C-style declarative WebMCP form attributes were found.

  4. Validate MCP-aware HTML annotations

    No data-mcp-tool or hyphenated WebMCP compatibility annotations were found.

  5. Validate static WebMCP JSON compatibility

    No static WebMCP JSON manifest or WMCP interaction graph was found.

  6. Validate WebMCP tool metadata quality

    Use clear tool names, useful descriptions, constrained schemas, side-effect clarity, and profile-appropriate naming.

  7. Review WebMCP security and policy signals

    Remove secrets and prompt-injection text from WebMCP metadata, avoid private endpoints, and use Permissions-Policy and annotations for tool safety.

Evidence log7 steps · 31 lines
Detect WebMCP runtime API [informational]INFODetect WebMCP runtime API status="informational"INFOProbe rendered browser for WebMCP runtime objects SKIPCheck current W3C runtime API actual="not detected" expected="document.modelContext/registerTool available"INFOWebMCP evidence was recorded for context. status="informational"Probe WebMCP operability [warning]! No WebMCP surface was found to probe.INFOProbe WebMCP operability status="warning"INFORun safe WebMCP operability checks safeProbeOnly=trueWARNCheck usable WebMCP evidence actual=0 expected="at least 1 usable runtime, declarative, annotation, or static manifest signal"WARNWebMCP operability warning warning="No WebMCP surface was found to probe."WARNNo WebMCP surface was found to probe.Validate declarative WebMCP form tools [informational]! No W3C-style declarative WebMCP form attributes were found.INFOValidate declarative WebMCP form tools status="informational"INFOInspect visible forms and controls for current declarative WebMCP attributes annotatedElements=0 formsWithAttributes=0 controlsWithAttributes=0SKIPValidate declarative WebMCP attribute quality actual=0 expected=0INFONo W3C-style declarative WebMCP form attributes were found. status="informational"Validate MCP-aware HTML annotations [informational]! No data-mcp-tool or hyphenated WebMCP compatibility annotations were found.INFOValidate MCP-aware HTML annotations status="informational"INFOInspect HTML for MCP compatibility annotations compatibilityAttributeCount=0 dataMcpToolCount=0 examples=[]SKIPValidate compatibility annotation quality actual=0 expected=0INFONo data-mcp-tool or hyphenated WebMCP compatibility annotations were found. status="informational"Validate static WebMCP JSON compatibility [warning]! No static WebMCP JSON manifest or WMCP interaction graph was found.INFOValidate static WebMCP JSON compatibility status="warning"INFODiscover static WebMCP manifest candidates conventionalPaths=["/.well-known/webmcp.json","/webmcp.json"] checkedCount=2 profileCounts={}INFOWebMCP manifest candidate checked source="path" path="/.well-known/webmcp.json" url="https://shop.lululemon.com/.well-known/webmcp.json" statusCode=403 contentType="text/html"INFOWebMCP manifest candidate checked source="path" path="/webmcp.json" url="https://shop.lululemon.com/webmcp.json" statusCode=403 contentType="text/html"WARNValidate discovered static WebMCP metadata actual={"validManifestCount":0,"invalidManifestCount":0,"toolCount":0,"wmcpActionCount":0} expected="at least 1 valid tools[] manifest or WMCP graph when static metadata is present"WARNNo static WebMCP JSON manifest or WMCP interaction graph was found.Validate WebMCP tool metadata quality [informational]INFOValidate WebMCP tool metadata quality status="informational"INFOInspect WebMCP tool names, descriptions, schemas, and safety hints toolCount=0SKIPCheck tool metadata findings actual={"issueCount":0,"warningCount":0} expected="0 issues and 0 warnings"INFOWebMCP evidence was recorded for context. status="informational"Review WebMCP security and policy signals [informational]INFOReview WebMCP security and policy signals status="informational"INFOInspect WebMCP security and policy signals permissionsPolicy="(missing)" failureCount=0 warningCount=0PASSCheck security findings actual={"failures":0,"warnings":0} expected="0 failures and 0 warnings"INFOWebMCP evidence was recorded for context. status="informational"

Security & TrustSecurity & TrustEstablished

Referrer-Policy

Referrer-Policy failed at "Find Referrer-Policy header".

22 Fail

Needs attention

Referrer-Policy

Failed check
01

Issue

Referrer-Policy header is missing.

02

Why it matters

Referrer-Policy controls how much URL context is sent to other origins, limiting accidental leakage of paths, queries, and identifiers.

Check name

Referrer-Policy

Score

33/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Limit how much referrer data leaves the site with an explicit Referrer-Policy header.

Result

Referrer-Policy failed at "Find Referrer-Policy header".

Validation steps

  1. Find Referrer-Policy header

    Referrer-Policy header is missing.

  2. Review observed browser responses

    One or more same-origin HTML documents observed by Chrome did not emit Referrer-Policy.

Evidence log2 steps · 8 lines
Find Referrer-Policy header [fail]! Referrer-Policy header is missing.INFOFind Referrer-Policy headerINFORead Referrer-Policy delivery header="referrer-policy" value="missing" metaReferrerPolicyCount=0 browserDefault="strict-origin-when-cross-origin"FAILRequire explicit HTTP Referrer-Policy header actual="missing" expected="HTTP response header present" issue="Referrer-Policy header is missing."FAILReferrer-Policy header is missing.Review observed browser responses [warning]! One or more same-origin HTML documents observed by Chrome did not emit Referrer-Policy.INFOReview observed browser responsesINFOSample Chrome-observed same-origin responses observedResponseCount=120 sameOriginCount=87 htmlDocumentCount=1WARNCompare observed Referrer-Policy coverage actual={"missingPolicyCount":1,"unsafeOrInvalidPolicyCount":0,"weakPolicyCount":0,"affected":[{"url":"https://shop.lululemon.com/","status":200,"resourceType":"document","contentType":"text/html; charset=utf-8","referrerPolicy":null,"classification":"invalid"}]} expected="0 missing, unsafe, invalid, or weak same-origin HTML responses" issue="One or more same-origin HTML documents observed by Chrome did not emit Referrer-Policy."WARNOne or more same-origin HTML documents observed by Chrome did not emit Referrer-Policy.

AI DiscoverabilityDiscoverabilityEstablished

robots.txt

robots.txt failed at "Validate RFC 9309 core syntax".

20 Fail

Needs attention

robots.txt

Failed check
01

Issue

robots.txt was found but did not contain a valid, parseable User-agent group.

02

Why it matters

robots.txt gives crawlers and agents a standard place to read crawl permissions, disallowed paths, and sitemap locations before requesting site content.

Check name

robots.txt

Score

40/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Publish /robots.txt with clear crawl rules.

Result

robots.txt failed at "Validate RFC 9309 core syntax".

Validation steps

  1. Validate RFC 9309 core syntax

    robots.txt was found but did not contain a valid, parseable User-agent group.

Evidence log1 step · 5 lines
Validate RFC 9309 core syntax [fail]! robots.txt was found but did not contain a valid, parseable User-agent group.INFOValidate RFC 9309 core syntaxINFOParsing robots.txt into User-agent groups and Allow/Disallow recordsPASSCheck User-agent group count actual=2 expected=">= 1 parseable group" parsedUserAgents=["*","meta-externalagent"]FAILCheck malformed lines and orphan Allow/Disallow records actual={"invalidLines":0,"orphanRecords":10} expected={"invalidLines":0,"orphanRecords":0}FAILAllow/Disallow records appeared before any User-agent group orphanRecords=[{"directive":"disallow","value":"*/search?Ntt=*","line":3},{"directive":"disallow","value":"/shop/gadgets/","line":4},{"directive":"disallow","value":"/cartridges/FeaturesResultsList/","line":5},{"directive":"disallow","value":"/search/","line":6},{"directive":"disallow","value":"/*?Ns=price*","line":7}]

Agent Ease of UseAuthEstablished

OAuth / OIDC discovery

OAuth / OIDC discovery failed at "Fetch discovery metadata".

19 Fail

Needs attention

OAuth / OIDC discovery

Failed check
01

Issue

OAuth/OIDC was claimed or referenced, but no registered OAuth/OIDC discovery document was found.

02

Why it matters

OAuth and OIDC discovery let agents and API clients find authorization, token, and key endpoints programmatically instead of scraping login pages or guessing provider setup.

Check name

OAuth / OIDC discovery

Score

43/100

Status

fail

Category

Auth

Maturity

Established

Goal

Publish OAuth/OIDC discovery metadata only when the site operates or advertises a real OAuth/OIDC authorization server.

Result

OAuth / OIDC discovery failed at "Fetch discovery metadata".

Validation steps

  1. Fetch discovery metadata

    OAuth/OIDC was claimed or referenced, but no registered OAuth/OIDC discovery document was found.

Evidence log1 step · 6 lines
Fetch discovery metadata [fail]! OAuth/OIDC was claimed or referenced, but no registered OAuth/OIDC discovery document was found.INFOFetch discovery metadataINFOTrying OAuth/OIDC well-known metadata candidates checkedCount=2INFOChecked discovery candidate path="/.well-known/openid-configuration" statusCode=403 contentType="text/html" length=420INFOChecked discovery candidate path="/.well-known/oauth-authorization-server" statusCode=403 contentType="text/html" length=430FAILCheck discovery metadata fetch succeeded actual=2 expected="HTTP 2xx JSON metadata document"FAILFetch discovery metadata failed issue="OAuth/OIDC was claimed or referenced, but no registered OAuth/OIDC discovery document was found."

Agent Ease of UseAuthEmerging recommendation

Auth.md Agent Registration

Auth.md Agent Registration has a validation warning at "Warn when auth surface lacks Auth.md".

17 Warning

Needs attention

Auth.md Agent Registration

Warning
01

Issue

The site appears to support login, signup, account access, or credentials but does not publish /auth.md.

02

Why it matters

Human login and signup flows are often opaque to agents. Auth.md gives automated clients a stable registration contract instead of forcing them to scrape docs, automate browser forms, or guess credential flows.

Check name

Auth.md Agent Registration

Score

50/100

Status

warning

Category

Auth

Maturity

Emerging recommendation

Goal

Publish Auth.md v1 metadata so agents can discover how to register, claim a user, and obtain credentials.

Result

Auth.md Agent Registration has a validation warning at "Warn when auth surface lacks Auth.md".

Validation steps

  1. Warn when auth surface lacks Auth.md

    The site appears to support login, signup, account access, or credentials but does not publish /auth.md.

Evidence log1 step · 2 lines
Warn when auth surface lacks Auth.md [warning]! The site appears to support login, signup, account access, or credentials but does not publish /auth.md.INFOWarn when auth surface lacks Auth.mdWARNThe site appears to support login, signup, account access, or credentials but does not publish /auth.md.

AI DiscoverabilityBot Access ControlInformational

Content Signal

Content Signal has a validation warning at "Validate declared usage preferences".

17 Warning

Needs attention

Content Signal

Warning
01

Issue

No Content-Usage or Content-Signal declarations were found.

02

Why it matters

Content usage preference signals communicate intended downstream AI use separately from robots.txt crawl permission. They can express training and search preferences for compliant systems without replacing access-control rules.

Check name

Content Signal

Score

50/100

Status

warning

Category

Bot Access Control

Maturity

Informational

Goal

Declare AI content usage preferences when the site intentionally publishes machine-readable usage policy.

Result

Content Signal has a validation warning at "Validate declared usage preferences".

Validation steps

  1. Validate declared usage preferences

    No Content-Usage or Content-Signal declarations were found.

Evidence log1 step · 5 lines
Validate declared usage preferences [warning]! No Content-Usage or Content-Signal declarations were found.INFOValidate declared usage preferencesINFOParsing declared preferences into terms and values recordCount=0SKIPSkipping declaration validation because no Content-Usage or Content-Signal records were declared.SKIPCompare declared records to validation requirement actual=0 expected="No validation needed when no records are declared"WARNNo Content-Usage or Content-Signal declarations were present.

Agent Ease of UseAuthEmerging recommendation

OAuth Protected Resource

OAuth Protected Resource has a validation warning at "Detect protected-resource applicability".

17 Warning

Needs attention

OAuth Protected Resource

Warning
01

Issue

Generic authentication signals were found, but no OAuth Protected Resource metadata signal was detected.

02

Why it matters

Protected-resource metadata tells agents which API/resource is locked, which authorization servers can issue tokens for it, and how a 401 challenge maps back to the correct resource.

Check name

OAuth Protected Resource

Score

50/100

Status

warning

Category

Auth

Maturity

Emerging recommendation

Goal

Publish OAuth Protected Resource Metadata for OAuth-protected APIs and MCP resources so clients can identify the resource and its authorization servers.

Result

OAuth Protected Resource has a validation warning at "Detect protected-resource applicability".

Validation steps

  1. Detect protected-resource applicability

    Generic authentication signals were found, but no OAuth Protected Resource metadata signal was detected.

Evidence log1 step · 4 lines
Detect protected-resource applicability [warning]! Generic authentication signals were found, but no OAuth Protected Resource metadata signal was detected.INFODetect protected-resource applicabilityINFOInspecting auth headers, MCP/OAuth claims, and protected-resource hints applies=false requiresAuthorizationServers=false signalsCount=0 genericAuthSignalsCount=3 checkedCount=1WARNCheck protected-resource metadata applicability actual=false expected="true when RFC 9728 metadata exists or support is claimed" checked=[{"url":"https://shop.lululemon.com/.well-known/oauth-protected-resource","path":"/.well-known/oauth-protected-resource","source":"root-well-known","resourceIdentifier":"https://shop.lululemon.com","statusCode":403,"contentType":"text/html","length":428}]WARNDetect protected-resource applicability completed with warnings issue="Generic authentication signals were found, but no OAuth Protected Resource metadata signal was detected."

AI DiscoverabilityBot Access ControlEmerging recommendation

RSL license signal

No RSL declarations were found.

17 Warning

Needs attention

RSL license signal

Warning
01

Issue

No RSL declarations were found.

02

Why it matters

Really Simple Licensing is an emerging rights-expression layer for communicating content usage and licensing terms separately from robots.txt crawl permission.

Check name

RSL license signal

Score

50/100

Status

warning

Category

Bot Access Control

Maturity

Emerging recommendation

Goal

Declare machine-readable content licensing terms for compliant AI and crawler systems when the site needs them.

Result

No RSL declarations were found.

Validation steps

  1. Discover RSL declarations

    No RSL declarations were found.

Evidence log1 step · 4 lines
Discover RSL declarations [warning]! No RSL declarations were found.INFODiscover RSL declarationsINFOChecking robots.txt License records, HTTP Link rel=license headers, HTML license links, and inline RSL XML robotsFound=trueSKIPCount discovered RSL declarations actual=0 expected=">= 1 when RSL licensing terms are published" sources={}WARNNo RSL declarations were found on any supported discovery surface.

AI DiscoverabilityBot Access ControlEmerging recommendation

TDMRep declaration

No TDMRep declaration was found.

17 Warning

Needs attention

TDMRep declaration

Warning
01

Issue

No TDMRep declaration was found at /.well-known/tdmrep.json.

02

Why it matters

TDMRep is a W3C Community Group protocol and IANA-registered well-known URI for declaring text and data mining reservation policy on applicable content.

Check name

TDMRep declaration

Score

50/100

Status

warning

Category

Bot Access Control

Maturity

Emerging recommendation

Goal

Publish a machine-readable text and data mining reservation declaration and verifiable ODRL policy when the site needs one.

Result

No TDMRep declaration was found.

Validation steps

  1. Fetch /.well-known/tdmrep.json

    No TDMRep declaration was found at /.well-known/tdmrep.json.

Evidence log1 step · 4 lines
Fetch /.well-known/tdmrep.json [warning]! No TDMRep declaration was found at /.well-known/tdmrep.json.INFOFetch /.well-known/tdmrep.jsonINFORequesting origin-level TDMRep declaration at /.well-known/tdmrep.jsonWARNCompare TDMRep file response actual=403 expected="2xx with JSON array when origin-level TDMRep is published" contentType="text/html" length=411WARNNo TDMRep declaration was found at /.well-known/tdmrep.json. 

AI DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is missing or incomplete.

14 Fail

Needs attention

Content freshness signals

Failed check
01

Issue

Content freshness signals are incomplete: missing any valid freshness date in Last-Modified, Schema.org, Open Graph, Dublin Core, generic meta, or sitemap lastmod.

Details

02

Why it matters

Freshness signals help agents, crawlers, and search systems decide whether content is current enough to cite, summarize, cache, or compare against newer sources.

Check name

Content freshness signals

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Expose modified and published dates for freshness-aware retrieval, citation, and ranking.

Result

Content freshness signals is missing or incomplete.

Validation steps

  1. Validate Last-Modified header

    No valid Last-Modified HTTP header was found.

  2. Validate structured freshness dates

    No Schema.org freshness dates were found.

  3. Validate metadata freshness dates

    No Open Graph, Dublin Core, or generic meta freshness date was found.

  4. Corroborate with sitemap lastmod

    Add a sitemap entry with a valid lastmod for the canonical page URL when sitemap corroboration is useful.

Evidence log4 steps · 16 lines
Validate Last-Modified header [fail]! No valid Last-Modified HTTP header was found.INFOValidate Last-Modified headerINFOReading Last-Modified response headerFAILCheck Last-Modified header is present and parseable actual="missing" expected="valid" alternateDates=[]FAILLast-Modified header is missing or invalidValidate structured freshness dates [fail]! No Schema.org freshness dates were found.INFOValidate structured freshness datesINFOCollecting Schema.org freshness dates from JSON-LD, Microdata, and RDFaFAILCheck structured freshness date count actual=0 expected="> 0" invalidDateCount=0 formats={} alternateDates=[]FAILNo structured freshness dates foundValidate metadata freshness dates [fail]! No Open Graph, Dublin Core, or generic meta freshness date was found.INFOValidate metadata freshness datesINFOCollecting Open Graph, Dublin Core, and generic meta freshness datesFAILCheck metadata freshness date count actual=0 expected="> 0" metaDateCount=0 invalidDateCount=0 alternateDates=[]FAILNo metadata freshness dates foundCorroborate with sitemap lastmod [warning]INFOCorroborate with sitemap lastmodINFODiscovering sitemap candidates and matching the scanned page URL candidateCount=1 attempts=1WARNCheck matching sitemap lastmod actual="no match" expected="valid match when available" robotsStatusCode=200WARNNo matching sitemap lastmod found after sitemap attempts attempts=1

AI DiscoverabilityContent ReadinessEmerging recommendation

llms.txt

llms.txt failed at "Fetch root llms.txt".

14 Fail

Needs attention

llms.txt

Failed check
01

Issue

/llms.txt was not found or could not be fetched.

02

Why it matters

llms.txt is an emerging Markdown convention for giving language-model clients curated context and links before they crawl broadly. Broken, private, or low-signal links make the file much less useful even when it exists.

Check name

llms.txt

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Emerging recommendation

Goal

Publish a concise llms.txt index that helps agents discover useful public site context.

Result

llms.txt failed at "Fetch root llms.txt".

Validation steps

  1. Fetch root llms.txt

    /llms.txt was not found or could not be fetched.

  2. Inspect optional llms-full.txt

    Passed.

Evidence log2 steps · 7 lines
Fetch root llms.txt [fail]! /llms.txt was not found or could not be fetched.INFOFetch root llms.txt path="/llms.txt"INFOTrying to fetch /llms.txt url="https://shop.lululemon.com/llms.txt"FAIL/llms.txt was not found or could not be fetched statusCode=404FAILFetch root llms.txt failed reason="/llms.txt is required for this check."Inspect optional llms-full.txt [informational]INFOInspect optional llms-full.txtINFOTrying to fetch /llms-full.txt url="https://shop.lululemon.com/llms-full.txt"SKIP/llms-full.txt is not present statusCode=404

AI DiscoverabilityContent ReadinessEstablished

Markdown negotiation

Markdown negotiation is missing or incomplete.

13 Fail

Needs attention

Markdown negotiation

Failed check
01

Issue

Best candidate returned Content-Type "text/html" instead of text/markdown.

02

Why it matters

Markdown representations give agents a cleaner page form while preserving normal HTML for browsers and cache-safe representation handling.

Check name

Markdown negotiation

Score

10/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Expose a useful Markdown representation through negotiation or an explicit alternate URL.

Result

Markdown negotiation is missing or incomplete.

Validation steps

  1. Markdown representation

    No usable Markdown representation was found through negotiation, advertised alternates, or conservative .md mirror checks.

  2. Same-URL negotiation

    Same-URL Accept: text/markdown did not return a valid Markdown representation.

  3. Markdown format validation

    Markdown response appears to expose MDX/JSX source rather than rendered agent-facing Markdown.

  4. Advertised Markdown alternate

    No Link or HTML rel=alternate text/markdown URL was advertised.

  5. Conventional .md mirror

    Conventional .md mirror candidates did not return valid Markdown.

Evidence log5 steps · 15 lines
Markdown representation [fail]! No usable Markdown representation was found through negotiation, advertised alternates, or conservative .md mirror checks.INFOMarkdown representationFAILCheck usable Markdown representation was selected actual={"source":"negotiated","url":"https://shop.lululemon.com/","statusCode":403,"contentType":"text/html","mediaType":"text/html","vary":"","requireVaryAccept":true,"contentTypeStatus":"fail","cacheStatus":"fail","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"mdx-like","hasHeading":false,"headingCount":0,"wordCount":45,"features":{"markdownLinks":0,"referenceLinks":0,"listItems":0,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":11,"jsxOrMdxSignals":7},"issues":["missing-heading","raw-html-heavy","mdx-jsx-source-leakage","plain-text-like"],"excerpt":"<HTML><HEAD>\n<TITLE>Access Denied</TITLE>\n</HEAD><BODY>\n<H1>Access Denied</H1>\n \nYou don't have permission to access \"http&#58;&#47;&#47;shop&#46;lululemon&#46;com&#47;\" on this server.<P>\nReference&#32;&#35;18&#46;8cd70b17&#46;1781745628&#","issue":"Markdown response appears to expose MDX/JSX source rather than rendered agent-facing Markdown."}} expected="negotiated, advertised alternate, or conventional mirror" selected={"source":"negotiated","url":"https://shop.lululemon.com/","statusCode":403,"contentType":"text/html","mediaType":"text/html","vary":"","requireVaryAccept":true,"contentTypeStatus":"fail","cacheStatus":"fail","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"mdx-like","hasHeading":false,"headingCount":0,"wordCount":45,"features":{"markdownLinks":0,"referenceLinks":0,"listItems":0,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":11,"jsxOrMdxSignals":7},"issues":["missing-heading","raw-html-heavy","mdx-jsx-source-leakage","plain-text-like"],"excerpt":"<HTML><HEAD>\n<TITLE>Access Denied</TITLE>\n</HEAD><BODY>\n<H1>Access Denied</H1>\n \nYou don't have permission to access \"http&#58;&#47;&#47;shop&#46;lululemon&#46;com&#47;\" on this server.<P>\nReference&#32;&#35;18&#46;8cd70b17&#46;1781745628&#","issue":"Markdown response appears to expose MDX/JSX source rather than rendered agent-facing Markdown."}} candidatesChecked=2FAILMarkdown representation failed issue="No usable Markdown representation was found through negotiation, advertised alternates, or conservative .md mirror checks."Same-URL negotiation [fail]! Same-URL Accept: text/markdown did not return a valid Markdown representation.INFOSame-URL negotiationFAILCheck negotiated Markdown response actual={"statusCode":403,"mediaType":"text/html","vary":""} expected="HTTP 2xx text/markdown with Vary: Accept" url="https://shop.lululemon.com/" statusCode=403 mediaType="text/html"FAILSame-URL negotiation failed issue="Same-URL Accept: text/markdown did not return a valid Markdown representation."Markdown format validation [fail]! Markdown response appears to expose MDX/JSX source rather than rendered agent-facing Markdown.INFOMarkdown format validationFAILCheck Markdown body quality actual={"valid":false,"wordCount":45,"headingCount":0,"dialect":"mdx-like"} expected="valid Markdown with substantive text and headings" valid=false dialect="mdx-like" wordCount=45 headingCount=0FAILMarkdown format validation failed issue="Markdown response appears to expose MDX/JSX source rather than rendered agent-facing Markdown."Advertised Markdown alternate [warning]! No Link or HTML rel=alternate text/markdown URL was advertised.INFOAdvertised Markdown alternateWARNCheck advertised Markdown alternate candidates actual=0 expected="> 0 when HTML advertises a Markdown alternate" advertisedUrls=[] candidateCount=0WARNAdvertised Markdown alternate has a warning issue="No Link or HTML rel=alternate text/markdown URL was advertised."Conventional .md mirror [fail]! Conventional .md mirror candidates did not return valid Markdown.INFOConventional .md mirrorFAILCheck conventional Markdown mirror candidates actual=1 expected="> 0 when a conventional mirror is discoverable" conventionalUrls=["https://shop.lululemon.com/index.html.md"] candidateCount=1FAILConventional .md mirror failed issue="Conventional .md mirror candidates did not return valid Markdown."

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

A2A Agent Card has a validation warning at "Discover A2A Agent Card".

13 Warning

Needs attention

A2A Agent Card

Warning
01

Issue

No A2A Agent Card was found at the current, legacy, or fallback discovery paths.

02

Why it matters

A2A Agent Cards provide protocol-specific discovery for agent identity, skills, input and output modes, transport bindings, capabilities, and security requirements. Legacy A2A also used /.well-known/agent.json, so scanners must classify the card shape before reporting readiness.

Check name

A2A Agent Card

Score

50/100

Status

warning

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish a version-appropriate A2A Agent Card so A2A-compatible clients can discover agent skills and invoke the declared endpoint safely.

Result

A2A Agent Card has a validation warning at "Discover A2A Agent Card".

Validation steps

  1. Discover A2A Agent Card

    No A2A Agent Card was found at the current, legacy, or fallback discovery paths.

Evidence log1 step · 8 lines
Discover A2A Agent Card [warning]! No A2A Agent Card was found at the current, legacy, or fallback discovery paths.INFODiscover A2A Agent CardINFOTry A2A discovery paths in priority order paths=["/.well-known/agent-card.json","/.well-known/agent.json","/agent-card.json","/.well-known/a2a/agent-card.json"]WARNA2A candidate path did not return a usable card path="/.well-known/agent-card.json" statusCode=403 contentType="text/html"WARNA2A candidate path did not return a usable card path="/.well-known/agent.json" statusCode=403 contentType="text/html"WARNA2A candidate path did not return a usable card path="/agent-card.json" statusCode=403 contentType="text/html"WARNA2A candidate path did not return a usable card path="/.well-known/a2a/agent-card.json" statusCode=403 contentType="text/html"WARNNo A2A Agent Card candidate was selectedWARNNo A2A Agent Card was found at the current, legacy, or fallback discovery paths.

Agent Ease of UseSkill DiscoveryEmerging recommendation

Agent Skills index

Agent Skills index has a validation warning at "Discover Agent Skills index".

13 Warning

Needs attention

Agent Skills index

Warning
01

Issue

No Agent Skills discovery index was found at the canonical or legacy path.

02

Why it matters

An Agent Skills index lets agents discover task-specific instructions through a small trusted index, then verify and load only the skill artifacts they need.

Check name

Agent Skills index

Score

50/100

Status

warning

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish an Agent Skills discovery index that advertises digest-pinned SKILL.md or archive artifacts.

Result

Agent Skills index has a validation warning at "Discover Agent Skills index".

Validation steps

  1. Discover Agent Skills index

    No Agent Skills discovery index was found at the canonical or legacy path.

Evidence log1 step · 5 lines
Discover Agent Skills index [warning]! No Agent Skills discovery index was found at the canonical or legacy path.INFODiscover Agent Skills indexINFOTry Agent Skills index paths in priority order paths=["/.well-known/agent-skills/index.json","/.well-known/skills/index.json"]WARNAgent Skills index candidate was not usable path="/.well-known/agent-skills/index.json" url="https://shop.lululemon.com/.well-known/agent-skills/index.json" statusCode=403WARNAgent Skills index candidate was not usable path="/.well-known/skills/index.json" url="https://shop.lululemon.com/.well-known/skills/index.json" statusCode=403WARNNo Agent Skills discovery index was found at the canonical or legacy path.

Agent Ease of UseSkill DiscoveryEmerging recommendation

agents.json

agents.json has a validation warning at "Discover agents.json".

13 Warning

Needs attention

agents.json

Warning
01

Issue

No Wildcard-style agents.json file was found.

02

Why it matters

Wildcard agents.json gives agents workflow-level context beyond plain OpenAPI, including flows, links, examples, and API action structure. It is an emerging OpenAPI-adjacent proposal, so scanners should validate the contract shape without treating it as an A2A or IETF standard.

Check name

agents.json

Score

50/100

Status

warning

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish a Wildcard-style agents.json file so agents can discover OpenAPI-backed workflows, links, examples, and authentication requirements.

Result

agents.json has a validation warning at "Discover agents.json".

Validation steps

  1. Discover agents.json

    No Wildcard-style agents.json file was found.

Evidence log1 step · 6 lines
Discover agents.json [warning]! No Wildcard-style agents.json file was found.INFODiscover agents.jsonINFOTry agents.json discovery paths in priority order paths=["/.well-known/agents.json","/agents.json"]WARNagents.json candidate path did not return a usable contract path="/.well-known/agents.json" statusCode=403 contentType="text/html"WARNagents.json candidate path did not return a usable contract path="/agents.json" statusCode=403 contentType="text/html"WARNNo agents.json candidate was selectedWARNNo Wildcard-style agents.json file was found.

Agent Ease of UseSkill DiscoveryEmerging recommendation

DNS-AID Agent Discovery

DNS-AID Agent Discovery has a validation warning at "Query DNS-AID records".

13 Warning

Needs attention

DNS-AID Agent Discovery

Warning
01

Issue

No DNS-AID HTTPS/SVCB records were found under _agents.

02

Why it matters

DNS-AID lets agents discover index, A2A, and other agent entrypoints before fetching HTTP metadata. HTTPS/SVCB records provide the service-binding substrate, while DNSSEC can authenticate the discovery answer when available.

Check name

DNS-AID Agent Discovery

Score

50/100

Status

warning

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish DNS-AID HTTPS/SVCB records under _agents for DNS-based agent entrypoint discovery.

Result

DNS-AID Agent Discovery has a validation warning at "Query DNS-AID records".

Validation steps

  1. Query DNS-AID records

    No DNS-AID HTTPS/SVCB records were found under _agents.

  2. Check DNSSEC authentication evidence

    DNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.

Evidence log2 steps · 24 lines
Query DNS-AID records [warning]! No DNS-AID HTTPS/SVCB records were found under _agents.INFOQuery DNS-AID recordsINFOBuild DNS-AID query names from hostname hostname="shop.lululemon.com" labels=["_index._agents.shop.lululemon.com","_a2a._agents.shop.lululemon.com"] claimedOnPage=falseWARNDNS query returned no DNS-AID answers name="_index._agents.shop.lululemon.com" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.shop.lululemon.com" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.shop.lululemon.com" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _index._agents.shop.lululemon.com"WARNDNS query returned no DNS-AID answers name="_a2a._agents.shop.lululemon.com" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.shop.lululemon.com" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.shop.lululemon.com" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _a2a._agents.shop.lululemon.com"WARNCompare total DNS-AID answer count actual=0 expected="> 0"WARNNo DNS-AID HTTPS/SVCB records were found under _agents.Check DNSSEC authentication evidence [warning]! DNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.INFOCheck DNSSEC authentication evidenceWARNCompare DNSSEC authenticated-data flag actual=false expected=trueWARNCompare visible DNSSEC material actual=false expected=trueWARNResolver did not confirm authenticated DNSSEC data name="_index._agents.shop.lululemon.com" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.shop.lululemon.com" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.shop.lululemon.com" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.shop.lululemon.com" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.shop.lululemon.com" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.shop.lululemon.com" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.shop.lululemon.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.shop.lululemon.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="shop.lululemon.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="lululemon.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNDNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Evaluate script execution".

12 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

default-src allows dangerous script schemes: blob:, data:.

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

65/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 script execution".

Validation steps

  1. Evaluate script execution

    default-src allows dangerous script schemes: blob:, data:.

  2. Review hardening directives

    CSP is missing recommended hardening directives: form-action.

  3. Review CSP reporting

    CSP does not define a reporting endpoint.

Evidence log3 steps · 12 lines
Evaluate script execution [fail]! default-src allows dangerous script schemes: blob:, data:.INFOEvaluate script executionINFOInspect effective script directive effectiveDirective="default-src" sources=["'self'","blob:","data:","'unsafe-inline'","'unsafe-eval'","https://amt.adeptmind.ai","https://analytics-ipv6.tiktokw.us","https://1ed92c59f6b0.6a312f71.us-east-1.captcha.awswaf.com","https://1ed92c59f6b0.6a312f71.us-east-1.token.awswaf.com","https://1ed92c59f6b0.us-east-1.captcha-sdk.awswaf.com","https://unq3b64663bf52f407fb93ae5c5d0ccd-crm.omnichannelengagementhub.com","https://api.cash.app","https://cash.app","https://emperia.digital","https://reporting.findmine.com","https://api.findmine.com","https://lit.findmine.com","https://pdimg-prod-fmv3.findmine.com","https://js.findmine.com","https://google.com","https://shopstylecollective.com","https://collectivevoice.com","https://d2hrivdxn8ekm8.cloudfront.net","https://d1lu3pmaz2ilpx.cloudfront.net","https://dvqigh9b7wa32.cloudfront.net","https://d330aiyvva2oww.cloudfront.net","https://geolocation.onetrust.com","https://view.seekxr.com","https://lantern.roeye.com","https://cdn.cookielaw.org","https://app.collectivevoice.com","https://lantern.roeyecdn.com","https://tr6.snapchat.com","https://www.awin1.com","https://www.zenaps.com","https://the.sciencebehindecommerce.com","https://lululemoncanada.us-4.evergage.com","https://www.dwin1.com","https://region1.google-analytics.com","https://region1.analytics.google.com","https://tr.snapchat.com","https://cdn.evgnet.com","https://*.truefitcorp.com","https://privacyportal.onetrust.com","https://analytics-sg.tiktok.com","https://oc-cdn-ocprod.azureedge.net","https://cdn.jsdelivr.net","https://offers.sheerid.com","https://insight.adsrvr.org","https://sc-static.net","https://romeo.liveclicker.com","https://analytics.tiktok.com","https://seal.digicert.com","https://www.pinterest.com","https://*.romeo.liveclicker.com","https://*.doubleclick.net","https://pubads.g.doubleclick.net","https://h.online-metrix.net","https://s7mbrstream.scene7.com","https://socialladder.rkiapps.com","https://us-central1-adaptive-growth.cloudfunctions.net","https://p11.techlab-cdn.com","https://www.onelink-edge.com","https://cdn.pdst.fm","https://js.afterpay.com","https://klarna-payments-na.klarna.com","https://cdn.honey.io","https://ws1.postescanada-canadapost.ca","https://js.klarna.com","https://na.klarnaevt.com","https://x.klarnacdn.net","https://na-library.klarnaservices.com","https://static.quiq-cdn.com","https://lululemon.quiq-api.com","https://portal.afterpay.com","https://static-us.afterpay.com","https://static.afterpay.com","https://graphql.contentful.com","https://*.medallia.com","https://cdn.contentful.com","https://preview.contentful.com","https://www.shopstylecollective.com/","https://tracking.shopstylecollective.com/","https://beta.shopstylecollective.com/","https://test.shopstylecollective.com/","https://optimize.google.com","https://*.kampyle.com","https://functions62d2bb65.azurewebsites.net","https://omny.fm","https://*.braintreegateway.com","https://*.braintree-api.com","https://cdnjs.cloudflare.com","https://*.btttag.com","https://*.demdex.net","https://*.sentry.io","https://sentry.io","https://*.lululemon.com","https://adobedtm.com","https://assets.adobedtm.com","https://scripts.agileone.com","https://cx.atdmt.com","https://static.atgsvcs.com","https://rules.atgsvcs.com","https://bat.bing.com","https://lululemonspna.btttag.com","https://d.btttag.com","https://cache-ssl.celtra.com","https://celtraidentity.com","https://custhelp.com","https://widget.custhelp.com","https://lululemon.custhelp.com","https://lululemonfr.custhelp.com","https://lululemon.widget.custhelp.com","https://www.facebook.com","https://connect.facebook.net","https://clientstream.launchdarkly.com","https://app.launchdarkly.com","https://*.lllapps.com","https://*.lllapi.com","https://www.googletagmanager.com","https://www.google-analytics.com","https://www.googleadservices.com","https://www.google.com","https://maps.gstatic.com","https://fonts.gstatic.com","https://www.gstatic.com","https://adservice.google.com","https://adservice.google.ca","https://www.google.ca","https://fonts.googleapis.com","https://maps.googleapis.com","https://googleads.g.doubleclick.net","https://cdn.ravenjs.com","https://*.bazaarvoice.com","https://*.akamaihd.net","https://cm.everesttech.net","https://cm.g.doubleclick.net","https://stats.g.doubleclick.net","https://bid.g.doubleclick.net","https://ads.celtra.com","https://scripts.agilone.com","https://vsvipmw01.rightnowtech.com","https://*.quantummetric.com","https://ad.doubleclick.net","https://events.launchdarkly.com","https://track.celtra.com","https://ads-twitter.com","https://www.youtube.com","https://*.paypal.com","https://www.paypalobjects.com","https://rlcdn.com","https://di.rlcdn.com","https://s.pinimg.com","https://yimg.com","https://analytics.yahoo.com","https://static.ads-twitter.com","https://analytics.twitter.com","https://t.co","https://ct.pinterest.com","https://beacon.lynx.cognitivlabs.com","https://scene7.com","https://s.ytimg.com","https://s.yimg.com","https://prf.hn","https://ln-rules.rewardstyle.com","https://*.curalate.com","https://d28m5bx785ox17.cloudfront.net","https://d2i1u3dt4wjv23.cloudfront.net","https://sp.analytics.yahoo.com","https://analytics.google.com","https://mpsnare.iesnare.com","https://shopstylecollective.com","https://flex.cybersource.com","https://*.browser-intake-datadoghq.com","https://www.datadoghq-browser-agent.com","https://browser-intake-datadoghq.com","https://lululemon.my.site.com","https://lululemon.my.salesforce-scrt.com","https://login.klarna.com","https://mgln.ai","https://cdn.mgln.ai","https://us.mgln.ai","https://eu.mgln.ai","https://lululemon-com.dlp.retail.adeptmind.net","https://raven.adeptmind.ai","https://pixel.tapad.com","https://www.redditstatic.com","https://alb.reddit.com","https://pixel-config.reddit.com","https://ade.googlesyndication.com","https://pagead2.googlesyndication.com","https://dwin1.com","https://awin1.com","https://zenaps.com","https://www.wepowerconnections.com","https://rts.persado.com","https://cdn.persa.do","https://cdn.persado.com","https://web.btncdn.com","https://api.usebutton.com","https://web.usebutton.com","https://*.kameleoon.com","https://*.kameleoon.io","https://*.kameleoon.eu","https://ecommwidget.trurating.com","https://fonts.googleapis.com","https://ecommapi.trurating.com","https://fonts.gstatic.com","https://amazon-adsystem.com","https://*.amazon-adsystem.com","https://paa-reporting-advertising.amazon","https://*.paa-reporting-advertising.amazon","https://m.media-amazon.com","https://fls-na.amazon.com","https://us.engage.app","https://eu.engage.app","https://talkative-cdn.com","https://sockjs-us2.pusher.com","https://pixel.byspotify.com","https://pixels.spotify.com","https://sockjs-eu.pusher.com","https://*.daily.co","https://osm.klarnaservices.com","https://onelinksmartscript.appsflyer.com","https://impressions.onelink.me","https://lululemon.onelink.me","https://static.experimentation.dev","https://sdk-config.experimentation.dev","https://eu-data.experiment.dev","wss://ws-us2.pusher.com","wss://ws-eu.pusher.com","wss://*.wss.daily.co"]FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":true,"hasUnsafeEval":true,"hasWildcardHost":false,"hasBroadScheme":false,"dangerousSchemes":["blob:","data:"]} expected="constrained script sources without unsafe execution allowances" issue="default-src allows dangerous script schemes: blob:, data:."FAILdefault-src allows dangerous script schemes: blob:, data:.Review hardening directives [warning]! CSP is missing recommended hardening directives: form-action.INFOReview hardening directivesINFOInspect CSP hardening directives objectSrc=["'none'"] baseUri=["'self'"] frameAncestors=["'self'"] formCount=2WARNCompare recommended hardening coverage actual=["form-action"] expected="no missing object-src/base-uri/form-action requirements" issue="CSP is missing recommended hardening directives: form-action."WARNCSP is missing recommended hardening directives: 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.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first passages

AEO: Answer-first passages scored 0/100 and needs a fix.

12 Fail

Needs attention

AEO: Answer-first passages

Failed check
01

Issue

27 section(s) bury or omit a concise opening answer. No direct definition pattern was detected.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Answer-first passages

Score

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

AEO: Answer-first passages scored 0/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Citable passages

GEO: Citable passages scored 35/100 and needs a fix.

8 Fail

Needs attention

GEO: Citable passages

Failed check
01

Issue

No evidence-backed, citation-length explanatory paragraph was found.

Details

02

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: Citable passages

Score

35/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.

Result

GEO: Citable passages scored 35/100 and needs a fix.

AI DiscoverabilityContent ReadinessEstablished

Author attribution

Author attribution is partially implemented.

6 Warning

Needs attention

Author attribution

Warning
01

Issue

No named author or publisher identity could be extracted.

02

Why it matters

Author attribution helps agents cite content responsibly, assess source credibility, and distinguish editorial pages from anonymous marketing copy.

Check name

Author attribution

Score

55/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

Identify content authors or publishers for trust and attribution.

Result

Author attribution is partially implemented.

Validation steps

  1. Schema.org attribution

    Schema.org attribution is incomplete or relies only on publisher/fallback evidence.

  2. Author identity quality

    No named author or publisher identity could be extracted.

Evidence log2 steps · 8 lines
Schema.org attribution [warning]! Schema.org attribution is incomplete or relies only on publisher/fallback evidence.INFOSchema.org attributionINFOChecking structured data for author, creator, and publisher contributorsWARNCheck named Schema.org author count actual=0 expected="> 0" authorCount=0 publisherCount=0 namedContributors=0 authors=[] publishers=[] formats=[]WARNSchema.org attribution is incomplete or fallback-only authorCount=0 publisherCount=0 authors=[] publishers=[]Author identity quality [fail]! No named author or publisher identity could be extracted.INFOAuthor identity qualityINFOChecking contributors for stable identity signalsFAILCheck identified contributor count actual=0 expected="> 0" namedContributors=0 identifiedContributors=[] unidentifiedContributors=[]FAILNo named contributor identity could be extracted

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Source and trust signals

GEO: Source and trust signals scored 50/100 and needs improvement.

6 Warning

Needs attention

GEO: Source and trust signals

Warning
01

Issue

Missing source or trust signals: authorOrOwner, freshnessDate, sourceLinks.

Details

02

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: Source and trust signals

Score

50/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.

Result

GEO: Source and trust signals scored 50/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Evidence and trust

AEO: Evidence and trust scored 57/100 and needs improvement.

5 Warning

Needs attention

AEO: Evidence and trust

Warning
01

Issue

Missing answer evidence or trust signals: author, publisher, freshnessDate.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Evidence and trust

Score

57/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

AEO: Evidence and trust scored 57/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Source and trust signals

AIO: Source and trust signals scored 50/100 and needs improvement.

5 Warning

Needs attention

AIO: Source and trust signals

Warning
01

Issue

Missing AIO trust signals: author, publisher, freshnessDate.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Source and trust signals

Score

50/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Source and trust signals scored 50/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Structured extraction

GEO: Structured extraction scored 63/100 and needs improvement.

4 Warning

Needs attention

GEO: Structured extraction

Warning
01

Issue

Missing or weak extraction signals: summary or key takeaways, FAQ or question-answer section where appropriate, direct definition sentence.

Details

02

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: Structured extraction

Score

63/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.

Result

GEO: Structured extraction scored 63/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Structured data consistency

AIO: Structured data consistency scored 67/100 and needs improvement.

3 Warning

Needs attention

AIO: Structured data consistency

Warning
01

Issue

1 structured-data value(s) were not found in visible page text.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Structured data consistency

Score

67/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Structured data consistency scored 67/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

AEO: Entity and definition clarity scored 76/100 and needs improvement.

3 Warning

Needs attention

AEO: Entity and definition clarity

Warning
01

Issue

No direct definition sentence was detected.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Entity and definition clarity

Score

76/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

AEO: Entity and definition clarity scored 76/100 and needs improvement.

AI DiscoverabilityContent ReadinessEstablished

Structured data

Structured data failed at "Page-relevant schema family".

2 Fail

Needs attention

Structured data

Failed check
01

Issue

The page has specific visible content intent, but structured data does not include a matching primary schema family.

02

Why it matters

Structured data gives agents explicit entities, relationships, and page meaning that are harder to infer reliably from visual layout alone.

Check name

Structured data

Score

83/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Expose machine-readable page entities and relationships through a recognized structured-data syntax.

Result

Structured data failed at "Page-relevant schema family".

Validation steps

  1. Page-relevant schema family

    The page has specific visible content intent, but structured data does not include a matching primary schema family.

Evidence log1 step · 4 lines
Page-relevant schema family [fail]! The page has specific visible content intent, but structured data does not include a matching primary schema family.INFOPage-relevant schema familyINFOInferring specific page intent and comparing it with detected Schema.org typesFAILCheck schema types matching specific visible page intent actual=0 expected="> 0" inferredIntents=["local-business"] expectedTypes=["LocalBusiness"] matchingTypes=[] observedTypes=["Organization","WebSite"]FAILNo primary schema family matches the inferred page intent expectedTypes=["LocalBusiness"] primaryTypes=[]

AI DiscoverabilityContent ReadinessEstablished

Semantic HTML

Semantic HTML is partially implemented.

2 Warning

Needs attention

Semantic HTML

Warning
01

Issue

Semantic HTML is incomplete: 2 form controls missing labels.

Details

02

Why it matters

Semantic HTML gives browsers, assistive technology, search systems, and agents reliable landmarks, headings, controls, form semantics, and image context.

Check name

Semantic HTML

Score

84/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

Expose readable page structure through semantic HTML and accessible controls.

Result

Semantic HTML is partially implemented.

Validation steps

  1. Form labels and autocomplete

    2 user-fillable form controls are missing labels.

Evidence log1 step · 3 lines
Form labels and autocomplete [fail]! 2 user-fillable form controls are missing labels.INFOForm labels and autocompleteFAILCheck form labels and autocomplete evidence actual={"counts":{"formControls":2,"unlabeledFormControls":2,"autocompleteInputs":0,"inputsWithAutocomplete":0,"missingAutocompleteInputs":0},"formLabelCoverage":false} expected="semantic HTML evidence for this step"FAILForm labels and autocomplete failed issue="2 user-fillable form controls are missing labels."

AI DiscoverabilityContent ReadinessEstablished

Organization / WebSite schema

Organization / WebSite schema is partially implemented.

2 Warning

Needs attention

Organization / WebSite schema

Warning
01

Issue

WebSite.publisher is missing.

02

Why it matters

Organization and WebSite schema help agents identify the publisher, canonical site identity, logo, and related profiles for attribution.

Check name

Organization / WebSite schema

Score

85/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

Identify the site owner and website entity in structured data.

Result

Organization / WebSite schema is partially implemented.

Validation steps

  1. WebSite publisher linkage

    WebSite.publisher is missing.

Evidence log1 step · 5 lines
WebSite publisher linkage [fail]! WebSite.publisher is missing.INFOWebSite publisher linkageINFOChecking whether WebSite.publisher points to the Organization entity websiteFormat="json-ld" organizationFormat="json-ld"FAILCheck publisher presence actual=false expected=true publisher={"present":false,"matchesOrganization":false} website={"name":"lululemon","url":"https://shop.lululemon.com/"} organization={"name":"lululemon","url":"https://shop.lululemon.com/"}FAILCheck publisher matches Organization actual=false expected=trueFAILWebSite publisher is missing

Security & TrustSecurity & TrustEstablished

HSTS header

HSTS header has a validation warning at "Review subdomain scope".

2 Warning

Needs attention

HSTS header

Warning
01

Issue

HSTS is valid, but includeSubDomains is absent.

02

Why it matters

HSTS tells browsers to keep using HTTPS after the first secure visit, reducing downgrade, SSL-stripping, and mixed-transport risk for repeat users.

Check name

HSTS header

Score

94/100

Status

warning

Category

Security & Trust

Maturity

Established

Goal

Require HTTPS for repeat browser visits with a valid Strict-Transport-Security policy.

Result

HSTS header has a validation warning at "Review subdomain scope".

Validation steps

  1. Review subdomain scope

    HSTS is valid, but includeSubDomains is absent.

Evidence log1 step · 4 lines
Review subdomain scope [warning]! HSTS is valid, but includeSubDomains is absent.INFOReview subdomain scopeINFOInspect subdomain enforcement scope includeSubDomains=falseWARNCompare includeSubDomains coverage actual="absent" expected="included after subdomains are HTTPS-ready" issue="HSTS is valid, but includeSubDomains is absent."WARNHSTS is valid, but includeSubDomains is absent.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Page experience proxy

AIO: Page experience proxy scored 80/100 and needs improvement.

2 Warning

Needs attention

AIO: Page experience proxy

Warning
01

Issue

47 image(s) are missing width/height attributes.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Page experience proxy

Score

80/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Page experience proxy scored 80/100 and needs improvement.

Agent Ease of UseAPIEstablished

API Catalog

API Catalog is informational for this page.

Informational

Needs attention

API Catalog

Informational
01

Issue

API Catalog is informational for this page.

02

Why it matters

API catalogs help agents find API endpoints, service descriptions, documentation, status resources, auth metadata, and related machine-readable contracts without guessing entry points.

Check name

API Catalog

Score

100/100

Status

informational

Category

API

Maturity

Established

Goal

Publish an API catalog for automated public API discovery using RFC 9727 when this origin exposes public APIs.

Result

API Catalog is informational for this page.

Validation steps

  1. Fetch API catalog

    No API catalog was found and no public API signal was detected.

Evidence log1 step · 4 lines
Fetch API catalog [informational]! No API catalog was found and no public API signal was detected.INFOFetch API catalogINFOFetch /.well-known/api-catalog requestedUrl="https://shop.lululemon.com/.well-known/api-catalog"PASSCompare API catalog HTTP status actual=403 expected="2xx/3xx"WARNNo API catalog was found and no public API signal was detected. status="informational"

AI DiscoverabilityDiscoverabilityEstablished

IndexNow key

IndexNow key is informational for this page.

Informational

Needs attention

IndexNow key

Informational
01

Issue

IndexNow key is informational for this page.

02

Why it matters

IndexNow lets sites notify participating search engines about changed URLs, but ownership verification requires a UTF-8 key file whose filename matches the key.

Check name

IndexNow key

Score

100/100

Status

informational

Category

Discoverability

Maturity

Established

Goal

Verify that IndexNow ownership key placement is detectable when the site advertises it.

Result

IndexNow key is informational for this page.

Validation steps

  1. Find advertised IndexNow key location

    No IndexNow key location was advertised in HTML, Link headers, or robots.txt.

  2. Fetch and validate IndexNow key file

    No discoverable IndexNow key file was found.

Evidence log2 steps · 10 lines
Find advertised IndexNow key location [informational]! No IndexNow key location was advertised in HTML, Link headers, or robots.txt.INFOFind advertised IndexNow key locationINFOLook for IndexNow key hints in HTML, Link headers, and robots.txt supportedHints=["robots.txt IndexNow-Key","rel=indexnow-key","meta name=indexnow-key-location"]PASSCompare advertised key location count actual=0 expected="> 0"WARNNo IndexNow key location was advertised in HTML, Link headers, or robots.txt.Fetch and validate IndexNow key file [informational]! No discoverable IndexNow key file was found.INFOFetch and validate IndexNow key fileINFOLook for IndexNow key hints in HTML, Link headers, and robots.txt supportedHints=["robots.txt IndexNow-Key","rel=indexnow-key","meta name=indexnow-key-location"]PASSCompare advertised key location count actual=0 expected="> 0"INFOFetch each advertised same-origin key file and validate filename/body matchFAILCompare valid IndexNow key file count actual=0 expected="> 0"WARNNo discoverable IndexNow key file was found.

SEOSEOBrowser audit

Image elements do not have `[alt]` attributes

50 Fail

Check name

Image elements do not have `[alt]` attributes

Score

0/100

Status

fail

Device

desktop

Category

SEO

Fix guidance

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. [Learn more about the `alt` attribute](https://dequeuniversity.com/rules/axe/4.12/image-alt).

Evidence
{
  "description": "Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. [Learn more about the `alt` attribute](https://dequeuniversity.com/rules/axe/4.12/image-alt)."
}

SEOSEOBrowser audit

Links are not crawlable

50 Fail

Check name

Links are not crawlable

Score

0/100

Status

fail

Device

desktop

Category

SEO

Fix guidance

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. [Learn how to make links crawlable](https://support.google.com/webmasters/answer/9112205)

Evidence
{
  "description": "Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. [Learn how to make links crawlable](https://support.google.com/webmasters/answer/9112205)"
}

AccessibilityAccessibilityBrowser audit

Certain ARIA roles must be contained by particular parents

11 Fail

Check name

Certain ARIA roles must be contained by particular parents

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Certain ARIA roles must be contained by particular parents

Evidence
{
  "ruleId": "aria-required-parent",
  "impact": "critical",
  "description": "Ensure elements with an ARIA role that require parent roles are contained by them",
  "tags": [
    "cat.aria",
    "wcag2a",
    "wcag131",
    "EN-301-549",
    "EN-9.1.3.1",
    "RGAAv4",
    "RGAA-9.3.1"
  ],
  "affectedNodeCount": 1,
  "nodes": [
    {
      "target": [
        ".main-details_mainDetailWrapper__P9Jqg"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 108
      },
      "failureSummary": "Fix any of the following:\n  Required ARIA parents role not present: menu, menubar, group"
    }
  ]
}

AccessibilityAccessibilityBrowser audit

Images must have alternative text

11 Fail

Check name

Images must have alternative text

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Images must have alternative text

Evidence
{
  "ruleId": "image-alt",
  "impact": "critical",
  "description": "Ensure <img> elements have alternative text or a role of none or presentation",
  "tags": [
    "cat.text-alternatives",
    "wcag2a",
    "wcag111",
    "section508",
    "section508.22.a",
    "TTv5",
    "TT7.a",
    "TT7.b",
    {
      "truncated": true,
      "omittedCount": 5,
      "originalCount": 13
    }
  ],
  "affectedNodeCount": 2,
  "nodes": [
    {
      "target": [
        "div[aria-label=\"Explore Yoga & Pilates\"] > picture > .twoByThree_mediaBlockImage__Doxl9.media-action-block_image__TiZiV[alt=\" \"]"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 161
      },
      "failureSummary": "Fix all of the following:\n  Element has an alt attribute containing only a space character, which is not ignored by all screen readers"
    },
    {
      "target": [
        "div[aria-label=\"Explore Golf\"] > picture > .twoByThree_mediaBlockImage__Doxl9.media-action-block_image__TiZiV[alt=\" \"]"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 161
      },
      "failureSummary": "Fix all of the following:\n  Element has an alt attribute containing only a space character, which is not ignored by all screen readers"
    }
  ]
}

AccessibilityAccessibilityBrowser audit

<li> elements must be contained in a <ul> or <ol>

8 Fail

Check name

<li> elements must be contained in a <ul> or <ol>

Score

25/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

<li> elements must be contained in a <ul> or <ol>

Evidence
{
  "ruleId": "listitem",
  "impact": "serious",
  "description": "Ensure <li> elements are used semantically",
  "tags": [
    "cat.structure",
    "wcag2a",
    "wcag131",
    "EN-301-549",
    "EN-9.1.3.1",
    "RGAAv4",
    "RGAA-9.3.1"
  ],
  "affectedNodeCount": 32,
  "nodes": [
    {
      "target": [
        "#footer-accordion-My\\ Account > .footer_footerListItems__Q1Er8:nth-child(1)"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 42
      },
      "failureSummary": "Fix any of the following:\n  List item parent element has a role that is not role=\"list\""
    },
    {
      "target": [
        "#footer-accordion-My\\ Account > .footer_footerListItems__Q1Er8:nth-child(2)"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 42
      },
      "failureSummary": "Fix any of the following:\n  List item parent element has a role that is not role=\"list\""
    },
    {
      "target": [
        "#footer-accordion-My\\ Account > .footer_footerListItems__Q1Er8:nth-child(3)"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 42
      },
      "failureSummary": "Fix any of the following:\n  List item parent element has a role that is not role=\"list\""
    },
    {
      "target": [
        "#footer-accordion-My\\ Account > .footer_footerListItems__Q1Er8:nth-child(4)"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 42
      },
      "failureSummary": "Fix any of the following:\n  List item parent element has a role that is not role=\"list\""
    },
    {
      "target": [
        "#footer-accordion-My\\ Account > .footer_footerListItems__Q1Er8:nth-child(5)"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 42
      },
      "failureSummary": "Fix any of the following:\n  List item parent element has a role that is not role=\"list\""
    },
    {
      "target": [
        "#footer-accordion-Help > .footer_footerListItems__Q1Er8:nth-child(1)"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 42
      },
      "failureSummary": "Fix any of the following:\n  List item parent element has a role that is not role=\"list\""
    },
    {
      "target": [
        "#footer-accordion-Help > .footer_footerListItems__Q1Er8:nth-child(2)"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 42
      },
      "failureSummary": "Fix any of the following:\n  List item parent element has a role that is not role=\"list\""
    },
    {
      "target": [
        "#footer-accordion-Help > .footer_footerListItems__Q1Er8:nth-child(3)"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 42
      },
      "failureSummary": "Fix any of the following:\n  List item parent element has a role that is not role=\"list\""
    },
    {
      "truncated": true,
      "omittedCount": 2,
      "originalCount": 10
    }
  ]
}

AccessibilityAccessibilityBrowser audit

<ul> and <ol> must only directly contain <li>, <script> or <template> elements

8 Fail

Check name

<ul> and <ol> must only directly contain <li>, <script> or <template> elements

Score

25/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

<ul> and <ol> must only directly contain <li>, <script> or <template> elements

Evidence
{
  "ruleId": "list",
  "impact": "serious",
  "description": "Ensure that lists are structured correctly",
  "tags": [
    "cat.structure",
    "wcag2a",
    "wcag131",
    "EN-301-549",
    "EN-9.1.3.1",
    "RGAAv4",
    "RGAA-9.3.1"
  ],
  "affectedNodeCount": 1,
  "nodes": [
    {
      "target": [
        ".secondary_siteSecondaryList__HD_Sz"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 113
      },
      "failureSummary": "Fix all of the following:\n  List element has direct children that are not allowed: [role=none], div"
    }
  ]
}

AccessibilityAccessibilityBrowser audit

ARIA commands must have an accessible name

8 Fail

Check name

ARIA commands must have an accessible name

Score

25/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

ARIA commands must have an accessible name

Evidence
{
  "ruleId": "aria-command-name",
  "impact": "serious",
  "description": "Ensure every ARIA button, link and menuitem has an accessible name",
  "tags": [
    "cat.aria",
    "wcag2a",
    "wcag412",
    "TTv5",
    "TT6.a",
    "EN-301-549",
    "EN-9.4.1.2",
    "ACT",
    {
      "truncated": true,
      "omittedCount": 2,
      "originalCount": 10
    }
  ],
  "affectedNodeCount": 1,
  "nodes": [
    {
      "target": [
        ".main-details_mainDetailWrapper__P9Jqg"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 108
      },
      "failureSummary": "Fix any of the following:\n  Element does not have text that is visible to screen readers\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"
    }
  ]
}

AccessibilityAccessibilityBrowser audit

Documents must have <title> element to aid in navigation

8 Fail

Check name

Documents must have <title> element to aid in navigation

Score

25/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Documents must have <title> element to aid in navigation

Evidence
{
  "ruleId": "document-title",
  "impact": "serious",
  "description": "Ensure each HTML document contains a non-empty <title> element",
  "tags": [
    "cat.text-alternatives",
    "wcag2a",
    "wcag242",
    "TTv5",
    "TT12.a",
    "EN-301-549",
    "EN-9.2.4.2",
    "ACT",
    {
      "truncated": true,
      "omittedCount": 2,
      "originalCount": 10
    }
  ],
  "affectedNodeCount": 1,
  "nodes": [
    {
      "target": [
        "html"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 36
      },
      "failureSummary": "Fix any of the following:\n  Document does not have a non-empty <title> element"
    }
  ]
}

PerformancePerformanceBrowser audit

Forced reflow

8 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."
}

PerformancePerformanceBrowser audit

Improve image delivery

8 Fail

Check name

Improve image delivery

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 2,044 KiB

Fix guidance

Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/performance/insights/image-delivery)

Evidence
{
  "displayValue": "Est savings of 2,044 KiB",
  "description": "Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/performance/insights/image-delivery)"
}

PerformancePerformanceBrowser audit

LCP request discovery

8 Fail

Check name

LCP request discovery

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

[Optimize LCP](https://developer.chrome.com/docs/performance/insights/lcp-discovery) by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Evidence
{
  "description": "[Optimize LCP](https://developer.chrome.com/docs/performance/insights/lcp-discovery) by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading"
}

PerformancePerformanceBrowser audit

Network dependency tree

8 Fail

Check name

Network dependency tree

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

[Avoid chaining critical requests](https://developer.chrome.com/docs/performance/insights/network-dependency-tree) by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Evidence
{
  "description": "[Avoid chaining critical requests](https://developer.chrome.com/docs/performance/insights/network-dependency-tree) by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load."
}

PerformancePerformanceBrowser audit

Reduce JavaScript execution time

8 Fail

Check name

Reduce JavaScript execution time

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

4.8 s

Fix guidance

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to reduce Javascript execution time](https://developer.chrome.com/docs/lighthouse/performance/bootup-time/).

Evidence
{
  "displayValue": "4.8 s",
  "description": "Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to reduce Javascript execution time](https://developer.chrome.com/docs/lighthouse/performance/bootup-time/).",
  "numericValue": 4797.745999999986
}

PerformancePerformanceBrowser audit

Reduce unused CSS

8 Fail

Check name

Reduce unused CSS

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 62 KiB

Fix guidance

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. [Learn how to reduce unused CSS](https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules/).

Evidence
{
  "displayValue": "Est savings of 62 KiB",
  "description": "Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. [Learn how to reduce unused CSS](https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules/).",
  "numericValue": 40
}

PerformancePerformanceBrowser audit

Reduce unused JavaScript

8 Fail

Check name

Reduce unused JavaScript

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 897 KiB

Fix guidance

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/).

Evidence
{
  "displayValue": "Est savings of 897 KiB",
  "description": "Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/).",
  "numericValue": 40
}

PerformancePerformanceBrowser audit

Render-blocking requests

8 Fail

Check name

Render-blocking requests

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 350 ms

Fix guidance

Requests are blocking the page's initial render, which may delay LCP. [Deferring or inlining](https://developer.chrome.com/docs/performance/insights/render-blocking) can move these network requests out of the critical path.

Evidence
{
  "displayValue": "Est savings of 350 ms",
  "description": "Requests are blocking the page's initial render, which may delay LCP. [Deferring or inlining](https://developer.chrome.com/docs/performance/insights/render-blocking) can move these network requests out of the critical path."
}

AccessibilityAccessibilityBrowser audit

Contentinfo landmark should not be contained in another landmark

5 Warning

Check name

Contentinfo landmark should not be contained in another landmark

Score

55/100

Status

warning

Device

desktop

Category

Accessibility

Fix guidance

Contentinfo landmark should not be contained in another landmark

Evidence
{
  "ruleId": "landmark-contentinfo-is-top-level",
  "impact": "moderate",
  "description": "Ensure the contentinfo landmark is at top level",
  "tags": [
    "cat.semantics",
    "best-practice"
  ],
  "affectedNodeCount": 1,
  "nodes": [
    {
      "target": [
        "#footer"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 102
      },
      "failureSummary": "Fix any of the following:\n  The contentinfo landmark is contained in another landmark."
    }
  ]
}

AccessibilityAccessibilityBrowser audit

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination

5 Warning

Check name

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination

Score

55/100

Status

warning

Device

desktop

Category

Accessibility

Fix guidance

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination

Evidence
{
  "ruleId": "landmark-unique",
  "impact": "moderate",
  "description": "Ensure landmarks are unique",
  "tags": [
    "cat.semantics",
    "best-practice"
  ],
  "affectedNodeCount": 2,
  "nodes": [
    {
      "target": [
        ".one-up_oneUpItem__e3mln[data-lll-pl=\"one-up-component-alp\"][data-testid=\"container\"]:nth-child(6) > .one-up_mediaWrapper__ymw88.one-up_parallaxTimeline__1kqHT > .one-up_overlay__VCqtn.one-up_overlayCenter__gFvs1[aria-label=\"Overlay Components\"]"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 109
      },
      "failureSummary": "Fix any of the following:\n  The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable"
    },
    {
      "target": [
        "#footer-accordion-My\\ Account"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 171
      },
      "failureSummary": "Fix any of the following:\n  The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable"
    }
  ]
}

PerformancePerformanceBrowser audit

Avoid enormous network payloads

4 Warning

Check name

Avoid enormous network payloads

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Total size was 8,043 KiB

Fix guidance

Large network payloads cost users real money and are highly correlated with long load times. [Learn how to reduce payload sizes](https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight/).

Evidence
{
  "displayValue": "Total size was 8,043 KiB",
  "description": "Large network payloads cost users real money and are highly correlated with long load times. [Learn how to reduce payload sizes](https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight/).",
  "numericValue": 8236447
}

PerformancePerformanceBrowser audit

Image elements do not have explicit `width` and `height`

4 Warning

Check name

Image elements do not have explicit `width` and `height`

Score

50/100

Status

warning

Device

desktop

Category

Performance

Fix guidance

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. [Learn how to set image dimensions](https://web.dev/articles/optimize-cls#images_without_dimensions)

Evidence
{
  "description": "Set an explicit width and height on image elements to reduce layout shifts and improve CLS. [Learn how to set image dimensions](https://web.dev/articles/optimize-cls#images_without_dimensions)"
}

PerformancePerformanceBrowser audit

Legacy JavaScript

4 Warning

Check name

Legacy JavaScript

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Est savings of 173 KiB

Fix guidance

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers. [Learn why most sites can deploy ES6+ code without transpiling](https://developer.chrome.com/docs/performance/insights/legacy-javascript)

Evidence
{
  "displayValue": "Est savings of 173 KiB",
  "description": "Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers. [Learn why most sites can deploy ES6+ code without transpiling](https://developer.chrome.com/docs/performance/insights/legacy-javascript)"
}

PerformancePerformanceBrowser audit

Minify JavaScript

4 Warning

Check name

Minify JavaScript

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Est savings of 7 KiB

Fix guidance

Minifying JavaScript files can reduce payload sizes and script parse time. [Learn how to minify JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unminified-javascript/).

Evidence
{
  "displayValue": "Est savings of 7 KiB",
  "description": "Minifying JavaScript files can reduce payload sizes and script parse time. [Learn how to minify JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unminified-javascript/).",
  "numericValue": 0
}

PerformancePerformanceBrowser audit

Loading performance

4 Fail

Check name

Loading performance

Score

51/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

Review the grouped loading performance checks and improve the failing sub-checks listed in evidence.

Evidence
{
  "checks": [
    {
      "id": "interactive",
      "title": "Time to Interactive",
      "score": 8,
      "displayValue": "8.5 s",
      "numericValue": 8529.644343075604
    },
    {
      "id": "first-contentful-paint",
      "title": "First Contentful Paint",
      "score": 90,
      "displayValue": "0.9 s",
      "numericValue": 922.504961007121
    },
    {
      "id": "total-blocking-time",
      "title": "Total Blocking Time",
      "score": 3,
      "displayValue": "1,190 ms",
      "numericValue": 1189.9999999999973
    },
    {
      "id": "max-potential-fid",
      "title": "Max Potential First Input Delay",
      "score": 55,
      "displayValue": "230 ms",
      "numericValue": 232.99999999999818
    },
    {
      "id": "server-response-time",
      "title": "Initial server response time was short",
      "score": 100,
      "displayValue": "Root document took 20 ms",
      "numericValue": 22
    },
    {
      "id": "largest-contentful-paint",
      "title": "Largest Contentful Paint",
      "score": 54,
      "displayValue": "2.3 s",
      "numericValue": 2262.5127568754547
    },
    {
      "id": "network-rtt",
      "title": "Network Round Trip Times",
      "score": 100,
      "displayValue": "50 ms",
      "numericValue": 47.845394999999996
    },
    {
      "id": "speed-index",
      "title": "Speed Index",
      "score": 0,
      "displayValue": "7.3 s",
      "numericValue": 7295.199062854243
    }
  ]
}

AccessibilityAccessibilityBrowser audit

ARIA role should be appropriate for the element

3 Warning

Check name

ARIA role should be appropriate for the element

Score

75/100

Status

warning

Device

desktop

Category

Accessibility

Fix guidance

ARIA role should be appropriate for the element

Evidence
{
  "ruleId": "aria-allowed-role",
  "impact": "minor",
  "description": "Ensure role attribute has an appropriate value for the element",
  "tags": [
    "cat.aria",
    "best-practice"
  ],
  "affectedNodeCount": 5,
  "nodes": [
    {
      "target": [
        "#footer-accordion-My\\ Account"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 171
      },
      "failureSummary": "Fix any of the following:\n  ARIA role region is not allowed for given element"
    },
    {
      "target": [
        "#footer-accordion-Help"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 159
      },
      "failureSummary": "Fix any of the following:\n  ARIA role region is not allowed for given element"
    },
    {
      "target": [
        "#footer-accordion-Legal"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 161
      },
      "failureSummary": "Fix any of the following:\n  ARIA role region is not allowed for given element"
    },
    {
      "target": [
        "#footer-accordion-About\\ Us"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 167
      },
      "failureSummary": "Fix any of the following:\n  ARIA role region is not allowed for given element"
    },
    {
      "target": [
        "#footer-accordion-Contact\\ Us"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 171
      },
      "failureSummary": "Fix any of the following:\n  ARIA role region is not allowed for given element"
    }
  ]
}

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.

Score history

Public scan score over time

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

2 reports
Public score history report links
Scan dateScoreReadinessReport
38/100Level 2, Agent-LimitedView report
50/100Level 3, Bot-AwareCurrent report