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

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability52%Agent Easeof Use66%Security& Trust77%GEO, AIO, AEO29%SEO92%Performance33%Accessibility0%
  • AI Discoverability 52 out of 100
  • Agent Ease of Use 66 out of 100
  • Security & Trust 77 out of 100
  • GEO, AIO and AEO 29 out of 100
  • SEO 92 out of 100
  • Performance 33 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

JetBrains: Essential tools for software developers and teams favicon

JetBrains: Essential tools for software developers and teams

JetBrains is a cutting-edge software vendor specializing in the creation of intelligent development tools, including IntelliJ IDEA – the leading Java IDE, and the Kotlin programming language.

Next step

Turn this report into a fix workflow

11 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
52
Needs work21116View details
Discoverability
47
Priority fix630View details
Content Readiness
65
Needs work1473View details
Bot Access Control
45
Priority fix113View details
Agent Ease of Use
66
Needs work6311View details
API
50
Needs work430View details
Auth
50
Needs work002
MCP
50
Needs work003
Skill Discovery
50
Needs work005
Agent Commerce
81
Mostly ready201
GEO, AIO and AEO
29
Priority fix3105View details
GEO Readiness
19
Priority fix141View details
AIO Readiness
45
Priority fix123View details
AEO Readiness
22
Priority fix141View details
SEO
92
Strong910View details
SEO
92
Strong910View details
Security & Trust
77
Mostly ready1723View details
Security & Trust
77
Mostly ready1723View details
Performance
33
Priority fix10113View details
Performance
33
Priority fix10113View details
Accessibility
0
Priority fix010View details
Accessibility
0
Priority fix010View details

Prioritized recommendations

Issues ranked by score impact

56 items need attention

AI DiscoverabilityDiscoverabilityEstablished

Link headers

Link headers failed at "Find useful Link headers".

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

Agent Ease of UseAPIEstablished

OpenAPI discovery

OpenAPI discovery failed at "Parse OpenAPI document".

50 Fail

Needs attention

OpenAPI discovery

Failed check
01

Issue

OpenAPI candidate was not parseable as JSON or YAML-like OpenAPI.

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

50/100

Status

fail

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 failed at "Parse OpenAPI document".

Validation steps

  1. Parse OpenAPI document

    OpenAPI candidate was not parseable as JSON or YAML-like OpenAPI.

  2. Validate OpenAPI shape

    Response is not valid JSON and does not match baseline OpenAPI YAML shape.

  3. Check machine-usable details

    Add servers, parameters, request bodies, response schemas, operation IDs, tags, examples, and security or explicit no-auth declarations where they apply.

Evidence log3 steps · 14 lines
Parse OpenAPI document [fail]! OpenAPI candidate was not parseable as JSON or YAML-like OpenAPI.INFOParse OpenAPI document status="fail"INFOParse selected document as JSON first, then YAML-like OpenAPI parsed=false format="unknown" versionFamily="missing"FAILCheck parse result actual="not parseable" expected="parseable OpenAPI 3.x or Swagger 2.0 document" compatibleContentType=falseFAILOpenAPI candidate was not parseable as JSON or YAML-like OpenAPI.Validate OpenAPI shape [fail]! Response is not valid JSON and does not match baseline OpenAPI YAML shape.INFOValidate OpenAPI shape status="fail"INFOValidate required OpenAPI shape versionFamily="missing" pathCount=0 webhookCount=0 operationCount=0PASSCheck operations define responses actual=0 expected="every operation should define responses"FAILCheck info metadata actual={"hasInfoTitle":false,"hasInfoVersion":false} expected="info.title and info.version present"FAILOpenAPI shape issue issue="Response is not valid JSON and does not match baseline OpenAPI YAML shape."FAILResponse is not valid JSON and does not match baseline OpenAPI YAML shape.Check machine-usable details [fail]INFOCheck machine-usable details status="fail"INFOInspect machine-usable operation details hasServers=false hasSecuritySchemes=false hasExplicitNoAuth=false requestBodyOperationCount=0 parameterOperationCount=0 responseSchemaOperationCount=0 operationIdCount=0 taggedOperationCount=0 exampleOperationCount=0PASSCheck OpenAPI operations include enough detail for agents to call them safely actual="no machine-usability warnings" expected="servers, auth/no-auth signals, operationIds, parameters, request bodies, responses, tags, and examples where relevant"FAILOpenAPI discovery validation failed.

