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

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability59%Agent Easeof Use51%Security& Trust55%GEO, AIO, AEO55%SEO100%Performance& Accessibility76%
  • AI Discoverability 59 out of 100
  • Agent Ease of Use 51 out of 100
  • Security & Trust 55 out of 100
  • GEO, AIO and AEO 55 out of 100
  • SEO 100 out of 100
  • Performance and Accessibility 76 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

BALIBET: Rekomendasi Tempat Bermain Game Online Terlengkap di Indonesia favicon

BALIBET: Rekomendasi Tempat Bermain Game Online Terlengkap di Indonesia

BALIBET adalah rekomendasi tempat bermain game online terlengkap di Indonesia yang menghadirkan ribuan pilihan permainan seru, bonus besar, dan layanan cepat 24 jam untuk pengalaman bermain terbaik.

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
59
Needs work21149View details
Discoverability
67
Needs work820View details
Content Readiness
38
Priority fix9126View details
Bot Access Control
69
Needs work403
Agent Ease of Use
51
Needs work1110View details
Auth
50
Needs work003
MCP
50
Needs work003
Skill Discovery
53
Needs work114View details
GEO, AIO and AEO
55
Needs work756View details
GEO Readiness
51
Needs work222View details
AIO Readiness
81
Mostly ready411View details
AEO Readiness
34
Priority fix123View details
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
55
Needs work1145View details
Security & Trust
55
Needs work1145View details
Performance and Accessibility
76
Mostly ready1770View details
Performance
75
Mostly ready1460View details
Accessibility
78
Mostly ready310View details

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 · 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 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://hoxtongin.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"INFOTrying to fetch /.well-known/mcp/server-card.json url="https://hoxtongin.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"INFOTrying to fetch /.well-known/mcp/server-cards.json url="https://hoxtongin.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"INFOTrying to fetch /mcp.json url="https://hoxtongin.com/mcp.json" source="transitional"FAIL/mcp.json did not return a usable server card statusCode=404 contentType="text/html"INFOTrying to fetch /.well-known/mcp.json url="https://hoxtongin.com/.well-known/mcp.json" source="transitional"FAIL/.well-known/mcp.json did not return a usable server card statusCode=404 contentType="text/html"WARNNo MCP server card was found reason="No MCP server card was found at current, transitional, or linked discovery paths."

Agent Ease of UseMCPEmerging recommendation

WebMCP

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

25 Warning

Needs attention

WebMCP

Warning
01

Issue

No WebMCP surface was found to probe.

Details

02

Why it matters

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

Check name

WebMCP

Score

50/100

Status

warning

Category

MCP

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Detect WebMCP runtime API

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

  2. Probe WebMCP operability

    No WebMCP surface was found to probe.

    WebMCP operability findings
    • No WebMCP surface was found to probe.
    • 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://hoxtongin.com/.well-known/webmcp.json" statusCode=404 contentType="text/html"INFOWebMCP manifest candidate checked source="path" path="/webmcp.json" url="https://hoxtongin.com/webmcp.json" statusCode=404 contentType="text/html"WARNValidate discovered static WebMCP metadata actual={"validManifestCount":0,"invalidManifestCount":0,"toolCount":0,"wmcpActionCount":0} expected="at least 1 valid tools[] manifest or WMCP graph when static metadata is present"WARNNo static WebMCP JSON manifest or WMCP interaction graph was found.Validate WebMCP tool metadata quality [informational]INFOValidate WebMCP tool metadata quality status="informational"INFOInspect WebMCP tool names, descriptions, schemas, and safety hints toolCount=0SKIPCheck tool metadata findings actual={"issueCount":0,"warningCount":0} expected="0 issues and 0 warnings"INFOWebMCP evidence was recorded for context. status="informational"Review WebMCP security and policy signals [informational]INFOReview WebMCP security and policy signals status="informational"INFOInspect WebMCP security and policy signals permissionsPolicy="(missing)" failureCount=0 warningCount=0PASSCheck security findings actual={"failures":0,"warnings":0} expected="0 failures and 0 warnings"INFOWebMCP evidence was recorded for context. status="informational"

AI DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is missing or incomplete.

17 Fail

Needs attention

