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

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability60%Agent Easeof Use58%Security& Trust73%GEO, AIO, AEO73%SEO92%Performance& Accessibility87%
  • AI Discoverability 60 out of 100
  • Agent Ease of Use 58 out of 100
  • Security & Trust 73 out of 100
  • GEO, AIO and AEO 73 out of 100
  • SEO 92 out of 100
  • Performance and Accessibility 87 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Scalability with MariaDB | MariaDB

Scale up with more cores, memory and storage and scale out reads, writes and storage with hundreds of instances with MariaDB.

Next step

Turn this report into a fix workflow

7 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
60
Needs work29108View details
Discoverability
67
Needs work820View details
Content Readiness
71
Needs work2075View details
Bot Access Control
45
Priority fix113View details
Agent Ease of Use
58
Needs work5115View details
API
67
Needs work202
Auth
50
Needs work003
MCP
25
Priority fix012View details
Skill Discovery
50
Needs work005
Agent Commerce
67
Needs work303
GEO, AIO and AEO
73
Needs work1017View details
GEO Readiness
61
Needs work312View details
AIO Readiness
87
Mostly ready402
AEO Readiness
71
Needs work303
SEO
92
Strong910View details
SEO
92
Strong910View details
Security & Trust
73
Needs work1724View details
Security & Trust
73
Needs work1724View details
Performance and Accessibility
87
Mostly ready1942View details
Performance
83
Mostly ready1442View details
Accessibility
94
Strong500

Prioritized recommendations

Issues ranked by score impact

44 items need attention

AI DiscoverabilityDiscoverabilityEstablished

Link headers

Link headers failed at "Find useful Link headers".

100 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 · 12 lines
Find useful Link headers [fail]! No useful agent discovery Link headers were found.INFOFind useful Link headersINFOParse response Link header linkCount=3FAILCompare registered agent-useful relation count actual=0 expected="> 0"FAILCompare community relation count actual=0 expected="accepted as weaker evidence"INFOIgnored non-discovery Link relation rel="https://api.w.org/" url="https://mariadb.com/wp-json/"INFOIgnored non-discovery Link relation rel="alternate" url="https://mariadb.com/wp-json/wp/v2/pages/31797"INFOIgnored non-discovery Link relation rel="shortlink" url="https://mariadb.com/?p=31797"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.

Agent Ease of UseMCPEmerging recommendation

MCP Server Card

MCP Server Card failed at "Discover MCP server card".

50 Fail

Needs attention

MCP Server Card

Failed check
01

Issue

This site claims MCP support or links to MCP metadata, but no MCP server card could be fetched.

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

0/100

Status

fail

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 failed at "Discover MCP server card".

Validation steps

  1. Discover MCP server card

    This site claims MCP support or links to MCP metadata, but no MCP server card could be fetched.

Evidence log1 step · 14 lines
Discover MCP server card [fail]! This site claims MCP support or links to MCP metadata, but no MCP server card could be fetched.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=[]WARNCheck whether page claims MCP support actual=true expected="true only when HTML or Link headers mention MCP" textMatches=["MCP","Model Context Protocol"] headerLinkCount=0INFOTrying to fetch /.well-known/mcp-server-card url="https://mariadb.com/.well-known/mcp-server-card" source="current"FAIL/.well-known/mcp-server-card did not return a usable server card statusCode=404 contentType="text/html; charset=UTF-8"INFOTrying to fetch /.well-known/mcp/server-card.json url="https://mariadb.com/.well-known/mcp/server-card.json" source="transitional"FAIL/.well-known/mcp/server-card.json did not return a usable server card statusCode=404 contentType="text/html; charset=UTF-8"INFOTrying to fetch /.well-known/mcp/server-cards.json url="https://mariadb.com/.well-known/mcp/server-cards.json" source="transitional"FAIL/.well-known/mcp/server-cards.json did not return a usable server card statusCode=404 contentType="text/html; charset=UTF-8"INFOTrying to fetch /mcp.json url="https://mariadb.com/mcp.json" source="transitional"FAIL/mcp.json did not return a usable server card statusCode=404 contentType="text/html; charset=UTF-8"INFOTrying to fetch /.well-known/mcp.json url="https://mariadb.com/.well-known/mcp.json" source="transitional"FAIL/.well-known/mcp.json did not return a usable server card statusCode=404 contentType="text/html; charset=UTF-8"FAILNo MCP server-card candidate was fetched successfully reason="This site claims MCP support or links to MCP metadata, but no MCP server card could be fetched."

Agent Ease of UseAgent CommerceEmerging recommendation

MPP - Machine Payments Protocol

MPP - Machine Payments Protocol has a validation warning at "Fetch canonical MPP discovery".

33 Warning

Needs attention

MPP - Machine Payments Protocol

Warning
01

Issue

MPP appears to be claimed or hinted, but canonical /openapi.json discovery was not found.

02

Why it matters

MPP lets agents find paid API operations through OpenAPI metadata and recognize HTTP payment challenges without scraping human checkout flows or guessing payable paths.

Check name

MPP - Machine Payments Protocol

Score

67/100

Status

warning

Category

Agent Commerce

Maturity

Emerging recommendation

Goal

Expose mpp.dev-style discovery and HTTP payment challenges so agents can discover payable resources and payment terms safely.

Result