AI DiscoverabilityDiscoverabilityEstablished

robots.txt

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

30 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=3 expected=">= 1 parseable group" parsedUserAgents=["*","Yandex","Baiduspider"]FAILCheck malformed lines and orphan Allow/Disallow records actual={"invalidLines":0,"orphanRecords":7} expected={"invalidLines":0,"orphanRecords":0}FAILAllow/Disallow records appeared before any User-agent group orphanRecords=[{"directive":"disallow","value":"*/search/","line":3},{"directive":"disallow","value":"*/shop/","line":4},{"directive":"disallow","value":"*/eshop*","line":5},{"directive":"disallow","value":"*/estore*","line":6},{"directive":"disallow","value":"*/unitrun*","line":7}]

AI DiscoverabilityContent ReadinessEmerging recommendation

llms.txt

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

25 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://www.jetbrains.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://www.jetbrains.com/llms-full.txt"SKIP/llms-full.txt is not present statusCode=404

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://www.jetbrains.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://www.jetbrains.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://www.jetbrains.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://www.jetbrains.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://www.jetbrains.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"WARNNo MCP server card was found reason="No MCP server card was found at current, transitional, or linked discovery paths."

Agent Ease of UseAuthEstablished

OAuth / OIDC discovery

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

25 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=1 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":45088},{"path":"/.well-known/oauth-authorization-server","statusCode":404,"contentType":"text/html; charset=utf-8","length":44890}]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".

25 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=1 checkedCount=1WARNCheck protected-resource metadata applicability actual=false expected="true when RFC 9728 metadata exists or support is claimed" checked=[{"url":"https://www.jetbrains.com/.well-known/oauth-protected-resource","path":"/.well-known/oauth-protected-resource","source":"root-well-known","resourceIdentifier":"https://www.jetbrains.com","statusCode":404,"contentType":"text/html; charset=utf-8","length":45088}]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 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://www.jetbrains.com/.well-known/webmcp.json" statusCode=404 contentType="text/html; charset=utf-8"INFOWebMCP manifest candidate checked source="path" path="/webmcp.json" url="https://www.jetbrains.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="(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"

AI DiscoverabilityContent ReadinessEstablished

Markdown negotiation

Markdown negotiation is missing or incomplete.

23 Fail

Needs attention

Markdown negotiation

Failed check
01

Issue