Content freshness signals

Failed check
01

Issue

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

Details

02

Why it matters

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

Check name

Content freshness signals

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

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

Result

Content freshness signals is missing or incomplete.

Validation steps

  1. Validate Last-Modified header

    No valid Last-Modified HTTP header was found.

  2. Validate structured freshness dates

    No Schema.org freshness dates were found.

  3. Validate metadata freshness dates

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

  4. Corroborate with sitemap lastmod

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

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

AI DiscoverabilityContent ReadinessEmerging recommendation

llms.txt

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

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

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

AI DiscoverabilityBot Access ControlEmerging recommendation

RSL license signal

No RSL declarations were found.

17 Warning

Needs attention

RSL license signal

Warning
01

Issue

No RSL declarations were found.

02

Why it matters

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

Check name

RSL license signal

Score

50/100

Status

warning

Category

Bot Access Control

Maturity

Emerging recommendation

Goal

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

Result

No RSL declarations were found.

Validation steps

  1. Discover RSL declarations

    No RSL declarations were found.

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

AI DiscoverabilityBot Access ControlEmerging recommendation

TDMRep declaration

No TDMRep declaration was found.

17 Warning

Needs attention

TDMRep declaration

Warning
01

Issue

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

02

Why it matters

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

Check name

TDMRep declaration

Score

50/100

Status

warning

Category

Bot Access Control

Maturity

Emerging recommendation

Goal

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

Result

No TDMRep declaration was found.

Validation steps

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

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

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

AI DiscoverabilityContent ReadinessEstablished

Markdown negotiation

Markdown negotiation is missing or incomplete.

15 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://hoxtongin.com/news/","statusCode":200,"contentType":"text/html; charset=UTF-8","mediaType":"text/html","vary":"Accept-Encoding","requireVaryAccept":true,"contentTypeStatus":"fail","cacheStatus":"fail","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"html-heavy","hasHeading":false,"headingCount":0,"wordCount":15595,"features":{"markdownLinks":0,"referenceLinks":0,"listItems":0,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":707,"jsxOrMdxSignals":0},"issues":["missing-heading","raw-html-heavy","plain-text-like"],"excerpt":"<!DOCTYPE html>\n<html>\n<head>\n    <script async=\"\" src=\"https://www.googletagmanager.com/gtm.js?id=GTM-NNZ3S8P5\"></script>\n    <meta name=\"viewport\" content=\"width=device-width\" />\n    <meta name=\"page google.com\" content=\"https://www.googl","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://hoxtongin.com/news/","statusCode":200,"contentType":"text/html; charset=UTF-8","mediaType":"text/html","vary":"Accept-Encoding","requireVaryAccept":true,"contentTypeStatus":"fail","cacheStatus":"fail","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"html-heavy","hasHeading":false,"headingCount":0,"wordCount":15595,"features":{"markdownLinks":0,"referenceLinks":0,"listItems":0,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":707,"jsxOrMdxSignals":0},"issues":["missing-heading","raw-html-heavy","plain-text-like"],"excerpt":"<!DOCTYPE html>\n<html>\n<head>\n    <script async=\"\" src=\"https://www.googletagmanager.com/gtm.js?id=GTM-NNZ3S8P5\"></script>\n    <meta name=\"viewport\" content=\"width=device-width\" />\n    <meta name=\"page google.com\" content=\"https://www.googl","issue":"Markdown response contains too much raw HTML to be a clean agent-facing Markdown representation."}} candidatesChecked=3FAILMarkdown 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":"Accept-Encoding"} expected="HTTP 2xx text/markdown with Vary: Accept" url="https://hoxtongin.com/news/" statusCode=200 mediaType="text/html" vary="Accept-Encoding"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":15595,"headingCount":0,"dialect":"html-heavy"} expected="valid Markdown with substantive text and headings" valid=false dialect="html-heavy" wordCount=15595 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=2 expected="> 0 when a conventional mirror is discoverable" conventionalUrls=["https://hoxtongin.com/news/index.html.md","https://hoxtongin.com/news.md"] candidateCount=2FAILConventional .md mirror failed issue="Conventional .md mirror candidates did not return valid Markdown."

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

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

13 Warning

