Overall AI readiness score
A combined result across all audit signals.
Average
AI readiness audit: 10/3/2026Public technical data
Overall AI readiness assessment
How ready chakra-ui.com is for AI systems
Chakra UI v3 Documentation for LLMs (chakra-ui.com) received an AI-readiness score of 55/100 in an automated technical audit. llms.txt was accessible, llms-full.txt was not found, and ai.txt was not found. The robots.txt analysis found 0 explicitly allowed and 0 blocked AI crawlers, with 0 declared sitemaps. 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-10-03T08:19:50.980Z.
Audit context
llms.txt is accessible and contains 272 tokens. No accessible llms-full.txt was detected, so deeper context still has to be assembled from regular pages. No separate ai.txt policy was detected; it is optional, but can clarify training, retrieval, and attribution preferences.
robots.txt was not found, so explicit crawler policy could not be confirmed. 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 37/100, Accessibility 85/100, Best Practices 96/100, SEO 91/100, and experimental Agentic Browsing 67/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
Priority improvements
- 1Add llms-full.txt for richer first-party context.
- 2Publish robots.txt with explicit search and AI crawler rules.
- 3Declare the current sitemap.xml in robots.txt.
- 4Add JSON-LD for the organisation, website, and core entities.
llms.txt tokens272
llms-full.txt tokens—
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.
37
Performance
85
Accessibility
96
Best Practices
91
Technical SEO
67
Agentic Browsing
What these results mean
Mobile performance is 37/100, with the largest visible content block appearing in 33.6 s and the browser main thread blocked for 1,600 ms. Layout shift was 0. 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 85/100, Best Practices 96/100, and technical SEO 91/100. The experimental Agentic Browsing category scored 67/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 network delay
Improve server response time, remove unnecessary redirects and repeat downloads, and use compression, caching, and selective preconnect hints.
3
Make controls unambiguous
Give buttons and links accessible names, associate labels with fields, and use ordered headings and semantic regions. The same structure helps screen readers and software agents understand actions.
4
Improve interface contrast and readability
Increase contrast for text, states, and interactive controls so both people and visual agents can distinguish content from actions and supporting labels.
FCP2.2 s
First content
LCP33.6 s
Main content
CLS0
Layout stability
TBT1,600 ms
Blocking time
SI10.8 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.
10/3/2026Lighthouse 13.5.0Mobile profile
AI readiness checks
Machine-readable files, crawler policy, discovery, and homepage markup.
llms-full.txt
Full version was not found
ai.txt
ai.txt file was not found
robots.txt
robots.txt file was not found
Sitemap in robots.txt
Sitemap is not declared in robots.txt
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
# Chakra UI v3 Documentation for LLMs > Chakra UI is an accessible component system for building products with speed ## Documentation Sets - [Complete documentation](https://chakra-ui.com/llms-full.txt): The complete Chakra UI v3 documentation including all components, styling and theming - [Components](https://chakra-ui.com/llms-components.txt): Documentation for all components in Chakra UI v3. - [Charts](https://chakra-ui.com/llms-charts.txt): Documentation for the charts in Chakra UI v3. - [Styling](https://chakra-ui.com/llms-styling.txt): Documentation for the styling system in Chakra UI v3. - [Theming](https://chakra-ui.com/llms-theming.txt): Documentation for theming Chakra UI v3. - [Migrating to v3](https://chakra-ui.com/llms-v3-migration.txt): Documentation for migrating to Chakra UI v3. ## Notes - The complete documentation includes all content from the official documentation - Package-specific documentation files contain only the content relevant to that package - The content is automatically generated from the same source as the official documentation
Share or continue the analysis
Share this audit
Discuss with AI
Added 9/30/2026