Overall AI readiness score
A combined result across all audit signals.
Average
AI readiness audit: 10/6/2026Public technical data
Overall AI readiness assessment
How ready docs.envoyer.io is for AI systems
Envoyer (docs.envoyer.io) received an AI-readiness score of 72/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-10-06T01:04:51.007Z.
Audit context
llms.txt is accessible and contains 311 tokens. An expanded llms-full.txt is also available with 7,263 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 62/100, Accessibility 90/100, Best Practices 100/100, SEO 92/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
- 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 tokens311
llms-full.txt tokens7,263
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.
62
Performance
90
Accessibility
100
Best Practices
92
Technical SEO
67
Agentic Browsing
What these results mean
Mobile performance is 62/100, with the largest visible content block appearing in 11.5 s and the browser main thread blocked for 240 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 90/100, Best Practices 100/100, and technical SEO 92/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.7 s
First content
LCP11.5 s
Main content
CLS0
Layout stability
TBT240 ms
Blocking time
SI5.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/6/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.
# Envoyer - [Introduction](https://docs.envoyer.io/introduction.md): Welcome to Envoyer, a zero downtime deployment service for PHP. - [Quick Start](https://docs.envoyer.io/quick-start.md): There are just a few simple and intuitive steps to get started. - [Source Control](https://docs.envoyer.io/accounts/source-control.md): Connect to source control providers to deploy your projects. - [Your Account](https://docs.envoyer.io/accounts/your-account.md): Learn how to manage your Envoyer account. - [Management](https://docs.envoyer.io/projects/management.md): How to manage your Envoyer projects. - [Servers](https://docs.envoyer.io/projects/servers.md): Learn how Envoyer deploys your projects to servers. - [Deployment Hooks](https://docs.envoyer.io/projects/deployment-hooks.md): Learn how to deploy your projects with Deployment Hooks. - [Heartbeats](https://docs.envoyer.io/projects/heartbeats.md): Learn how to monitor your application's cron jobs. - [Notifications](https://docs.envoyer.io/projects/notifications.md): Receive notifications from Envoyer. - [Collaborators](https://docs.envoyer.io/projects/collaborators.md): Manage who can collaborate on your projects. ## Optional - [Community](https://discord.com/invite/laravel)
Share or continue the analysis
Share this audit
Discuss with AI
Added 9/29/2026