Best candidate returned Content-Type "text/html; charset=utf-8" 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 contains too much raw HTML to be a clean agent-facing Markdown representation.

  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://www.jetbrains.com/","statusCode":200,"contentType":"text/html; charset=utf-8","mediaType":"text/html","vary":"","requireVaryAccept":true,"contentTypeStatus":"fail","cacheStatus":"fail","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"html-heavy","hasHeading":false,"headingCount":0,"wordCount":4854,"features":{"markdownLinks":0,"referenceLinks":0,"listItems":7,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":84,"jsxOrMdxSignals":0},"issues":["missing-heading","raw-html-heavy"],"excerpt":"<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n    <!-- Optimizely -->\n<script type=\"text/javascript\">\n    window.optimizely = window.optimizely || [];\n\n    function checkConsent() {\n        var hasAnalyticsConsent = false;\n\n        // Find the co","issue":"Markdown response contains too much raw HTML to be a clean agent-facing Markdown representation."}} expected="negotiated, advertised alternate, or conventional mirror" selected={"source":"negotiated","url":"https://www.jetbrains.com/","statusCode":200,"contentType":"text/html; charset=utf-8","mediaType":"text/html","vary":"","requireVaryAccept":true,"contentTypeStatus":"fail","cacheStatus":"fail","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"html-heavy","hasHeading":false,"headingCount":0,"wordCount":4854,"features":{"markdownLinks":0,"referenceLinks":0,"listItems":7,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":84,"jsxOrMdxSignals":0},"issues":["missing-heading","raw-html-heavy"],"excerpt":"<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n    <!-- Optimizely -->\n<script type=\"text/javascript\">\n    window.optimizely = window.optimizely || [];\n\n    function checkConsent() {\n        var hasAnalyticsConsent = false;\n\n        // Find the co","issue":"Markdown response contains too much raw HTML to be a clean agent-facing Markdown representation."}} 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":200,"mediaType":"text/html","vary":""} expected="HTTP 2xx text/markdown with Vary: Accept" url="https://www.jetbrains.com/" statusCode=200 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 contains too much raw HTML to be a clean agent-facing Markdown representation.INFOMarkdown format validationFAILCheck Markdown body quality actual={"valid":false,"wordCount":4854,"headingCount":0,"dialect":"html-heavy"} expected="valid Markdown with substantive text and headings" valid=false dialect="html-heavy" wordCount=4854 headingCount=0FAILMarkdown format validation failed issue="Markdown response contains too much raw HTML to be a clean agent-facing Markdown representation."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://www.jetbrains.com/index.html.md"] candidateCount=1FAILConventional .md mirror failed issue="Conventional .md mirror candidates did not return valid Markdown."

Agent Ease of UseAgent CommerceInformational

ACP - Agentic Commerce Protocol

ACP - Agentic Commerce Protocol has a validation warning at "Fetch ACP discovery".

19 Warning

Needs attention

ACP - Agentic Commerce Protocol

Warning
01

Issue

ACP-like signals were found, but /.well-known/acp.json was not available.

02

Why it matters

ACP discovery lets agents find the seller's ACP API base URL, supported versions, transports, and stable services before attempting authenticated checkout-session negotiation.

Check name

ACP - Agentic Commerce Protocol

Score

81/100

Status

warning

Category

Agent Commerce

Maturity

Informational

Goal

Expose valid ACP discovery when this origin supports Agentic Commerce Protocol workflows.

Result

ACP - Agentic Commerce Protocol has a validation warning at "Fetch ACP discovery".

Validation steps

  1. Fetch ACP discovery

    ACP-like signals were found, but /.well-known/acp.json was not available.

Evidence log1 step · 5 lines
Fetch ACP discovery [warning]! ACP-like signals were found, but /.well-known/acp.json was not available.INFOFetch ACP discovery status="warning"INFOFetch canonical ACP discovery /.well-known/acp.json statusCode=404 contentType="text/html; charset=utf-8" parsed=falseINFOFetch compatibility ACP discovery /.well-known/acp statusCode=404 contentType="text/html; charset=utf-8" parsed=falseWARNCheck canonical ACP discovery response actual=false expected=true canonicalFound=false compatibilityFound=falseWARNACP-like signals were found, but /.well-known/acp.json was not available.

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

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

Applicable HTML response is missing an enforcing Content-Security-Policy header.

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

    Applicable HTML response is missing an enforcing Content-Security-Policy header.

