Overall AI readiness score
A combined result across all audit signals.
Excellent
AI readiness audit: 8/1/2026Public technical data
Overall AI readiness assessment
How ready exstats.com is for AI systems
Exstats (exstats.com) received an AI-readiness score of 95/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 100%; Schema.org types included Organization, WebSite, FAQPage and 10 OpenGraph tags were detected. Results reflect the public site response observed on 2026-08-01T00:40:07.739Z.
Audit context
llms.txt is accessible and contains 686 tokens. An expanded llms-full.txt is also available with 1,961 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. The homepage exposes Schema.org types Organization, WebSite, FAQPage; 10 OpenGraph tags were found and markup completeness is 100%.
The mobile Lighthouse profile adds Performance 89/100, Accessibility 92/100, Best Practices 100/100, SEO 100/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
- Schema.org: Organization, WebSite
- Complete social metadata
- Strong Google agentic signals
Priority improvements
- 1Reduce mobile rendering delay and main-thread work.
llms.txt tokens686
llms-full.txt tokens1,961
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.
89
Performance
92
Accessibility
100
Best Practices
100
Technical SEO
100
Agentic Browsing
What these results mean
Mobile performance is 89/100, with the largest visible content block appearing in 3.7 s and the browser main thread blocked for 40 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 92/100, Best Practices 100/100, and technical SEO 100/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
Optimise images and their loading order
Serve correctly sized modern formats, prioritise the primary visual, and lazy-load content below the first viewport.
4
Reduce network delay
Improve server response time, remove unnecessary redirects and repeat downloads, and use compression, caching, and selective preconnect hints.
FCP0.9 s
First content
LCP3.7 s
Main content
CLS0
Layout stability
TBT40 ms
Blocking time
SI3.1 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/1/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)
Types: Organization, WebSite, FAQPage
OpenGraph100%
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:titleExstats — Browser Extension Analytics for Chrome, Edge & Firefoxog:descriptionMonitor installs, ratings, reviews, and search rankings for 360,000+ browser extensions across Chrome, Edge, and Firefox. Updated daily.og:urlhttps://exstats.comog:site_nameExstatsog:localeen_USog:image:typeimage/jpegog:image:width1200og:image:height630og:typewebsiteSchema.org markup
Structured entities and properties exposed on the homepage.
OrganizationWebSiteFAQPage
nameExstatsurlhttps://exstats.comlogohttps://exstats.com/logo.svgsameAshttps://www.linkedin.com/company/exstatsinLanguageenpublisherhttps://exstats.com# Exstats > Exstats is a browser extension analytics platform that crawls Chrome Web Store, Edge Add-ons, and Firefox Add-ons daily, collecting ratings, users, reviews, categories, rankings, and more for 360,000+ extensions. It helps extension developers and marketers track performance, monitor competitors, research the market, and set up alerts — all from one dashboard. Key concepts: - A **Product** groups listings of the same extension across different stores (e.g. Chrome + Edge + Firefox) and optionally includes competitor extensions for side-by-side comparison - A **Listing** is a specific extension in a specific store — the atomic unit of tracked data - An **Alert** is a monitoring rule attached to a listing that notifies you on changes (rating drops, ranking shifts, field updates) via email or Slack, on a daily/weekly/monthly schedule - **Tracked Keywords** are search terms attached to a product, used to monitor your extension's ranking position in store search results across all three stores - Store metrics differ: Chrome shows weekly active users, Edge shows active install count, Firefox shows average daily users — Exstats shows each as-is without combining them ## Platform - [Products](https://app.exstats.com/products): Create products that group your extension listings across Chrome, Edge, and Firefox. Add competitors. View performance charts, reviews, keyword rankings, and alerts per product. - [Explorer](https://app.exstats.com/explorer): Browse 360,000+ extensions with 30+ filterable and sortable columns including daily deltas (1D, 7D, 30D). Export to CSV/XLSX. - [Trends](https://app.exstats.com/trends): Store-level analytics dashboard showing total extensions, developers, users, review activity, category breakdowns, growing extensions, and rating distributions over time. - [Alerts](https://app.exstats.com/alerts): Manage all alerts across all products in one place. Configure rules (field + condition + value), frequency, and delivery channels. ## Pricing - [Pricing](https://exstats.com/#pricing): Free Starter plan, Pro at $16/mo (billed annually, or $19/mo monthly), Business at $39/mo (billed annually, or $49/mo monthly). No credit card required to start. Enterprise plans available on request. ## Optional - [Blog](https://exstats.com/blog): Insights, guides, and data on browser extension analytics and growth. - [Features](https://exstats.com/#features): Overview of all platform features. - [FAQ](https://exstats.com/#faq): Frequently asked questions about supported stores, data sources, update frequency, regions, and billing. - [Terms of Service](https://exstats.com/terms): Legal terms of service. - [Privacy Policy](https://exstats.com/privacy): Privacy policy.
Share or continue the analysis
Share this audit
Discuss with AI
Added 8/1/2026