MPP - Machine Payments Protocol has a validation warning at "Fetch canonical MPP discovery".

Validation steps

  1. Fetch canonical MPP discovery

    MPP appears to be claimed or hinted, but canonical /openapi.json discovery was not found.

  2. Find explicitly documented payable routes

    MPP was claimed or hinted, but no explicit safe GET route was available to probe.

  3. Validate safe runtime MPP challenge

    No explicit safe MPP route was available to probe; the check did not guess arbitrary paid paths.

Evidence log3 steps · 14 lines
Fetch canonical MPP discovery [warning]! MPP appears to be claimed or hinted, but canonical /openapi.json discovery was not found.INFOFetch canonical MPP discovery status="warning"INFOFetch /openapi.json statusCode=404 contentType="text/html; charset=UTF-8"WARNCheck canonical MPP discovery response actual=false expected=true found=false parsed=falseWARNCount payable OpenAPI operations actual=0 expected="> 0 when MPP is claimed"WARNMPP appears to be claimed or hinted, but canonical /openapi.json discovery was not found.Find explicitly documented payable routes [warning]! MPP was claimed or hinted, but no explicit safe GET route was available to probe.INFOFind explicitly documented payable routes status="warning"INFOCollect safe GET probe candidates from OpenAPI and public metadata candidateCount=0WARNCheck explicit payable route candidates actual=0 expected="> 0 when MPP is claimed"INFOReview metadata sources for route hints metadata=[{"path":"/llms.txt","statusCode":200,"contentType":"text/plain; charset=UTF-8","found":true,"markers":["MPP"],"candidateCount":0},{"path":"/llms-full.txt","statusCode":404,"contentType":"text/html; charset=UTF-8","found":false,"markers":[],"candidateCount":0}]WARNMPP was claimed or hinted, but no explicit safe GET route was available to probe.Validate safe runtime MPP challenge [warning]! No explicit safe MPP route was available to probe; the check did not guess arbitrary paid paths.INFOValidate safe runtime MPP challenge status="warning"INFOSafely probe documented GET candidates without sending payment credentials checkedCount=0WARNCheck runtime MPP payment challenge actual="none" expected="HTTP 402 with WWW-Authenticate: Payment" best={}WARNNo explicit safe MPP route was available to probe; the check did not guess arbitrary paid 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.
    • Conventional WebMCP manifest paths were checked but did not return a valid manifest.
  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 · 32 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."WARNWebMCP operability warning warning="Conventional WebMCP manifest paths were checked but did not return a valid manifest."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://mariadb.com/.well-known/webmcp.json" statusCode=404 contentType="text/html; charset=UTF-8"INFOWebMCP manifest candidate checked source="path" path="/webmcp.json" url="https://mariadb.com/webmcp.json" statusCode=404 contentType="text/html; charset=UTF-8"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="accelerometer=(), autoplay=(), camera=(), cross-origin-isolated=(), display-capture=(), encrypted-media=(), fullscreen=(), geolocation=(), gyroscope=(), keyboard-map=(), magnetometer=(), microphone=(), midi=(), payment=(), picture-in-picture=(), publickey-credentials-get=(), screen-wake-lock=(), sync-xhr=(self), usb=(), web-share=(), xr-spatial-tracking=(), clipboard-read=(self), clipboard-write=(self), gamepad=(), hid=(), idle-detection=(), interest-cohort=(), serial=(), unload=(), microphone=(self)" 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"

AI DiscoverabilityBot Access ControlEstablished

AI bot rules in robots.txt

AI bot rules in robots.txt failed at "Classify AI crawler rules".

17 Fail

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

No explicit User-agent rules were found for major AI crawler tokens.

02

Why it matters

AI crawler product tokens have different meanings. Explicit robots.txt groups make training, search, and retrieval access policy auditable for compliant crawler operators.

Check name

AI bot rules in robots.txt

Score

31/100

Status

fail

Category

Bot Access Control

Maturity

Established

Goal

Declare deliberate robots.txt rules for major AI training, AI search, user-triggered, and dataset crawlers.

Result

AI bot rules in robots.txt failed at "Classify AI crawler rules".

Validation steps

  1. Classify AI crawler rules

    No explicit User-agent rules were found for major AI crawler tokens.

Evidence log1 step · 6 lines
Classify AI crawler rules [fail]! No explicit User-agent rules were found for major AI crawler tokens.INFOClassify AI crawler rulesINFOParsing User-agent groups and Allow/Disallow records for known AI crawler tokens evaluatedPath="/"INFOEvaluating exact User-agent matches before wildcard fallback exactAiPolicyCount=0 totalCrawlerTokens=18FAILNo explicit AI crawler User-agent groups were found examplesExpected=["GPTBot","OAI-SearchBot","ClaudeBot","Google-Extended","CCBot"]FAILCompare explicit AI crawler coverage actual=0 expected="> 0 explicit non-search AI crawler policies" missingTokens=["GPTBot","OAI-SearchBot","ChatGPT-User","ClaudeBot","Claude-SearchBot","Claude-User","Google-Extended","Applebot-Extended","Amazonbot","Amzn-SearchBot","Amzn-User","PerplexityBot"]INFOResolved effective root-path policy for crawler tokens blocked=0 allowed=21 unspecified=0

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.

Agent Ease of UseAuthEstablished

OAuth / OIDC discovery