Evidence log1 step · 4 lines
Find enforcing CSP delivery [fail]! Applicable HTML response is missing an enforcing Content-Security-Policy header.INFOFind enforcing CSP deliveryINFORead CSP delivery headers enforcingHeader="missing" reportOnlyHeader="missing" metaPolicyCount=0 legacyHeadersPresent=[]FAILRequire enforcing Content-Security-Policy header actual="missing" expected="present" issue="Applicable HTML response is missing an enforcing Content-Security-Policy header."FAILApplicable HTML response is missing an enforcing Content-Security-Policy header.

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://www.jetbrains.com/.well-known/agent-skills/index.json" statusCode=404WARNAgent Skills index candidate was not usable path="/.well-known/skills/index.json" url="https://www.jetbrains.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 · 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="www.jetbrains.com" labels=["_index._agents.www.jetbrains.com","_a2a._agents.www.jetbrains.com"] claimedOnPage=falseWARNDNS query returned no DNS-AID answers name="_index._agents.www.jetbrains.com" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.www.jetbrains.com" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.www.jetbrains.com" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _index._agents.www.jetbrains.com"WARNDNS query returned no DNS-AID answers name="_a2a._agents.www.jetbrains.com" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.www.jetbrains.com" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.www.jetbrains.com" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _a2a._agents.www.jetbrains.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.www.jetbrains.com" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.www.jetbrains.com" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.www.jetbrains.com" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.www.jetbrains.com" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.www.jetbrains.com" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.www.jetbrains.com" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.www.jetbrains.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.www.jetbrains.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="www.jetbrains.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="jetbrains.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=44846WARNNo TDMRep declaration was found at /.well-known/tdmrep.json. 

Security & TrustSecurity & TrustEstablished

X-Content-Type-Options

X-Content-Type-Options failed at "Validate nosniff value".

8 Fail

Needs attention

X-Content-Type-Options

Failed check
01

Issue

X-Content-Type-Options first effective value is not nosniff.

02

Why it matters

X-Content-Type-Options tells browsers to trust declared media types instead of sniffing content, reducing the risk that mislabeled files execute as active content.

Check name

X-Content-Type-Options

Score

68/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Prevent browser MIME sniffing for browser-loadable responses with X-Content-Type-Options: nosniff.

Result

X-Content-Type-Options failed at "Validate nosniff value".

Validation steps

  1. Validate nosniff value

    X-Content-Type-Options first effective value is not nosniff.

  2. Review observed browser responses

    One or more same-origin browser-observed responses had missing or non-conformant nosniff headers.

Evidence log2 steps · 8 lines
Validate nosniff value [fail]! X-Content-Type-Options first effective value is not nosniff.INFOValidate nosniff valueINFOParse X-Content-Type-Options values values=["nosniff nosniff"] firstValue="nosniff nosniff" extraValues=[]FAILCompare effective nosniff value actual="nosniff nosniff" expected="nosniff" nosniffActive=false conformant=false issue="X-Content-Type-Options first effective value is not nosniff."FAILX-Content-Type-Options first effective value is not nosniff.Review observed browser responses [warning]! One or more same-origin browser-observed responses had missing or non-conformant nosniff headers.INFOReview observed browser responsesINFOSample Chrome-observed same-origin resources observedResponseCount=29 sameOriginCount=10 eligibleCount=9WARNCompare observed nosniff coverage actual={"missingNosniffCount":1,"malformedNosniffCount":0,"activeResourceMissingNosniffCount":0,"affected":[{"url":"https://www.jetbrains.com/","status":200,"resourceType":"document","contentType":"text/html; charset=utf-8","xContentTypeOptions":"nosniff nosniff"}]} expected="0 missing or malformed eligible same-origin responses" issue="One or more same-origin browser-observed responses had missing or non-conformant nosniff headers."WARNOne or more same-origin browser-observed responses had missing or non-conformant nosniff headers.

AI DiscoverabilityContent ReadinessEstablished

Organization / WebSite schema

Organization / WebSite schema is partially implemented.

7 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

73/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. Identity fields

    Missing identity field(s): Organization.name.

  2. WebSite publisher linkage

    WebSite.publisher is missing.

