Overall AI readiness score
A combined result across all audit signals.
Average
AI readiness audit: 9/29/2026Public technical data
Overall AI readiness assessment
How ready docs.dynamic.xyz is for AI systems
Dynamic Documentation (docs.dynamic.xyz) received an AI-readiness score of 70/100 in an automated technical audit. llms.txt was accessible, llms-full.txt was accessible, and ai.txt was not found. The robots.txt analysis found 0 explicitly allowed and 0 blocked AI crawlers, with 1 declared sitemap. Homepage markup completeness was 0%; no Schema.org types were detected and 0 OpenGraph tags were detected. Results reflect the public site response observed on 2026-09-29T01:50:05.347Z.
Audit context
llms.txt is accessible and contains 1,126 tokens. An expanded llms-full.txt is also available with 1,116 tokens, giving agents more direct context. No separate ai.txt policy was detected; it is optional, but can clarify training, retrieval, and attribution preferences.
robots.txt is available. 11 of 11 tracked AI bots are not blocked. Declared sitemaps: 1. No Schema.org type was detected on the homepage. 0 OpenGraph tags were found and markup completeness is 0%, leaving more entity interpretation to crawlers.
The mobile Lighthouse profile adds Performance 53/100, Accessibility 92/100, Best Practices 96/100, SEO 100/100, and experimental Agentic Browsing 50/100. These signals have a limited weight: they complement rather than replace llms.txt, robots.txt, and structured-data checks.
Confirmed strengths
- Accessible llms.txt
- Expanded llms-full.txt
- 1 sitemap declaration
Priority improvements
- 1Add JSON-LD for the organisation, website, and core entities.
- 2Complete OpenGraph and canonical homepage metadata.
- 3Reduce mobile rendering delay and main-thread work.
llms.txt tokens1,126
llms-full.txt tokens1,116
ai.txt
sitemap.xml
Google Lighthouse technical profile
A mobile Lighthouse measurement. Google’s experimental Agentic Browsing category is explained separately and does not replace the broader llmsmap AI-readiness score.
53
Performance
92
Accessibility
96
Best Practices
100
Technical SEO
50
Agentic Browsing
What these results mean
Mobile performance is 53/100, with the largest visible content block appearing in 13.2 s and the browser main thread blocked for 370 ms. Layout shift was 0.014. The main thread is where the browser runs JavaScript, calculates layout, and paints the page; long work there delays both user input and browser-agent actions.
Accessibility scored 92/100, Best Practices 96/100, and technical SEO 100/100. The experimental Agentic Browsing category scored 50/100. It measures signals Google currently tests for software agents and is shown separately from the llmsmap AI-readiness score.
1
Free the main thread and accelerate the first view
Split long JavaScript tasks, defer non-critical scripts and styles, and shorten blocking request chains. This helps the primary content appear sooner and makes controls usable earlier.
2
Reduce code that loads without helping the page
Remove unused CSS and JavaScript, load heavy widgets on demand, and limit third-party scripts. Less code means less parsing and background work on the device.
3
Optimise images and their loading order
Serve correctly sized modern formats, prioritise the primary visual, and lazy-load content below the first viewport.
4
Reduce network delay
Improve server response time, remove unnecessary redirects and repeat downloads, and use compression, caching, and selective preconnect hints.
FCP3.5 s
First content
LCP13.2 s
Main content
CLS0.014
Layout stability
TBT370 ms
Blocking time
SI6.5 s
Visual speed
Metric glossary
- FCP · First content
- When the first text or image appeared on screen.
- LCP · Main content
- When the largest visible element in the first viewport rendered.
- CLS · Layout stability
- How much content shifted unexpectedly while loading; lower is better.
- TBT · Blocking time
- How long the browser main thread could not respond quickly to input.
- SI · Visual speed
- How quickly the visible viewport filled with content.
9/29/2026Lighthouse 13.5.0Mobile profile
AI readiness checks
Machine-readable files, crawler policy, discovery, and homepage markup.
ai.txt
ai.txt file was not found
Sitemap in robots.txt1
1 sitemap found
Schema.org (JSON-LD)
Schema.org markup was not found on the homepage
OpenGraph
OpenGraph tags were not found on the homepage
AI bot access
Based on robots.txt analysis
GPTBotNot mentioned
OAI-SearchBotNot mentioned
ChatGPT-UserNot mentioned
Google-ExtendedNot mentioned
ClaudeBotNot mentioned
Claude-SearchBotNot mentioned
Claude-UserNot mentioned
BytespiderNot mentioned
CCBotNot mentioned
PerplexityBotNot mentioned
Perplexity-UserNot mentioned
Sitemaps
Declared discovery routes for crawlers and agents.
# Dynamic Documentation > **Agent navigation guide:** Start here. Fetch only the section file that matches the reader's SDK or task. > Identify the installed SDK generation and task before following an implementation guide. > Fetch the relevant section and prerequisites rather than scanning every file. > API Reference schemas are split across parts; consult them only for type definitions. > Base URL: `https://www.dynamic.xyz/docs` ## Documentation sections - [Get Started](https://www.dynamic.xyz/docs/get-started/llms.txt) (42 pages) — Welcome, developer console, rate limits, go-live checklist, migrations, and troubleshooting - [Embedded Wallets](https://www.dynamic.xyz/docs/embedded-wallets/llms.txt) (30 pages) — MPC embedded wallets: architecture, policies, recovery, delegated access, and chain support - [External Wallets](https://www.dynamic.xyz/docs/external-wallets/llms.txt) (2 pages) — Connect wallets that users bring to your application - [Funding](https://www.dynamic.xyz/docs/funding/llms.txt) (1 page) — Fund wallets through the documented providers and supported methods - [Business Accounts](https://www.dynamic.xyz/docs/business-accounts/llms.txt) (2 pages) — Share embedded wallets across a team, with separate control over who manages the account and who can sign - [Authentication](https://www.dynamic.xyz/docs/auth/llms.txt) (16 pages) — Auth concepts, tokens, MFA, step-up auth, and access control - [Agents](https://www.dynamic.xyz/docs/agents/llms.txt) (4 pages) — Server wallets, agent wallets, and agent payments - [Earn](https://www.dynamic.xyz/docs/earn/llms.txt) (1 page) — Yield vaults - [Fireblocks Flow](https://www.dynamic.xyz/docs/flow/llms.txt) (16 pages) — Accept stablecoin payments, per-SDK integration guides and API - [Platform](https://www.dynamic.xyz/docs/platform/llms.txt) (40 pages) — Developer console, webhooks, social providers, security, and rate limits - [Connections](https://www.dynamic.xyz/docs/connections/llms.txt) (9 pages) — Hosted wallet connection with redirect and headless integrations; capabilities depend on the selected mode - [Recipes](https://www.dynamic.xyz/docs/recipes/llms.txt) (50 pages) — Step-by-step integration recipes, frameworks, and how-tos - [Legacy React SDK](https://www.dynamic.xyz/docs/react/llms.txt) (299 pages) — Maintain existing legacy React integrations; use the JavaScript SDK React quickstart for new applications - [JavaScript SDK](https://www.dynamic.xyz/docs/javascript/llms.txt) (284 pages) — Current JavaScript SDK for JavaScript, React, and React Native - [Legacy React Native SDK](https://www.dynamic.xyz/docs/react-native/llms.txt) (141 pages) — Maintain existing legacy React Native integrations; use the JavaScript SDK React Native quickstart for new applications - [Node.js SDK](https://www.dynamic.xyz/docs/node/llms.txt) (130 pages) — Server-side Node.js SDK for EVM and SVM wallets - [Python SDK](https://www.dynamic.xyz/docs/python/llms.txt) (10 pages) — Server-side Python SDK for EVM and SVM wallets - [Rust SDK](https://www.dynamic.xyz/docs/rust/llms.txt) (10 pages) — Server-side Rust SDK for EVM and SVM wallets (beta) - [Java SDK](https://www.dynamic.xyz/docs/java/llms.txt) (19 pages) — Server-side Java SDK for EVM and SVM wallets (beta) - [Flutter SDK](https://www.dynamic.xyz/docs/flutter/llms.txt) (70 pages) — Flutter/Dart integration - [Swift SDK](https://www.dynamic.xyz/docs/swift/llms.txt) (52 pages) — iOS/macOS Swift integration - [Kotlin SDK](https://www.dynamic.xyz/docs/kotlin/llms.txt) (50 pages) — Android Kotlin integration - [Unity SDK](https://www.dynamic.xyz/docs/unity/llms.txt) (32 pages) — Unity game engine integration - [CLI](https://www.dynamic.xyz/docs/cli/llms.txt) (7 pages) — Command-line tool for environment configuration and dashboard operations - [REST API Reference](https://www.dynamic.xyz/docs/api-reference/llms.txt) (606 pages) — Full REST API — admin endpoints, SDK endpoints, and schema types ## Key entry points - [Welcome](https://www.dynamic.xyz/docs/get-started/welcome.md): Product overview, SDK links, and getting started steps - [React Quickstart](https://www.dynamic.xyz/docs/javascript/reference/react-quickstart.md): Install and run Dynamic in a React app - [JavaScript Quickstart](https://www.dynamic.xyz/docs/javascript/reference/quickstart.md): Vanilla JavaScript integration quickstart - [Go Live Checklist](https://www.dynamic.xyz/docs/get-started/go-live-checklist.md): Pre-launch checklist for production environments
Share or continue the analysis
Share this audit
Discuss with AI
Added 9/29/2026