OAuth / OIDC discovery has a validation warning at "Detect OAuth/OIDC applicability".

17 Warning

Needs attention

OAuth / OIDC discovery

Warning
01

Issue

Generic authentication signals were found, but no OAuth/OIDC discovery signal was detected.

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

50/100

Status

warning

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 has a validation warning at "Detect OAuth/OIDC applicability".

Validation steps

  1. Detect OAuth/OIDC applicability

    Generic authentication signals were found, but no OAuth/OIDC discovery signal was detected.

Evidence log1 step · 4 lines
Detect OAuth/OIDC applicability [warning]! Generic authentication signals were found, but no OAuth/OIDC discovery signal was detected.INFODetect OAuth/OIDC applicabilityINFOInspecting homepage, headers, and known auth/API signals for OAuth or OIDC claims applies=false signalsCount=0 genericAuthSignalsCount=3 checkedCount=2WARNCheck OAuth/OIDC applicability signal actual=false expected="true when metadata exists or OAuth/OIDC is claimed" checked=[{"path":"/.well-known/openid-configuration","statusCode":404,"contentType":"text/html; charset=UTF-8","length":1608126},{"path":"/.well-known/oauth-authorization-server","statusCode":404,"contentType":"text/html; charset=UTF-8","length":1608126}]WARNDetect OAuth/OIDC applicability completed with warnings issue="Generic authentication signals were found, but no OAuth/OIDC discovery signal was detected."

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=2WARNCheck protected-resource metadata applicability actual=false expected="true when RFC 9728 metadata exists or support is claimed" checked=[{"url":"https://mariadb.com/.well-known/oauth-protected-resource","path":"/.well-known/oauth-protected-resource","source":"root-well-known","resourceIdentifier":"https://mariadb.com","statusCode":404,"contentType":"text/html; charset=UTF-8","length":1608126},{"url":"https://mariadb.com/.well-known/oauth-protected-resource/database-topics/scalability/","path":"/.well-known/oauth-protected-resource/database-topics/scalability/","source":"final-url-path","resourceIdentifier":"https://mariadb.com/database-topics/scalability/","statusCode":404,"contentType":"text/html; charset=UTF-8","length":1608126}]WARNDetect protected-resource applicability completed with warnings issue="Generic authentication signals were found, but no OAuth Protected Resource metadata signal was detected."

Agent Ease of UseAPIEstablished

API Catalog

API Catalog has a validation warning at "Fetch API catalog".

17 Warning

Needs attention

API Catalog

Warning
01

Issue

This origin appears to publish or claim public APIs, but no RFC 9727 API catalog was found.

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

67/100

Status

warning

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 has a validation warning at "Fetch API catalog".

Validation steps

  1. Fetch API catalog

    This origin appears to publish or claim public APIs, but no RFC 9727 API catalog was found.

Evidence log1 step · 4 lines
Fetch API catalog [warning]! This origin appears to publish or claim public APIs, but no RFC 9727 API catalog was found.INFOFetch API catalogINFOFetch /.well-known/api-catalog requestedUrl="https://mariadb.com/.well-known/api-catalog"WARNCompare API catalog HTTP status actual=404 expected="2xx/3xx"WARNThis origin appears to publish or claim public APIs, but no RFC 9727 API catalog was found. status="warning"

Agent Ease of UseAPIEstablished

OpenAPI discovery

OpenAPI discovery has a validation warning at "Discover OpenAPI document".

17 Warning

Needs attention

OpenAPI discovery

Warning
01

Issue

The site appears to publish or document a public API, but no OpenAPI or Swagger document was found.

02

Why it matters

OpenAPI documents let agents understand operations, schemas, authentication, servers, and request/response formats before calling an API.

Check name

OpenAPI discovery

Score

67/100

Status

warning

Category

API

Maturity

Established

Goal

Publish a valid OpenAPI or Swagger document for public API discovery when this origin exposes public APIs.

Result

OpenAPI discovery has a validation warning at "Discover OpenAPI document".

Validation steps

  1. Discover OpenAPI document

    The site appears to publish or document a public API, but no OpenAPI or Swagger document was found.

Evidence log1 step · 16 lines
Discover OpenAPI document [warning]! The site appears to publish or document a public API, but no OpenAPI or Swagger document was found.INFODiscover OpenAPI document status="warning"INFOBuild OpenAPI candidate list conventionalPaths=19 candidateCount=19 sources={"conventional-path":19}INFOFetch OpenAPI candidate path="/openapi.json" source="conventional-path" statusCode=404 contentType="text/html; charset=UTF-8"INFOFetch OpenAPI candidate path="/openapi.yaml" source="conventional-path" statusCode=403 contentType="text/html; charset=UTF-8"INFOFetch OpenAPI candidate path="/swagger.json" source="conventional-path" statusCode=404 contentType="text/html; charset=UTF-8"INFOFetch OpenAPI candidate path="/swagger.yaml" source="conventional-path" statusCode=403 contentType="text/html; charset=UTF-8"INFOFetch OpenAPI candidate path="/api/openapi.json" source="conventional-path" statusCode=404 contentType="text/html; charset=UTF-8"INFOFetch OpenAPI candidate path="/api/openapi.yaml" source="conventional-path" statusCode=403 contentType="text/html; charset=UTF-8"INFOFetch OpenAPI candidate path="/api/swagger.json" source="conventional-path" statusCode=404 contentType="text/html; charset=UTF-8"INFOFetch OpenAPI candidate path="/api/swagger.yaml" source="conventional-path" statusCode=403 contentType="text/html; charset=UTF-8"INFOFetch OpenAPI candidate path="/docs/openapi.json" source="conventional-path" statusCode=404 contentType="text/html; charset=utf-8"INFOFetch OpenAPI candidate path="/docs/openapi.yaml" source="conventional-path" statusCode=404 contentType="text/html; charset=utf-8"INFOFetch OpenAPI candidate path="/api-docs" source="conventional-path" statusCode=404 contentType="text/html; charset=UTF-8"INFOFetch OpenAPI candidate path="/v3/api-docs" source="conventional-path" statusCode=404 contentType="text/html; charset=UTF-8"WARNSelect a usable OpenAPI candidate actual="none" expected="same-origin candidate with a parseable OpenAPI or Swagger document"WARNThe site appears to publish or document a public API, but no OpenAPI or Swagger document was found.

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Find enforcing CSP delivery".