Evidence log2 steps · 10 lines
Identity fields [warning]! Missing identity field(s): Organization.name.INFOIdentity fieldsINFOChecking Organization and WebSite name/url fields organizationFormat="json-ld" websiteFormat="json-ld"WARNCheck required identity fields actual=3 expected=4 missing=["Organization.name"] organizationFields=[{"name":"Organization.@type","present":true,"value":"Organization","format":"json-ld"},{"name":"Organization.@id","present":true,"value":"https://www.jetbrains.com/#organization","format":"json-ld"},{"name":"Organization.name","present":false,"format":"json-ld"},{"name":"Organization.url","present":true,"value":"https://www.jetbrains.com","format":"json-ld"},{"name":"Organization.logo","present":true,"value":"https://www.jetbrains.com/company/brand/img/jetbrains_logo.png","format":"json-ld"},{"name":"Organization.sameAs","present":true,"value":["https://x.com/jetbrains","https://www.facebook.com/JetBrains","https://youtube.com/user/JetBrainsTV","https://www.linkedin.com/company/jetbrains","http://www.wikidata.org/entity/Q1688472"],"format":"json-ld"}] websiteFields=[{"name":"WebSite.@type","present":true,"value":"WebSite","format":"json-ld"},{"name":"WebSite.@id","present":true,"value":"https://www.jetbrains.com/#website","format":"json-ld"},{"name":"WebSite.name","present":true,"value":"JetBrains","format":"json-ld"},{"name":"WebSite.url","present":true,"value":"https://www.jetbrains.com","format":"json-ld"},{"name":"WebSite.publisher.@id","present":false,"format":"json-ld"},{"name":"WebSite.publisher.name","present":false,"format":"json-ld"},{"name":"WebSite.publisher.url","present":false,"format":"json-ld"}]PASSCheck identity URLs match scanned origin actual={"organizationUrlMatchesOrigin":true,"websiteUrlMatchesOrigin":true} expected={"organizationUrlMatchesOrigin":true,"websiteUrlMatchesOrigin":true}WARNIdentity fields are partially complete missing=["Organization.name"]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={"id":"https://www.jetbrains.com/#website","name":"JetBrains","url":"https://www.jetbrains.com"} organization={"id":"https://www.jetbrains.com/#organization","url":"https://www.jetbrains.com"}FAILCheck publisher matches Organization actual=false expected=trueFAILWebSite publisher is missing

AI DiscoverabilityContent ReadinessEstablished

Semantic HTML

Semantic HTML is partially implemented.

7 Warning

Needs attention

Semantic HTML

Warning
01

Issue

Semantic HTML is incomplete: invalid h1 structure (visible h1 count 0).

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

73/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. Page landmarks

    The page has a main landmark but is missing a primary navigation, header/banner, or page-level footer/contentinfo landmark.

  2. Heading structure

    Expected one meaningful visible h1; found 0.

Evidence log2 steps · 6 lines
Page landmarks [warning]! The page has a main landmark but is missing a primary navigation, header/banner, or page-level footer/contentinfo landmark.INFOPage landmarksWARNCheck page landmarks evidence actual={"counts":{"main":1,"roleMain":0,"nav":0,"roleNavigation":0,"header":0,"roleBanner":0,"footer":0,"pageFooter":0,"roleContentinfo":0},"main":true} expected="semantic HTML evidence for this step"WARNPage landmarks has a warning issue="The page has a main landmark but is missing a primary navigation, header/banner, or page-level footer/contentinfo landmark."Heading structure [fail]! Expected one meaningful visible h1; found 0.INFOHeading structureFAILCheck heading structure evidence actual={"counts":{"h1":0,"visibleH1":0,"headings":0,"emptyHeadings":0},"meaningfulH1":false} expected="semantic HTML evidence for this step"FAILHeading structure failed issue="Expected one meaningful visible h1; found 0."

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Evidence and trust

AEO: Evidence and trust scored 14/100 and needs a fix.

6 Fail

Needs attention

AEO: Evidence and trust

Failed check
01

Issue

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

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

14/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: Evidence and trust scored 14/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Source and trust signals

AIO: Source and trust signals scored 0/100 and needs a fix.

6 Fail

Needs attention

AIO: Source and trust signals

Failed check
01

Issue

Missing AIO trust signals: author, publisher, freshnessDate, aboutOrContact, policyLinks, sourceLinks.

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

0/100

Status

fail

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Source and trust signals

GEO: Source and trust signals scored 17/100 and needs a fix.

6 Fail

Needs attention

GEO: Source and trust signals

Failed check
01

Issue

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

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

17/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: Source and trust signals scored 17/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Structured extraction

