Independent technical audit

llmstxt.org

Overall AI readiness score

A combined result across all audit signals.

Average

AI readiness audit: 7/21/2026Public technical data

Overall AI readiness assessment

How ready llmstxt.org is for AI systems

72/100

llms.txt was independently audited by llmsmap. llmstxt.org currently scores 72/100 for AI readiness. The result combines AI-specific files, crawler policy, sitemap discovery, structured homepage data, and—when available—the mobile Google Lighthouse technical profile.

Audit context

llms.txt is accessible and contains 162 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 is available. 11 of 11 tracked AI bots are not blocked. Declared sitemaps: 1. No Schema.org type was detected on the homepage. 6 OpenGraph tags were found and markup completeness is 40%, leaving more entity interpretation to crawlers.

The mobile Lighthouse profile adds Performance 67/100, Accessibility 97/100, Best Practices 100/100, SEO 100/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
1 sitemap declaration

Priority improvements

1Add llms-full.txt for richer first-party context.
2Add JSON-LD for the organisation, website, and core entities.
3Complete OpenGraph and canonical homepage metadata.
4Reduce mobile rendering delay and main-thread work.

llms.txt tokens162

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.

Mobile · Lighthouse

Performance

Accessibility

100

Best Practices

100

Technical SEO

Agentic Browsing

What these results mean

Mobile performance is 67/100, with the largest visible content block appearing in 5.8 s and the browser main thread blocked for 0 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 97/100, Best Practices 100/100, and technical SEO 100/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.

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.

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.

Optimise images and their loading order

Serve correctly sized modern formats, prioritise the primary visual, and lazy-load content below the first viewport.

Reduce network delay

Improve server response time, remove unnecessary redirects and repeat downloads, and use compression, caching, and selective preconnect hints.

FCP4.1 s

First content

LCP5.8 s

Main content

CLS0

Layout stability

TBT0 ms

Blocking time

SI4.9 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.

7/21/2026Lighthouse 13.4.0Mobile profile

AI readiness checks

Machine-readable files, crawler policy, discovery, and homepage markup.

llms.txt

File found and accessible

https://llmstxt.org/llms.txt

llms-full.txt

Full version was not found

ai.txt

ai.txt file was not found

robots.txt

File found

https://llmstxt.org/robots.txt

Sitemap in robots.txt1

1 sitemap found

Schema.org (JSON-LD)

Schema.org markup was not found on the homepage

OpenGraph40%

6 OG tags found

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.

https://llmstxt.org/sitemap.xml

OpenGraph tags

Social preview metadata found on the homepage.

Markup completeness: 40%

og:titleThe /llms.txt file – llms-txt

og:descriptionA proposal to standardise on using an /llms.txt file to provide information to help LLMs use a website at inference time.

og:imagehttps://llmstxt.org//sample.png

og:site_namellms-txt

og:image:height718

og:image:width1108

# llms.txt

> A proposal that those interested in providing LLM-friendly content add a /llms.txt file to their site. This is a markdown file that provides brief background information and guidance, along with links to markdown files providing more detailed information.

## Docs

- [llms.txt proposal](https://llmstxt.org/index.md): The proposal for llms.txt
- [Python library docs](https://llmstxt.org/intro.html.md): Docs for `llms-txt` python lib
- [ed demo](https://llmstxt.org/ed-commonmark.md): Tongue-in-cheek example of how llms.txt could be used in the classic `ed` editor, used to show how editors could incorporate llms.txt in general.

Share or continue the analysis

Share this audit

Discuss with AI

Added 7/19/2026