Overall AI readiness score
A combined result across all audit signals.
Excellent
AI readiness audit: 9/7/2026Public technical data
Overall AI readiness assessment
How ready docs.de.fi is for AI systems
De.Fi Docs (docs.de.fi) received an AI-readiness score of 75/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-07T00:29:40.997Z.
Audit context
llms.txt is accessible and contains 337 tokens. An expanded llms-full.txt is also available with 10,714 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 80/100, Accessibility 100/100, Best Practices 100/100, SEO 92/100, and experimental Agentic Browsing 100/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
- Strong Google agentic signals
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 tokens337
llms-full.txt tokens10,714
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.
80
Performance
100
Accessibility
100
Best Practices
92
Technical SEO
100
Agentic Browsing
What these results mean
Mobile performance is 80/100, with the largest visible content block appearing in 3.3 s and the browser main thread blocked for 380 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 100/100, Best Practices 100/100, and technical SEO 92/100. The experimental Agentic Browsing category scored 100/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
Clarify search and canonical signals
Verify unique titles and descriptions, crawlability, canonicals, descriptive link text, and language relationships. This reduces ambiguity for search engines and AI systems selecting a page.
FCP2.4 s
First content
LCP3.3 s
Main content
CLS0
Layout stability
TBT380 ms
Blocking time
SI2.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.
9/7/2026Lighthouse 13.4.1Mobile 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.
# De.Fi Docs ## De.Fi Docs - [Introduction](https://docs.de.fi/welcome/readme.md) - [Getting Started](https://docs.de.fi/welcome/getting-started.md) - [The De.Fi Dashboard](https://docs.de.fi/dashboard/the-defi-dashboard.md) - [Address Book](https://docs.de.fi/dashboard/the-defi-dashboard/address-book.md) - [Wallet](https://docs.de.fi/dashboard/the-defi-dashboard/wallet.md) - [Deposit](https://docs.de.fi/dashboard/the-defi-dashboard/deposit.md) - [Lending](https://docs.de.fi/dashboard/the-defi-dashboard/lending.md) - [NFTs](https://docs.de.fi/dashboard/the-defi-dashboard/nfts.md) - [Explore Yields](https://docs.de.fi/dashboard/the-defi-dashboard/explore-yields.md) - [Supported Blockchains](https://docs.de.fi/dashboard/the-defi-dashboard/supported-blockchains.md) - [Supported Protocols](https://docs.de.fi/dashboard/the-defi-dashboard/supported-protocols.md) - [Shield](https://docs.de.fi/security-toolkit/shield.md) - [Scanner](https://docs.de.fi/security-toolkit/scanner.md) - [DEFI Token](https://docs.de.fi/defi-ecosystem/defi-token.md) - [Governance](https://docs.de.fi/defi-ecosystem/governance.md) - [Audit Database](https://docs.de.fi/audits/audit-database.md) - [Rekt Database](https://docs.de.fi/audits/rekt-database.md) - [API](https://docs.de.fi/api/api.md) - [Brand Assets](https://docs.de.fi/resources/brand-assets.md)
Share or continue the analysis
Share this audit
Discuss with AI
Added 9/7/2026