Overall AI readiness score
A combined result across all audit signals.
Excellent
AI readiness audit: 8/27/2026Public technical data
Overall AI readiness assessment
How ready aicosts.ai is for AI systems
llms.txt (aicosts.ai) received an AI-readiness score of 85/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 60%; no Schema.org types were detected and 10 OpenGraph tags were detected. Results reflect the public site response observed on 2026-08-27T06:57:47.996Z.
Audit context
llms.txt is accessible and contains 245 tokens. An expanded llms-full.txt is also available with 606 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. 10 OpenGraph tags were found and markup completeness is 60%, leaving more entity interpretation to crawlers.
The mobile Lighthouse profile adds Performance 90/100, Accessibility 96/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
- 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.
llms.txt tokens245
llms-full.txt tokens606
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.
90
Performance
96
Accessibility
100
Best Practices
100
Technical SEO
67
Agentic Browsing
What these results mean
The mobile page renders efficiently; its largest visible content block appeared in 3.1 s.
Accessibility scored 96/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.
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
Reduce network delay
Improve server response time, remove unnecessary redirects and repeat downloads, and use compression, caching, and selective preconnect hints.
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.
FCP1.7 s
First content
LCP3.1 s
Main content
CLS0
Layout stability
TBT40 ms
Blocking time
SI4.3 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.
8/27/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
OpenGraph60%
10 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.
OpenGraph tags
Social preview metadata found on the homepage.
og:titleAICosts.ai | All your AI costs in one dashboardog:descriptionOne dashboard across 50+ AI providers. Upload your billing files for daily spend, model breakdowns, CSV / JSON export.og:urlhttps://www.aicosts.aiog:site_nameAICosts.aiog:localeen_USog:image:width1200og:image:height630og:image:altAICosts.aiog:typewebsite# llms.txt Site: https://aicosts.ai Owner: AICosts.ai Contact: team@aicosts.ai Last-Updated: 2025-07-18 # Purpose AICosts.ai is a comprehensive platform that manages pricing information, provides cost calculators, and comparison tools for AI services and APIs. It helps developers, businesses, and researchers make informed decisions about AI service costs and usage. # Key Features - Real-time pricing data for major AI APIs (OpenAI, Anthropic, Google, etc.) - Interactive cost calculators for token usage and API calls - Price comparison tools across different AI providers - Historical pricing trends and analytics - Cost optimization recommendations - API usage estimation tools - Multi-model pricing breakdowns - Enterprise pricing insights # Permission Requests Contact us at team@aicosts.ai if you wish to request access for research or non-commercial purposes. # Respect open source. Respect contributors. Don't exploit human effort for unapproved model training.
Share or continue the analysis
Share this audit
Discuss with AI
Added 8/27/2026