15 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

Only Content-Security-Policy-Report-Only is present; report-only policies are not enforced.

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

40/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 "Find enforcing CSP delivery".

Validation steps

  1. Find enforcing CSP delivery

    Only Content-Security-Policy-Report-Only is present; report-only policies are not enforced.

Evidence log1 step · 4 lines
Find enforcing CSP delivery [fail]! Only Content-Security-Policy-Report-Only is present; report-only policies are not enforced.INFOFind enforcing CSP deliveryINFORead CSP delivery headers enforcingHeader="missing" reportOnlyHeader="script-src 'unsafe-inline' 'unsafe-eval'; report-uri https://csp-reporting.cloudflare.com/cdn-cgi/script_monitor/report?m=RMInNjR57Qi_bkOtKlbxHYSB1QPgMN8Dauh0mPUgKQQ-1781468526.351547-1.0.1.1-xo7Y0irBBxyTe3PEP6sgWT5hSYv6e3474kjEeZVUrbKbeV438PlO3ZSnjB747WUJshnQGAjHbo00lBwhRj1NfIZPcEnJIRCmQ8l67K7evI8OskX9kZsHa3kEbL3iLsYg3_tKTmeSVKgCsoHm0KMMD4r.tDwZbinXo0CzjSfGX0E; report-to cf-csp-endpoint" metaPolicyCount=0 legacyHeadersPresent=[]FAILRequire enforcing Content-Security-Policy header actual="missing" expected="present" issue="Only Content-Security-Policy-Report-Only is present; report-only policies are not enforced."FAILOnly Content-Security-Policy-Report-Only is present; report-only policies are not enforced.

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=404 contentType="text/html; charset=UTF-8"WARNA2A candidate path did not return a usable card path="/.well-known/agent.json" statusCode=404 contentType="text/html; charset=UTF-8"WARNA2A candidate path did not return a usable card path="/agent-card.json" statusCode=404 contentType="text/html; charset=UTF-8"WARNA2A candidate path did not return a usable card path="/.well-known/a2a/agent-card.json" statusCode=404 contentType="text/html; charset=UTF-8"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://mariadb.com/.well-known/agent-skills/index.json" statusCode=404WARNAgent Skills index candidate was not usable path="/.well-known/skills/index.json" url="https://mariadb.com/.well-known/skills/index.json" statusCode=404WARNNo 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=404 contentType="text/html; charset=UTF-8"WARNagents.json candidate path did not return a usable contract path="/agents.json" statusCode=404 contentType="text/html; charset=UTF-8"WARNNo agents.json candidate was selectedWARNNo Wildcard-style agents.json file was found.

AI DiscoverabilityBot Access ControlInformational

Content Signal

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

13 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 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 · 23 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="mariadb.com" labels=["_index._agents.mariadb.com","_a2a._agents.mariadb.com"] claimedOnPage=falseWARNDNS query returned no DNS-AID answers name="_index._agents.mariadb.com" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.mariadb.com" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.mariadb.com" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _index._agents.mariadb.com"WARNDNS query returned no DNS-AID answers name="_a2a._agents.mariadb.com" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.mariadb.com" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.mariadb.com" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _a2a._agents.mariadb.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.mariadb.com" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.mariadb.com" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.mariadb.com" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.mariadb.com" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.mariadb.com" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.mariadb.com" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.mariadb.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.mariadb.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="mariadb.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNDNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.

AI DiscoverabilityBot Access ControlEmerging recommendation

RSL license signal

No RSL declarations were found.

13 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.

13 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=404 expected="2xx with JSON array when origin-level TDMRep is published" contentType="text/html; charset=UTF-8" length=1608126WARNNo TDMRep declaration was found at /.well-known/tdmrep.json. 

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Citable passages

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

12 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

0/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 0/100 and needs a fix.

Security & TrustSecurity & TrustEstablished

Referrer-Policy

Referrer-Policy failed at "Parse policy tokens".

10 Fail

Needs attention

Referrer-Policy

Failed check
01

Issue

Referrer-Policy has no recognized policy token.

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

60/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 "Parse policy tokens".

Validation steps

  1. Parse policy tokens

    Referrer-Policy has no recognized policy token.

  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
