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 py3.online is for AI systems
Hot Module Reload for Python <https://pypi.org/project/hmr/> was independently audited by llmsmap. py3.online currently scores 67/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 22,986 tokens. The llms-full.txt URL returns an invalid format. It is excluded from the directory; serve text or Markdown instead. A separate ai.txt policy is published.
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 81/100, Accessibility 89/100, Best Practices 100/100, SEO 91/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
- Published AI policy
- 1 sitemap declaration
Priority improvements
- 1Fix llms-full.txt to return text or Markdown instead of HTML.
- 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 tokens22,986
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.
81
Performance
89
Accessibility
100
Best Practices
91
Technical SEO
50
Agentic Browsing
What these results mean
Mobile performance is 81/100, with the largest visible content block appearing in 4.1 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 89/100, Best Practices 100/100, and technical SEO 91/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
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.
FCP3.1 s
First content
LCP4.1 s
Main content
CLS0
Layout stability
TBT0 ms
Blocking time
SI3.2 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-full.txt
Invalid format: the llms-full.txt URL does not return text or Markdown.
https://py3.online/hmr/llms-full.txtSitemap in robots.txt1
1 sitemap found
llms.txt in robots.txt
References: LLM-Policy: /llms.txt
Schema.org (JSON-LD)
Schema.org markup was not found on the homepage
OpenGraph0%
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.
<!DOCTYPE html><html><head><script>window.onload=function(){window.location.href="/lander"}</script></head></html>Share or continue the analysis
Share this audit
Discuss with AI
Added 7/19/2026
Similar sites in the directory
Sites with a close AI-readiness score — compare how they set up llms.txt and markup.