Needs attention

A2A Agent Card

Warning
01

Issue

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

02

Why it matters

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

Check name

A2A Agent Card

Score

50/100

Status

warning

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Discover A2A Agent Card

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

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

Agent Ease of UseSkill DiscoveryEmerging recommendation

Agent Skills index

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

13 Warning

Needs attention

Agent Skills index

Warning
01

Issue

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

02

Why it matters

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

Check name

Agent Skills index

Score

50/100

Status

warning

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Discover Agent Skills index

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

Evidence log1 step · 5 lines
Discover Agent Skills index [warning]! No Agent Skills discovery index was found at the canonical or legacy path.INFODiscover Agent Skills indexINFOTry Agent Skills index paths in priority order paths=["/.well-known/agent-skills/index.json","/.well-known/skills/index.json"]WARNAgent Skills index candidate was not usable path="/.well-known/agent-skills/index.json" url="https://hoxtongin.com/.well-known/agent-skills/index.json" statusCode=404WARNAgent Skills index candidate was not usable path="/.well-known/skills/index.json" url="https://hoxtongin.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"WARNagents.json candidate path did not return a usable contract path="/agents.json" statusCode=404 contentType="text/html"WARNNo agents.json candidate was selectedWARNNo Wildcard-style agents.json file was found.

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

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

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

Security & TrustSecurity & TrustEstablished

Referrer-Policy

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

12 Fail

Needs attention

Referrer-Policy

Failed check
01

Issue

Referrer-Policy header is missing.

02

Why it matters

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

Check name

Referrer-Policy

Score

40/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

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

Result

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

Validation steps

  1. Find Referrer-Policy header

    Referrer-Policy header is missing.

  2. Review observed browser responses

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

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

Security & TrustSecurity & TrustEstablished

Frame protection

Frame protection failed at "Validate X-Frame-Options".

11 Fail

Needs attention

Frame protection

Failed check
01

Issue

No valid X-Frame-Options fallback is present.

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

44/100

Status

fail

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 failed at "Validate X-Frame-Options".

Validation steps

  1. Validate CSP frame-ancestors

    No enforcing CSP frame-ancestors directive is present.

  2. Validate X-Frame-Options

    No valid X-Frame-Options fallback is present.

  3. Review observed browser responses

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