GEO: Structured extraction scored 25/100 and needs a fix.

5 Fail

Needs attention

GEO: Structured extraction

Failed check
01

Issue

Missing or weak extraction signals: heading structure, clean heading hierarchy, summary or key takeaways, lists for grouped facts or steps, 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

25/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: Structured extraction scored 25/100 and needs a fix.

Security & TrustSecurity & TrustEstablished

Frame protection

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

5 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

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

Evidence log1 step · 4 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=false 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.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Citable passages

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

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Extractable HTML

GEO: Extractable HTML scored 35/100 and needs a fix.

5 Fail

Needs attention

GEO: Extractable HTML

Failed check
01

Issue

Only 8 visible words were found in the initial HTML. Initial HTML has low visible-text density.

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: Extractable HTML

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: Extractable HTML scored 35/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question and answer structure

AEO: Question and answer structure scored 40/100 and needs a fix.

4 Fail

Needs attention

AEO: Question and answer structure

Failed check
01

Issue

No natural question headings were detected. No visible FAQ or Q&A pattern was detected. Heading structure issues were detected. No list or table answer format 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: Question and answer structure

Score

40/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: Question and answer structure scored 40/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Extractable visible copy

AEO: Extractable visible copy scored 46/100 and needs a fix.

4 Fail

Needs attention

AEO: Extractable visible copy

Failed check
01

Issue

Only 8 visible words were detected for answer extraction. Visible text has few answer-oriented terms or explanatory markers.

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: Extractable visible copy

Score

46/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: Extractable visible copy scored 46/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

AEO: Entity and definition clarity scored 49/100 and needs a fix.

4 Fail

Needs attention

AEO: Entity and definition clarity

Failed check
01

Issue

Expected exactly one h1, found 0. 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

49/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: Entity and definition clarity scored 49/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Visible content clarity

AIO: Visible content clarity scored 47/100 and needs a fix.

3 Fail

Needs attention

AIO: Visible content clarity

Failed check
01

Issue

Expected exactly one h1, found 0. Only 8 visible words were detected. Heading outline issues were detected.

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: Visible content clarity

Score

47/100

Status

fail

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: Visible content clarity scored 47/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first passages

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

3 Warning

Needs attention

AEO: Answer-first passages

Warning
01

Issue

No h2/h3 answer sections were detected. 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

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Structured data consistency

AIO: Structured data consistency scored 50/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

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: Structured data consistency scored 50/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Page experience proxy

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

2 Warning

Needs attention

AIO: Page experience proxy

Warning
01

Issue

Only 8 words of visible rendered text were detected.

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

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

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

GEO: Entity clarity

GEO: Entity clarity scored 80/100 and needs improvement.

1 Warning

Needs attention

GEO: Entity clarity

Warning
01

Issue

Expected exactly one h1, found 0. Title/H1 terms missing from description: essential, developers, teams.

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: Entity clarity

Score

80/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: Entity clarity scored 80/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Google Search eligibility

AIO: Google Search eligibility scored 80/100 and needs improvement.

1 Warning

Needs attention

AIO: Google Search eligibility

Warning
01

Issue

Only 8 visible words were detected.

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: Google Search eligibility

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: Google Search eligibility scored 80/100 and needs improvement.

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.

AccessibilityAccessibilityBrowser audit

Accessibility audit

100 Fail

Check name

Accessibility audit

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

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

Evidence
{
  "error": "Accessibility audit did not return a result."
}

SEOSEOBrowser audit

Links do not have descriptive text

100 Fail

Check name

Links do not have descriptive text

Score

0/100

Status

fail

Device

desktop

Category

SEO

Estimated savings

2 links found

Fix guidance