Parse policy tokens [fail]! Referrer-Policy has no recognized policy token.INFOParse policy tokensINFOParse Referrer-Policy tokens tokens=["no-referrer strict-origin-when-cross-origin"] recognizedTokens=[] unknownTokens=["no-referrer strict-origin-when-cross-origin"]FAILSelect browser-effective policy token actual="none recognized" expected="last recognized unquoted policy token" hasFallbackValues=false quotedOrMalformed=false issue="Referrer-Policy has no recognized policy token."FAILReferrer-Policy has no recognized policy token.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=38 sameOriginCount=17 htmlDocumentCount=2WARNCompare observed Referrer-Policy coverage actual={"missingPolicyCount":1,"unsafeOrInvalidPolicyCount":1,"weakPolicyCount":0,"affected":[{"url":"https://mariadb.com/wp-content/uploads/2025/12/hero-mask.png","status":404,"resourceType":"image","contentType":"text/html; charset=UTF-8","referrerPolicy":null,"classification":"invalid"},{"url":"https://mariadb.com/database-topics/scalability/","status":200,"resourceType":"document","contentType":"text/html; charset=UTF-8","referrerPolicy":"no-referrer strict-origin-when-cross-origin","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 DiscoverabilityContent ReadinessEstablished

Organization / WebSite schema

Organization / WebSite schema is partially implemented.

9 Warning

Needs attention

Organization / WebSite schema

Warning
01

Issue

No Organization or Organization subtype was found in Schema.org structured data. Organization schema is missing logo and sameAs or public contact evidence.

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

45/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. Organization entity

    No Organization or Organization subtype was found in Schema.org structured data.

  2. Identity fields

    Missing identity field(s): Organization.name, Organization.url.

  3. WebSite publisher linkage

    WebSite.publisher exists but does not clearly match the Organization entity.

  4. Organization trust fields

    Organization schema is missing logo and sameAs or public contact evidence.

Evidence log4 steps · 19 lines
Organization entity [fail]! No Organization or Organization subtype was found in Schema.org structured data.INFOOrganization entityINFOLooking for Organization or Organization subtype in structured data observedTypes=[]FAILCheck Organization entity presence actual=false expected=true fields=[{"name":"Organization.@type","present":false},{"name":"Organization.@id","present":false},{"name":"Organization.name","present":false},{"name":"Organization.url","present":false},{"name":"Organization.logo","present":false},{"name":"Organization.sameAs","present":false}]FAILOrganization entity is missingIdentity fields [warning]! Missing identity field(s): Organization.name, Organization.url.INFOIdentity fieldsINFOChecking Organization and WebSite name/url fields websiteFormat="json-ld"WARNCheck required identity fields actual=2 expected=4 missing=["Organization.name","Organization.url"] organizationFields=[{"name":"Organization.@type","present":false},{"name":"Organization.@id","present":false},{"name":"Organization.name","present":false},{"name":"Organization.url","present":false},{"name":"Organization.logo","present":false},{"name":"Organization.sameAs","present":false}] websiteFields=[{"name":"WebSite.@type","present":true,"value":"WebSite","format":"json-ld"},{"name":"WebSite.@id","present":true,"value":"https://mariadb.com/#/schema/WebSite","format":"json-ld"},{"name":"WebSite.name","present":true,"value":"MariaDB","format":"json-ld"},{"name":"WebSite.url","present":true,"value":"https://mariadb.com/","format":"json-ld"},{"name":"WebSite.publisher.@id","present":true,"value":"https://mariadb.com/#/schema/Organization","format":"json-ld"},{"name":"WebSite.publisher.name","present":true,"value":"MariaDB","format":"json-ld"},{"name":"WebSite.publisher.url","present":true,"value":"https://mariadb.com/","format":"json-ld"}]WARNCheck identity URLs match scanned origin actual={"organizationUrlMatchesOrigin":false,"websiteUrlMatchesOrigin":true} expected={"organizationUrlMatchesOrigin":true,"websiteUrlMatchesOrigin":true}WARNIdentity fields are partially complete missing=["Organization.name","Organization.url"]WebSite publisher linkage [warning]! WebSite.publisher exists but does not clearly match the Organization entity.INFOWebSite publisher linkageINFOChecking whether WebSite.publisher points to the Organization entity websiteFormat="json-ld"PASSCheck publisher presence actual=true expected=true publisher={"present":true,"id":"https://mariadb.com/#/schema/Organization","name":"MariaDB","url":"https://mariadb.com/","matchesOrganization":false} website={"id":"https://mariadb.com/#/schema/WebSite","name":"MariaDB","url":"https://mariadb.com/"} organization={}WARNCheck publisher matches Organization actual=false expected=trueWARNWebSite publisher exists but does not clearly match OrganizationOrganization trust fields [fail]! Organization schema is missing logo and sameAs or public contact evidence.INFOOrganization trust fieldsINFOChecking logo, sameAs, and public contact evidence FAILCheck logo presence actual=false expected=true fields=[{"name":"Organization.logo","present":false},{"name":"Organization.sameAs","present":false},{"name":"Organization.contactPoint","present":false},{"name":"Organization.telephone","present":false},{"name":"Organization.email","present":false},{"name":"Organization.address","present":false}]FAILCheck sameAs or contact evidence actual=0 expected=">= 1" sameAsCount=0 contactSignalCount=0 fields=[{"name":"Organization.logo","present":false},{"name":"Organization.sameAs","present":false},{"name":"Organization.contactPoint","present":false},{"name":"Organization.telephone","present":false},{"name":"Organization.email","present":false},{"name":"Organization.address","present":false}]FAILOrganization trust fields are missing

AI DiscoverabilityContent ReadinessEstablished

Semantic HTML

Semantic HTML is partially implemented.

8 Warning

Needs attention

Semantic HTML

Warning
01

Issue

Semantic HTML is incomplete: skipped or empty headings; 1 links missing accessible names; 79 controls missing accessible names.

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

54/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. Heading structure

    Headings skip levels or include empty heading elements.

  2. Links

    1 links are missing accessible names.

  3. Buttons and interactive controls

    79 button controls are missing accessible names.

Evidence log3 steps · 9 lines
Heading structure [fail]! Headings skip levels or include empty heading elements.INFOHeading structureFAILCheck heading structure evidence actual={"counts":{"h1":1,"visibleH1":1,"headings":10,"emptyHeadings":0},"meaningfulH1":true} expected="semantic HTML evidence for this step"FAILHeading structure failed issue="Headings skip levels or include empty heading elements."Links [fail]! 1 links are missing accessible names.INFOLinksFAILCheck links evidence actual={"counts":{"links":172,"inaccessibleLinks":1,"nonCrawlableLinks":0,"genericLinks":0},"accessibleLinks":false} expected="semantic HTML evidence for this step"FAILLinks failed issue="1 links are missing accessible names."Buttons and interactive controls [fail]! 79 button controls are missing accessible names.INFOButtons and interactive controlsFAILCheck buttons and interactive controls evidence actual={"counts":{"buttons":80,"inaccessibleButtons":79},"accessibleButtons":false} expected="links, buttons, and form controls expose accessible names"FAILButtons and interactive controls failed issue="79 button controls are missing accessible names."

Security & TrustSecurity & TrustEstablished

Frame protection

Frame protection has a validation warning at "Validate CSP frame-ancestors".

7 Warning

Needs attention

Frame protection

Warning
01

Issue

Frame protection relies only on X-Frame-Options; CSP frame-ancestors is the modern control.

02

Why it matters

Frame protection blocks hostile sites from embedding pages in deceptive frames, reducing clickjacking and UI redressing risk.

Check name

Frame protection

Score

72/100

Status

warning

Category

Security & Trust

Maturity

Established

Goal

Prevent unwanted framing with an enforcing CSP frame-ancestors directive or a valid X-Frame-Options fallback.

Result

Frame protection has a validation warning at "Validate CSP frame-ancestors".

Validation steps

  1. Validate CSP frame-ancestors

    Frame protection relies only on X-Frame-Options; CSP frame-ancestors is the modern control.

  2. Review observed browser responses

    One or more same-origin HTML documents observed by Chrome did not emit valid frame protection.

Evidence log2 steps · 8 lines
Validate CSP frame-ancestors [warning]! Frame protection relies only on X-Frame-Options; CSP frame-ancestors is the modern control.INFOValidate CSP frame-ancestorsINFORead CSP frame-ancestors signals enforcingHeaderPresent=false reportOnlyHeaderPresent=true metaFrameAncestors=false policyCount=0 duplicateDirectives=[]WARNCompare effective frame-ancestors directive actual="missing" expected="valid restrictive enforcing frame-ancestors" issue="Frame protection relies only on X-Frame-Options; CSP frame-ancestors is the modern control."WARNFrame protection relies only on X-Frame-Options; CSP frame-ancestors is the modern control.Review observed browser responses [warning]! One or more same-origin HTML documents observed by Chrome did not emit valid frame protection.INFOReview observed browser responsesINFOSample Chrome-observed same-origin responses observedResponseCount=38 sameOriginCount=17 htmlDocumentCount=2WARNCompare observed HTML frame protection actual={"missingOrInvalidFrameProtectionCount":1,"broadFrameAncestorsCount":0,"affected":[{"url":"https://mariadb.com/wp-content/uploads/2025/12/hero-mask.png","status":404,"resourceType":"image","contentType":"text/html; charset=UTF-8","contentSecurityPolicy":null,"contentSecurityPolicyReportOnly":null}]} expected="0 missing/invalid or broad same-origin HTML responses" issue="One or more same-origin HTML documents observed by Chrome did not emit valid frame protection."WARNOne or more same-origin HTML documents observed by Chrome did not emit valid frame protection.

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, freshnessDate, sameAs.

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 67/100 and needs improvement.

5 Warning

Needs attention

AIO: Source and trust signals

Warning
01

Issue

Missing AIO trust signals: author, 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

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: Source and trust signals scored 67/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first passages

AEO: Answer-first passages scored 60/100 and needs improvement.

5 Warning

Needs attention

AEO: Answer-first passages

Warning
01

Issue

2 section(s) bury or omit a concise opening answer.

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

60/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: Answer-first passages scored 60/100 and needs improvement.

AI DiscoverabilityContent ReadinessEmerging recommendation

llms.txt

llms.txt has a validation warning at "Score llms.txt structure and usefulness".

4 Warning

Needs attention

llms.txt

Warning
01

Issue

llms.txt is present, but its structure or link curation is weaker than the emerging proposal and production examples.

Details

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

76/100

Status

warning

Category

Content Readiness

Maturity

Emerging recommendation

Goal

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

Result

llms.txt has a validation warning at "Score llms.txt structure and usefulness".

Validation steps

  1. Score llms.txt structure and usefulness

    llms.txt is present, but its structure or link curation is weaker than the emerging proposal and production examples.

    Findings
    • Missing a blockquote summary. The llms.txt proposal recommends a concise blockquote after the H1.
  2. Probe sampled linked resources

    Some sampled llms.txt links were broken, redirected unexpectedly, or did not return clearly agent-readable content.

    Findings
    • 2/25 probed links were broken or unreachable.
    • 2/25 probed links did not look agent-readable.
  3. Inspect optional llms-full.txt

    Passed.

Evidence log3 steps · 16 lines
Score llms.txt structure and usefulness [warning]! llms.txt is present, but its structure or link curation is weaker than the emerging proposal and production examples.INFOScore llms.txt structure and usefulnessINFOChecking recommended summary, sections, link labels, agent-friendly links, duplicates, and unsafe targetsWARNCheck blockquote summary is present actual=false expected=truePASSCheck H2 section count actual=8 expected="> 0"PASSCheck Markdown-formatted links actual=46 expected="> 0"PASSCheck unsafe/private link count actual=0 expected=0WARNllms.txt structure-quality validation completed with warnings reason="llms.txt is present, but its structure or link curation is weaker than the emerging proposal and production examples."Probe sampled linked resources [warning]! Some sampled llms.txt links were broken, redirected unexpectedly, or did not return clearly agent-readable content.INFOProbe sampled linked resourcesINFOSelecting safe, useful links for bounded probing selectedCount=25PASSCheck probed links were attempted actual=25 expected="> 0"WARNCheck broken probed link count actual=2 expected=0PASSCheck agent-readable probed links actual=23 expected="> 0"WARNLinked resource probe validation completed with warnings reason="Some sampled llms.txt links were broken, redirected unexpectedly, or did not return clearly agent-readable content."Inspect optional llms-full.txt [informational]INFOInspect optional llms-full.txtINFOTrying to fetch /llms-full.txt url="https://mariadb.com/llms-full.txt"SKIP/llms-full.txt is not present statusCode=404

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Source and trust signals

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

4 Warning

Needs attention

GEO: Source and trust signals

Warning
01

Issue

Missing source or trust signals: freshnessDate, entityLinks.

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

67/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 67/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question and answer structure

AEO: Question and answer structure scored 68/100 and needs improvement.

4 Warning

Needs attention

AEO: Question and answer structure

Warning
01

Issue

Heading structure issues were 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: Question and answer structure

Score

68/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: Question and answer structure scored 68/100 and needs improvement.

AI DiscoverabilityContent ReadinessEstablished

Markdown negotiation

Markdown negotiation is partially implemented.

4 Warning

Needs attention

Markdown negotiation

Warning
01

Issue

Markdown negotiation is missing or incomplete.

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

78/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

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

Result

Markdown negotiation is partially implemented.

Validation steps

  1. Advertised Markdown alternate

    Advertise dedicated Markdown URLs with Link: <url>; rel="alternate"; type="text/markdown" or an HTML link rel=alternate tag.

  2. Conventional .md mirror

    If a .md mirror is intentional, advertise it with rel=alternate and type=text/markdown.

Evidence log2 steps · 6 lines
Advertised Markdown alternate [fail]INFOAdvertised Markdown alternateFAILCheck advertised Markdown alternate candidates actual=1 expected="> 0 when HTML advertises a Markdown alternate" advertisedUrls=["https://mariadb.com/database-topics/scalability.md"] candidateCount=0FAILAdvertised Markdown alternate failed Conventional .md mirror [informational]INFOConventional .md mirrorINFOCheck conventional Markdown mirror candidates actual=0 expected="> 0 when a conventional mirror is discoverable" conventionalUrls=[] candidateCount=0PASSConventional .md mirror recorded for context status="informational"

AI DiscoverabilityContent ReadinessEstablished

Author attribution

Author attribution is partially implemented.

3 Warning

Needs attention

Author attribution

Warning
01

Issue

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

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

80/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.

Evidence log1 step · 4 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=1 namedContributors=1 authors=[] publishers=[{"role":"publisher","name":"MariaDB","type":"Organization","id":"https://mariadb.com/#/schema/Organization","url":"https://mariadb.com/","sameAs":[],"format":"json-ld","mergedName":false}] formats=["json-ld"]WARNSchema.org attribution is incomplete or fallback-only authorCount=0 publisherCount=1 authors=[] publishers=[{"role":"publisher","name":"MariaDB","type":"Organization","id":"https://mariadb.com/#/schema/Organization","url":"https://mariadb.com/","sameAs":[],"format":"json-ld","mergedName":false}]

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Structured extraction

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

3 Warning

Needs attention

GEO: Structured extraction

Warning
01

Issue

Missing or weak extraction signals: clean heading hierarchy, summary or key takeaways.

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

75/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 75/100 and needs improvement.

AI DiscoverabilityContent ReadinessEstablished

Structured data

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

3 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=["commerce","software"] expectedTypes=["Product","ProductGroup","Offer","AggregateOffer","Service","SoftwareApplication","WebApplication","MobileApplication"] matchingTypes=[] observedTypes=["WebPage","WebSite"]FAILNo primary schema family matches the inferred page intent expectedTypes=["Product","ProductGroup","Offer","AggregateOffer","Service","SoftwareApplication","WebApplication","MobileApplication"] primaryTypes=[]

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Structured data consistency

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

2 Warning

Needs attention

AIO: Structured data consistency

Warning
01

Issue

2 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

88/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 88/100 and needs improvement.

Security & TrustSecurity & TrustEstablished

HSTS header

HSTS header has a validation warning at "Review preload opt-in".

1 Warning

Needs attention

HSTS header

Warning
01

Issue

preload is present; verify hstspreload.org operational requirements before submission.

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

95/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 preload opt-in".

Validation steps

  1. Review preload opt-in

    preload is present; verify hstspreload.org operational requirements before submission.

Evidence log1 step · 4 lines
Review preload opt-in [warning]! preload is present; verify hstspreload.org operational requirements before submission.INFOReview preload opt-inINFOInspect preload opt-in preload=true includeSubDomains=true maxAge=63072000WARNCompare header-level preload requirements actual="eligible by header" expected="preload + includeSubDomains + max-age >= 31536000" issue="preload is present; verify hstspreload.org operational requirements before submission."WARNpreload is present; verify hstspreload.org operational requirements before submission.

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.

Performance and AccessibilityBest PracticesBrowser audit

Browser errors were logged to the console

100 Fail

Check name

Browser errors were logged to the console

Score

0/100

Status

fail

Device

desktop

Category

Best Practices

Fix guidance

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. [Learn more about this errors in console diagnostic audit](https://developer.chrome.com/docs/lighthouse/best-practices/errors-in-console/)

Evidence
{
  "description": "Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. [Learn more about this errors in console diagnostic audit](https://developer.chrome.com/docs/lighthouse/best-practices/errors-in-console/)"
}

SEOSEOBrowser audit

robots.txt is not valid

100 Fail

Check name

robots.txt is not valid

Score

0/100

Status

fail

Device

desktop

Category

SEO

Estimated savings

1 error found

Fix guidance

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. [Learn more about robots.txt](https://developer.chrome.com/docs/lighthouse/seo/invalid-robots-txt/).

Evidence
{
  "description": "If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. [Learn more about robots.txt](https://developer.chrome.com/docs/lighthouse/seo/invalid-robots-txt/).",
  "displayValue": "1 error found"
}

Performance and AccessibilityPerformanceBrowser audit

Network dependency tree

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

Performance and AccessibilityPerformanceBrowser audit

Render-blocking requests

17 Fail

Check name

Render-blocking requests

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 310 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
{
  "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.",
  "displayValue": "Est savings of 310 ms"
}

Performance and AccessibilityPerformanceBrowser audit

Use efficient cache lifetimes

17 Fail

Check name

Use efficient cache lifetimes

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 348 KiB

Fix guidance

A long cache lifetime can speed up repeat visits to your page. [Learn more about caching](https://developer.chrome.com/docs/performance/insights/cache).

Evidence
{
  "description": "A long cache lifetime can speed up repeat visits to your page. [Learn more about caching](https://developer.chrome.com/docs/performance/insights/cache).",
  "displayValue": "Est savings of 348 KiB"
}

Performance and AccessibilityPerformanceBrowser audit

Legacy JavaScript

8 Warning

Check name

Legacy JavaScript

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Est savings of 36 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
{
  "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)",
  "displayValue": "Est savings of 36 KiB"
}

Performance and AccessibilityPerformanceBrowser audit

Reduce unused CSS

8 Warning

Check name

Reduce unused CSS

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Est savings of 34 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
{
  "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/).",
  "displayValue": "Est savings of 34 KiB",
  "numericValue": 0
}

Performance and AccessibilityPerformanceBrowser audit

Loading performance

3 Fail

Check name

Loading performance

Score

84/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": "speed-index",
      "score": 69,
      "title": "Speed Index",
      "displayValue": "1.8 s",
      "numericValue": 1827.5984477250258
    },
    {
      "id": "max-potential-fid",
      "score": 81,
      "title": "Max Potential First Input Delay",
      "displayValue": "160 ms",
      "numericValue": 159
    },
    {
      "id": "largest-contentful-paint",
      "score": 89,
      "title": "Largest Contentful Paint",
      "displayValue": "1.2 s",
      "numericValue": 1209.5018870387835
    },
    {
      "id": "interactive",
      "score": 75,
      "title": "Time to Interactive",
      "displayValue": "3.3 s",
      "numericValue": 3265.05427602889
    },
    {
      "id": "server-response-time",
      "score": 100,
      "title": "Initial server response time was short",
      "displayValue": "Root document took 500 ms",
      "numericValue": 500
    },
    {
      "id": "total-blocking-time",
      "score": 64,
      "title": "Total Blocking Time",
      "displayValue": "270 ms",
      "numericValue": 273.5
    },
    {
      "id": "first-contentful-paint",
      "score": 97,
      "title": "First Contentful Paint",
      "displayValue": "0.7 s",
      "numericValue": 729.5018870387836
    },
    {
      "id": "network-rtt",
      "score": 100,
      "title": "Network Round Trip Times",
      "displayValue": "20 ms",
      "numericValue": 20.814255
    }
  ]
}

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.

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