Evidence log3 steps · 12 lines
Validate CSP frame-ancestors [warning]! No enforcing CSP frame-ancestors directive is present.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="No enforcing CSP frame-ancestors directive is present."WARNNo enforcing CSP frame-ancestors directive is present.Validate X-Frame-Options [fail]! No valid X-Frame-Options fallback is present.INFOValidate X-Frame-OptionsINFORead X-Frame-Options fallback value="missing" parsedValues=[] normalizedValues=[]FAILCompare X-Frame-Options value actual="missing" expected="DENY or SAMEORIGIN" valid=false obsoleteAllowFrom=false duplicateOrConflicting=false issue="No valid X-Frame-Options fallback is present."FAILNo valid X-Frame-Options fallback is present.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=15 sameOriginCount=2 htmlDocumentCount=2WARNCompare observed HTML frame protection actual={"missingOrInvalidFrameProtectionCount":1,"broadFrameAncestorsCount":0,"affected":[{"url":"https://hoxtongin.com/news/","status":200,"resourceType":"document","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

AIO: Source and trust signals

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

10 Fail

Needs attention

AIO: Source and trust signals

Failed check
01

Issue

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

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

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

Agent Ease of UseSkill DiscoveryEmerging recommendation

DNS-AID Agent Discovery

DNS-AID Agent Discovery failed at "Validate HTTPS/SVCB shape".

10 Fail

Needs attention

DNS-AID Agent Discovery

Failed check
01

Issue

One or more DNS-AID records could not be parsed as usable HTTPS/SVCB ServiceMode records.

Details

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

61/100

Status

fail

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 failed at "Validate HTTPS/SVCB shape".

Validation steps

  1. Validate HTTPS/SVCB shape

    One or more DNS-AID records could not be parsed as usable HTTPS/SVCB ServiceMode records.

    Malformed record issues
    [
      {
        "raw": "\\# 136 00 01 00 00 01 00 06 02 68 33 02 68 32 00 04 00 08 68 15 1e c6 ac 43 ad 92 00 05 00 47 00 45 fe 0d 00 41 76 00 20 00 20 14 ce b6 fa d8 da 35 dc 93 26 07 4b ca b4 3e ba d9 98 31 df cb 86 51 41 a6 cd 5e 2d b2 7a a7 0a 00 04 00 01 00 01 00 12 63 6c 6f 75 64 66 6c 61 72 65 2d 65 63 68 2e 63 6f 6d 00 00 00 06 00 20 26 06 47 00 30 32 00 00 00 00 00 00 68 15 1e c6 26 06 47 00 30 35 00 00 00 00 00 00 ac 43 ad 92",
        "ttl": 300,
        "alpn": [],
        "mode": "unknown",
        "params": [
          {
            "key": "00",
            "value": "present"
          },
          {
            "key": "01",
            "value": "present"
          },
          {
            "key": "00",
            "value": "present"
          },
          {
            "key": "00",
            "value": "present"
          },
          {
            "truncated": true,
            "omittedCount": 132,
            "originalCount": 136
          }
        ],
        "rrtype": "HTTPS",
        "source": "cloudflare-doh-json",
        "mandatory": [],
        "ownerName": "_index._agents.hoxtongin.com",
        "targetName": "136",
        "endpointIssue": "missing endpoint",
        "parseWarnings": [
          "SvcPriority is missing or not numeric."
        ],
        "unknownParams": [
          "00",
          "01",
          "00",
          "00",
          {
            "truncated": true,
            "omittedCount": 132,
            "originalCount": 136
          }
        ]
      },
      {
        "raw": "\\# 136 00 01 00 00 01 00 06 02 68 33 02 68 32 00 04 00 08 68 15 1e c6 ac 43 ad 92 00 05 00 47 00 45 fe 0d 00 41 76 00 20 00 20 14 ce b6 fa d8 da 35 dc 93 26 07 4b ca b4 3e ba d9 98 31 df cb 86 51 41 a6 cd 5e 2d b2 7a a7 0a 00 04 00 01 00 01 00 12 63 6c 6f 75 64 66 6c 61 72 65 2d 65 63 68 2e 63 6f 6d 00 00 00 06 00 20 26 06 47 00 30 32 00 00 00 00 00 00 68 15 1e c6 26 06 47 00 30 35 00 00 00 00 00 00 ac 43 ad 92",
        "ttl": 300,
        "alpn": [],
        "mode": "unknown",
        "params": [
          {
            "key": "00",
            "value": "present"
          },
          {
            "key": "01",
            "value": "present"
          },
          {
            "key": "00",
            "value": "present"
          },
          {
            "key": "00",
            "value": "present"
          },
          {
            "truncated": true,
            "omittedCount": 132,
            "originalCount": 136
          }
        ],
        "rrtype": "HTTPS",
        "source": "cloudflare-doh-json",
        "mandatory": [],
        "ownerName": "_a2a._agents.hoxtongin.com",
        "targetName": "136",
        "endpointIssue": "missing endpoint",
        "parseWarnings": [
          "SvcPriority is missing or not numeric."
        ],
        "unknownParams": [
          "00",
          "01",
          "00",
          "00",
          {
            "truncated": true,
            "omittedCount": 132,
            "originalCount": 136
          }
        ]
      }
    ]
  2. Check DNSSEC authentication evidence

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

Evidence log2 steps · 17 lines
Validate HTTPS/SVCB shape [fail]! One or more DNS-AID records could not be parsed as usable HTTPS/SVCB ServiceMode records.INFOValidate HTTPS/SVCB shapeFAILCompare parsed DNS-AID record count actual=2 expected="> 0"FAILCompare ServiceMode record count actual=0 expected="> 0"FAILDNS-AID record has parse/shape warnings ownerName="_index._agents.hoxtongin.com" rrtype="HTTPS" mode="unknown" warnings=["SvcPriority is missing or not numeric."]FAILDNS-AID record has parse/shape warnings ownerName="_a2a._agents.hoxtongin.com" rrtype="HTTPS" mode="unknown" warnings=["SvcPriority is missing or not numeric."]FAILOne or more DNS-AID records could not be parsed as usable HTTPS/SVCB ServiceMode records.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.hoxtongin.com" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.hoxtongin.com" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.hoxtongin.com" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.hoxtongin.com" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.hoxtongin.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.hoxtongin.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="hoxtongin.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNDNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.

AI DiscoverabilityContent ReadinessEstablished

Organization / WebSite schema

Organization / WebSite schema is partially implemented.

10 Warning

Needs attention

Organization / WebSite schema

Warning
01

Issue

No WebSite entity was found in Schema.org structured data. 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

43/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

Identify the site owner and website entity in structured data.

Result

Organization / WebSite schema is partially implemented.

Validation steps

  1. WebSite entity

    No WebSite entity was found in Schema.org structured data.

  2. Identity fields

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

  3. WebSite publisher linkage

    WebSite.publisher is missing.

  4. Organization trust fields

    Organization schema is missing logo.

Evidence log4 steps · 19 lines
WebSite entity [fail]! No WebSite entity was found in Schema.org structured data.INFOWebSite entityINFOLooking for WebSite entity in structured data FAILCheck WebSite entity presence actual=false expected=true fields=[{"name":"WebSite.@type","present":false},{"name":"WebSite.@id","present":false},{"name":"WebSite.name","present":false},{"name":"WebSite.url","present":false},{"name":"WebSite.publisher.@id","present":false},{"name":"WebSite.publisher.name","present":false},{"name":"WebSite.publisher.url","present":false}]FAILWebSite entity is missingIdentity fields [warning]! Missing identity field(s): WebSite.name, WebSite.url.INFOIdentity fieldsINFOChecking Organization and WebSite name/url fields organizationFormat="json-ld"WARNCheck required identity fields actual=2 expected=4 missing=["WebSite.name","WebSite.url"] organizationFields=[{"name":"Organization.@type","present":true,"value":"LocalBusiness","format":"json-ld"},{"name":"Organization.@id","present":false,"format":"json-ld"},{"name":"Organization.name","present":true,"value":"BALIBET","format":"json-ld"},{"name":"Organization.url","present":true,"value":"https://hoxtongin.com/news/","format":"json-ld"},{"name":"Organization.logo","present":false,"format":"json-ld"},{"name":"Organization.sameAs","present":true,"value":["https://www.facebook.com/groups/balibet","https://x.com/balibet","https://www.instagram.com/balibet_official/"],"format":"json-ld"}] websiteFields=[{"name":"WebSite.@type","present":false},{"name":"WebSite.@id","present":false},{"name":"WebSite.name","present":false},{"name":"WebSite.url","present":false},{"name":"WebSite.publisher.@id","present":false},{"name":"WebSite.publisher.name","present":false},{"name":"WebSite.publisher.url","present":false}]WARNCheck identity URLs match scanned origin actual={"organizationUrlMatchesOrigin":true,"websiteUrlMatchesOrigin":false} expected={"organizationUrlMatchesOrigin":true,"websiteUrlMatchesOrigin":true}WARNIdentity fields are partially complete missing=["WebSite.name","WebSite.url"]WebSite publisher linkage [fail]! WebSite.publisher is missing.INFOWebSite publisher linkageINFOChecking whether WebSite.publisher points to the Organization entity organizationFormat="json-ld"FAILCheck publisher presence actual=false expected=true publisher={"present":false,"matchesOrganization":false} website={} organization={"name":"BALIBET","url":"https://hoxtongin.com/news/"}FAILCheck publisher matches Organization actual=false expected=trueFAILWebSite publisher is missingOrganization trust fields [warning]! Organization schema is missing logo.INFOOrganization trust fieldsINFOChecking logo, sameAs, and public contact evidence format="json-ld"FAILCheck logo presence actual=false expected=true fields=[{"name":"Organization.logo","present":false,"format":"json-ld"},{"name":"Organization.sameAs","present":true,"value":["https://www.facebook.com/groups/balibet","https://x.com/balibet","https://www.instagram.com/balibet_official/"],"format":"json-ld"},{"name":"Organization.contactPoint","present":false,"format":"json-ld"},{"name":"Organization.telephone","present":true,"value":"present","format":"json-ld"},{"name":"Organization.email","present":false,"format":"json-ld"},{"name":"Organization.address","present":true,"value":"present","format":"json-ld"}]PASSCheck sameAs or contact evidence actual=4 expected=">= 1" sameAsCount=3 contactSignalCount=1 fields=[{"name":"Organization.logo","present":false,"format":"json-ld"},{"name":"Organization.sameAs","present":true,"value":["https://www.facebook.com/groups/balibet","https://x.com/balibet","https://www.instagram.com/balibet_official/"],"format":"json-ld"},{"name":"Organization.contactPoint","present":false,"format":"json-ld"},{"name":"Organization.telephone","present":true,"value":"present","format":"json-ld"},{"name":"Organization.email","present":false,"format":"json-ld"},{"name":"Organization.address","present":true,"value":"present","format":"json-ld"}]WARNOrganization trust fields are partially complete

Security & TrustSecurity & TrustEstablished

X-Content-Type-Options

X-Content-Type-Options failed at "Find X-Content-Type-Options".

9 Fail

Needs attention

X-Content-Type-Options

Failed check
01

Issue

Browser-loadable response is missing X-Content-Type-Options.

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

57/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 "Find X-Content-Type-Options".

Validation steps

  1. Find X-Content-Type-Options

    Browser-loadable response is missing X-Content-Type-Options.

  2. Review observed browser responses

    One or more same-origin active resources observed by Chrome did not emit X-Content-Type-Options: nosniff.

Evidence log2 steps · 8 lines
Find X-Content-Type-Options [fail]! Browser-loadable response is missing X-Content-Type-Options.INFOFind X-Content-Type-OptionsINFORead X-Content-Type-Options header header="x-content-type-options" value="missing"FAILRequire nosniff header actual="missing" expected="present" issue="Browser-loadable response is missing X-Content-Type-Options."FAILBrowser-loadable response is missing X-Content-Type-Options.Review observed browser responses [warning]! One or more same-origin active resources observed by Chrome did not emit X-Content-Type-Options: nosniff.INFOReview observed browser responsesINFOSample Chrome-observed same-origin resources observedResponseCount=15 sameOriginCount=2 eligibleCount=2WARNCompare observed nosniff coverage actual={"missingNosniffCount":2,"malformedNosniffCount":0,"activeResourceMissingNosniffCount":1,"affected":[{"url":"https://hoxtongin.com/news/","status":200,"resourceType":"document","contentType":"text/html; charset=UTF-8"},{"url":"https://hoxtongin.com/cdn-cgi/rum?","status":404,"resourceType":"xhr","contentType":"text/html; charset=UTF-8"}]} expected="0 missing or malformed eligible same-origin responses" issue="One or more same-origin active resources observed by Chrome did not emit X-Content-Type-Options: nosniff."WARNOne or more same-origin active resources observed by Chrome did not emit X-Content-Type-Options: nosniff.

AI DiscoverabilityBot Access ControlInformational

Content Signal

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

8 Warning

Needs attention

Content Signal

Warning
01

Issue

Declared content usage preferences are valid but partial or include unrecognized extension terms.

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

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

    Declared content usage preferences are valid but partial or include unrecognized extension terms.

Evidence log1 step · 5 lines
Validate declared usage preferences [warning]! Declared content usage preferences are valid but partial or include unrecognized extension terms.INFOValidate declared usage preferencesINFOParsing declared preferences into terms and values recordCount=1INFORecognized declaration formats formats=["legacy-content-signal"] sources=["robots.txt"]WARNCompare valid declarations to declared records actual=1 expected=">= 1 valid declaration with recognized preference terms" invalidRecords=[] warningRecords=[{"source":"robots.txt","directive":"Content-Signal","format":"legacy-content-signal","line":29,"preferences":["search=yes","ai-train=no"],"warnings":["Legacy Content-Signal declaration is partial; missing ai-input."]}]WARNLegacy Content-Signal declaration is partial; missing ai-input. record={"source":"robots.txt","directive":"Content-Signal","format":"legacy-content-signal","line":29,"preferences":["search=yes","ai-train=no"]}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first passages

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

7 Fail

Needs attention

AEO: Answer-first passages

Failed check
01

Issue

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

Details

02

Why it matters

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

Check name

AEO: Answer-first passages

Score

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

AI DiscoverabilityContent ReadinessEstablished

Semantic HTML

Semantic HTML is partially implemented.

7 Warning

Needs attention

Semantic HTML

Warning
01

Issue

Semantic HTML is incomplete: 4 links missing accessible names; 1 links are not crawlable; 1 form controls missing labels.

Details

02

Why it matters

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

Check name

Semantic HTML

Score

59/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. Links

    4 links are missing accessible names.

  3. Form labels and autocomplete

    1 user-fillable form controls are missing labels.

Evidence log3 steps · 9 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":1,"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."Links [fail]! 4 links are missing accessible names.INFOLinksFAILCheck links evidence actual={"counts":{"links":21,"inaccessibleLinks":4,"nonCrawlableLinks":1,"genericLinks":0},"accessibleLinks":false} expected="semantic HTML evidence for this step"FAILLinks failed issue="4 links are missing accessible names."Form labels and autocomplete [fail]! 1 user-fillable form controls are missing labels.INFOForm labels and autocompleteFAILCheck form labels and autocomplete evidence actual={"counts":{"formControls":1,"unlabeledFormControls":1,"autocompleteInputs":0,"inputsWithAutocomplete":0,"missingAutocompleteInputs":0},"formLabelCoverage":false} expected="semantic HTML evidence for this step"FAILForm labels and autocomplete failed issue="1 user-fillable form controls are missing labels."

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: AI retrieval access

GEO: AI retrieval access scored 35/100 and needs a fix.

6 Fail

Needs attention

GEO: AI retrieval access

Failed check
01

Issue

Relevant AI retrieval crawler(s) appear blocked for this URL: ClaudeBot.

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: AI retrieval access

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: AI retrieval access scored 35/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Citable passages

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

6 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

AIO: Page experience proxy

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

5 Warning

Needs attention

AIO: Page experience proxy

Warning
01

Issue

13 image(s) are missing width/height attributes. 3 possible modal/interstitial element(s) 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

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Source and trust signals

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

4 Warning

Needs attention

GEO: Source and trust signals

Warning
01

Issue

Missing source or trust signals: freshnessDate, 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

50/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Evidence and trust

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

4 Fail

Needs attention

AEO: Evidence and trust

Failed check
01

Issue

Missing answer evidence or trust signals: publisher, freshnessDate, 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

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Structured extraction

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

3 Warning

Needs attention

GEO: Structured extraction

Warning
01

Issue

Missing or weak extraction signals: summary or key takeaways, table headers, direct definition sentence.

Details

02

Why it matters

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

Check name

GEO: Structured extraction

Score

63/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question and answer structure

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

3 Warning

Needs attention

AEO: Question and answer structure

Warning
01

Issue

No natural question headings were detected. 6 Q&A structured-data value(s) were not found in visible content.

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

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

AI DiscoverabilityContent ReadinessEstablished

Structured data

Structured data has a validation warning at "Format consistency".

2 Warning

Needs attention

Structured data

Warning
01

Issue

The page mixes structured-data syntaxes. This is allowed when consistent, but a single primary syntax is easier to maintain and debug.

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

90/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

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

Result

Structured data has a validation warning at "Format consistency".

Validation steps

  1. Format consistency

    The page mixes structured-data syntaxes. This is allowed when consistent, but a single primary syntax is easier to maintain and debug.

Evidence log1 step · 4 lines
Format consistency [warning]! The page mixes structured-data syntaxes. This is allowed when consistent, but a single primary syntax is easier to maintain and debug.INFOFormat consistencyINFOComparing structured-data formats and duplicated entity values primaryFormat="mixed"WARNCheck conflicting duplicated entity values actual=0 expected=0 mixedFormats=true formatsFound=["json-ld","microdata"]WARNMultiple structured-data syntaxes are mixed formatsFound=["json-ld","microdata"]

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

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

1 Warning

Needs attention

AEO: Entity and definition clarity

Warning
01

Issue

No direct definition sentence was detected.

Details

02

Why it matters

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

Check name

AEO: Entity and definition clarity

Score

80/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Extractable visible copy

AEO: Extractable visible copy scored 81/100 and needs improvement.

1 Warning

Needs attention

AEO: Extractable visible copy

Warning
01

Issue

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

81/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: Extractable visible copy scored 81/100 and needs improvement.

Security & TrustSecurity & TrustEstablished

HSTS header

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

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

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 AccessibilityAccessibilityBrowser audit

`<html>` element does not have a `[lang]` attribute

100 Fail

Check name

`<html>` element does not have a `[lang]` attribute

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. [Learn more about the `lang` attribute](https://dequeuniversity.com/rules/axe/4.11/html-has-lang).

Evidence
{
  "description": "If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. [Learn more about the `lang` attribute](https://dequeuniversity.com/rules/axe/4.11/html-has-lang)."
}

Performance and AccessibilityBest PracticesBrowser audit

Uses deprecated APIs

100 Fail

Check name

Uses deprecated APIs

Score

0/100

Status

fail

Device

desktop

Category

Best Practices

Estimated savings

1 warning found

Fix guidance

Deprecated APIs will eventually be removed from the browser. [Learn more about deprecated APIs](https://developer.chrome.com/docs/lighthouse/best-practices/deprecations/).

Evidence
{
  "description": "Deprecated APIs will eventually be removed from the browser. [Learn more about deprecated APIs](https://developer.chrome.com/docs/lighthouse/best-practices/deprecations/).",
  "displayValue": "1 warning found"
}

Performance and AccessibilityPerformanceBrowser audit

Image optimization

17 Fail

Check name

Image optimization

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

Review the grouped image optimization checks and improve the failing sub-checks listed in evidence.

Evidence
{
  "checks": [
    {
      "id": "image-aspect-ratio",
      "score": 0,
      "title": "Displays images with incorrect aspect ratio"
    }
  ]
}

Performance and AccessibilityPerformanceBrowser audit

Improve image delivery

17 Fail

Check name

Improve image delivery

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 8,239 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 8,239 KiB"
}

Performance and AccessibilityPerformanceBrowser audit

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

17 Fail

Check name

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. [Learn more about proper list structure](https://dequeuniversity.com/rules/axe/4.11/list).

Evidence
{
  "description": "Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. [Learn more about proper list structure](https://dequeuniversity.com/rules/axe/4.11/list)."
}

Performance and AccessibilityPerformanceBrowser audit

Reduce unused JavaScript

17 Fail

Check name

Reduce unused JavaScript

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 72 KiB

Fix guidance

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

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

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 5,844 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 5,844 KiB"
}

Performance and AccessibilityPerformanceBrowser audit

Loading performance

4 Fail

Check name

Loading performance

Score

77/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": "network-rtt",
      "score": 100,
      "title": "Network Round Trip Times",
      "displayValue": "20 ms",
      "numericValue": 20.1285
    },
    {
      "id": "largest-contentful-paint",
      "score": 1,
      "title": "Largest Contentful Paint",
      "displayValue": "7.3 s",
      "numericValue": 7327.877279565604
    },
    {
      "id": "first-contentful-paint",
      "score": 100,
      "title": "First Contentful Paint",
      "displayValue": "0.5 s",
      "numericValue": 473.0057716673814
    },
    {
      "id": "speed-index",
      "score": 99,
      "title": "Speed Index",
      "displayValue": "0.9 s",
      "numericValue": 857.6752270384679
    },
    {
      "id": "server-response-time",
      "score": 100,
      "title": "Initial server response time was short",
      "displayValue": "Root document took 0 ms",
      "numericValue": 4
    },
    {
      "id": "total-blocking-time",
      "score": 100,
      "title": "Total Blocking Time",
      "displayValue": "0 ms",
      "numericValue": 0
    },
    {
      "id": "interactive",
      "score": 14,
      "title": "Time to Interactive",
      "displayValue": "7.4 s",
      "numericValue": 7360.409297344342
    },
    {
      "id": "max-potential-fid",
      "score": 100,
      "title": "Max Potential First Input Delay",
      "displayValue": "50 ms",
      "numericValue": 50
    }
  ]
}

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
59/100Level 3, Bot-AwareCurrent report