Descriptive link text helps search engines understand your content. [Learn how to make links more accessible](https://developer.chrome.com/docs/lighthouse/seo/link-text/).

Evidence
{
  "description": "Descriptive link text helps search engines understand your content. [Learn how to make links more accessible](https://developer.chrome.com/docs/lighthouse/seo/link-text/).",
  "displayValue": "2 links found"
}

PerformancePerformanceBrowser audit

Avoid large layout shifts

7 Fail

Check name

Avoid large layout shifts

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

4 layout shifts found

Fix guidance

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls). [Learn how to improve CLS](https://web.dev/articles/optimize-cls)

Evidence
{
  "description": "These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls). [Learn how to improve CLS](https://web.dev/articles/optimize-cls)",
  "displayValue": "4 layout shifts found"
}

PerformancePerformanceBrowser audit

Improve image delivery

7 Fail

Check name

Improve image delivery

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

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

PerformancePerformanceBrowser audit

Layout shift culprits

7 Fail

Check name

Layout shift culprits

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

Layout shifts occur when elements move absent any user interaction. [Investigate the causes of layout shifts](https://developer.chrome.com/docs/performance/insights/cls-culprit), such as elements being added, removed, or their fonts changing as the page loads.

Evidence
{
  "description": "Layout shifts occur when elements move absent any user interaction. [Investigate the causes of layout shifts](https://developer.chrome.com/docs/performance/insights/cls-culprit), such as elements being added, removed, or their fonts changing as the page loads."
}

PerformancePerformanceBrowser audit

LCP request discovery

7 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

Legacy JavaScript

7 Fail

Check name

Legacy JavaScript

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 33 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 33 KiB"
}

PerformancePerformanceBrowser audit

Network dependency tree

7 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

7 Fail

Check name

Reduce JavaScript execution time

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

2.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
{
  "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/).",
  "displayValue": "2.8 s",
  "numericValue": 2784.186999999984
}

PerformancePerformanceBrowser audit

Reduce unused CSS

7 Fail

Check name

Reduce unused CSS

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 128 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 128 KiB",
  "numericValue": 80
}

PerformancePerformanceBrowser audit

Render-blocking requests

7 Fail

Check name

Render-blocking requests

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 2,130 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 2,130 ms"
}

PerformancePerformanceBrowser audit

Use efficient cache lifetimes

7 Fail

Check name

Use efficient cache lifetimes

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 245 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 245 KiB"
}

PerformancePerformanceBrowser audit

Loading performance

4 Fail

Check name

Loading performance

Score

45/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": "first-contentful-paint",
      "score": 22,
      "title": "First Contentful Paint",
      "displayValue": "2.2 s",
      "numericValue": 2205.4383407401083
    },
    {
      "id": "total-blocking-time",
      "score": 2,
      "title": "Total Blocking Time",
      "displayValue": "1,230 ms",
      "numericValue": 1227.2478408777977
    },
    {
      "id": "interactive",
      "score": 42,
      "title": "Time to Interactive",
      "displayValue": "4.9 s",
      "numericValue": 4942.366951608218
    },
    {
      "id": "network-rtt",
      "score": 100,
      "title": "Network Round Trip Times",
      "displayValue": "10 ms",
      "numericValue": 8.918737500000002
    },
    {
      "id": "server-response-time",
      "score": 100,
      "title": "Initial server response time was short",
      "displayValue": "Root document took 0 ms",
      "numericValue": 1
    },
    {
      "id": "largest-contentful-paint",
      "score": 25,
      "title": "Largest Contentful Paint",
      "displayValue": "3.4 s",
      "numericValue": 3402.431143666101
    },
    {
      "id": "speed-index",
      "score": 23,
      "title": "Speed Index",
      "displayValue": "3.1 s",
      "numericValue": 3137.567055593001
    },
    {
      "id": "max-potential-fid",
      "score": 46,
      "title": "Max Potential First Input Delay",
      "displayValue": "260 ms",
      "numericValue": 262
    }
  ]
}

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,659 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
{
  "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/).",
  "displayValue": "Total size was 8,659 KiB",
  "numericValue": 8866976
}

PerformancePerformanceBrowser audit

Font display

4 Warning

Check name

Font display

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Est savings of 20 ms

Fix guidance

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

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

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)"
}

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
47/100Level 2, Agent-LimitedCurrent report