Overall AI readiness score
A combined result across all audit signals.
Average
AI readiness audit: 10/5/2026Public technical data
Overall AI readiness assessment
How ready docs.bucket.co is for AI systems
Reflag docs (docs.bucket.co) received an AI-readiness score of 70/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-05T01:49:47.799Z.
Audit context
llms.txt is accessible and contains 2,440 tokens. An expanded llms-full.txt is also available with 260,860 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 60/100, Accessibility 91/100, Best Practices 96/100, SEO 92/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
- 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 tokens2,440
llms-full.txt tokens260,860
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.
60
Performance
91
Accessibility
96
Best Practices
92
Technical SEO
50
Agentic Browsing
What these results mean
Mobile performance is 60/100, with the largest visible content block appearing in 8.4 s and the browser main thread blocked for 190 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 91/100, Best Practices 96/100, and technical SEO 92/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
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.
FCP3.6 s
First content
LCP8.4 s
Main content
CLS0
Layout stability
TBT190 ms
Blocking time
SI6.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.
10/5/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.
# Reflag docs ## Reflag docs - [Getting started](https://docs.reflag.com/welcome/readme.md) - [Overview](https://docs.reflag.com/supported-languages/overview.md): Reflag SDKs for React, Vue.js, Node.js, Next.js, and more. Supports OpenFeature. - [React SDK](https://docs.reflag.com/supported-languages/react-sdk.md) - [Reference](https://docs.reflag.com/supported-languages/react-sdk/globals.md) - [React Native SDK (beta)](https://docs.reflag.com/supported-languages/react-native-sdk.md) - [Reference](https://docs.reflag.com/supported-languages/react-native-sdk/globals.md) - [Vue SDK (beta)](https://docs.reflag.com/supported-languages/vue-sdk.md) - [Reference](https://docs.reflag.com/supported-languages/vue-sdk/globals.md) - [Browser SDK](https://docs.reflag.com/supported-languages/browser-sdk.md) - [Reference](https://docs.reflag.com/supported-languages/browser-sdk/globals.md) - [Feedback](https://docs.reflag.com/supported-languages/browser-sdk/feedback.md) - [Node.js SDK](https://docs.reflag.com/supported-languages/node-sdk.md) - [Reference](https://docs.reflag.com/supported-languages/node-sdk/globals.md) - [Next.js](https://docs.reflag.com/supported-languages/next.js.md): Next.js client for Reflag - [OpenFeature](https://docs.reflag.com/supported-languages/openfeature.md): Reflag provides OpenFeature integration for use in browser (Web) and Node.js - [Ruby SDK](https://docs.reflag.com/supported-languages/ruby-sdk.md): How to use Reflag with Rails and Stimulus - [API Access](https://docs.reflag.com/api/api-access.md): Understand when to use the Reflag Runtime API and when to use the Reflag Management API - [Runtime API](https://docs.reflag.com/api/public-api.md): Introduction to Reflag Runtime API - [API Reference](https://docs.reflag.com/api/public-api/public-api-reference.md) - [Management SDK](https://docs.reflag.com/api/management-sdk.md) - [Reference](https://docs.reflag.com/api/management-sdk/globals.md) - [Management API](https://docs.reflag.com/api/reflag-rest-api.md): Introduction to Reflag Management API - [API Reference](https://docs.reflag.com/api/reflag-rest-api/reflag-api-reference.md): Describes the Management API that allows clients to manage and update apps, flags, and related entities. - [CLI](https://docs.reflag.com/api/cli.md) - [MCP](https://docs.reflag.com/api/mcp.md): Reflag supports the MCP protocol. Understand how to connect the agent in your code editor to your Reflag account. - [Overview](https://docs.reflag.com/integrations/overview.md): Integrate Reflag with your stack. - [Slack](https://docs.reflag.com/integrations/slack.md): Integrate Slack to get notified about new flag changes and feedback - [Linear](https://docs.reflag.com/integrations/linear.md): Create features and manage access in Linear - [Cursor](https://docs.reflag.com/integrations/cursor.md): How to create feature flags in Cursor - [GitHub](https://docs.reflag.com/integrations/github.md): Integrate GitHub to automatically check feature flag code references and receive automatic AI code clean-up pull requests - [Datadog](https://docs.reflag.com/integrations/datadog.md): How Reflag integrates with Datadog to catch regressions on new feature releases - [PostHog](https://docs.reflag.com/integrations/posthog.md): How Reflag integrates with PostHog to query analytics based on feature access filters - [Segment](https://docs.reflag.com/integrations/segment.md): Use Segment events for tracking feature adoption metrics on Reflag - [Amplitude](https://docs.reflag.com/integrations/amplitude.md): How Reflag integrates with Amplitude to query analytics based on feature access filters - [Mixpanel](https://docs.reflag.com/integrations/mixpanel.md): How Reflag integrates with Mixpanel to query analytics based on feature access filters - [AWS S3](https://docs.reflag.com/integrations/aws-s3.md): Export feature data for CS, Marketing, and Sales tools, via Amazon AWS S3 - [Product overview](https://docs.reflag.com/product-handbook/product-overview.md) - [Flag rollouts](https://docs.reflag.com/product-handbook/feature-rollouts.md): Learn more about flag rollouts in Reflag - [Access rules](https://docs.reflag.com/product-handbook/feature-rollouts/feature-targeting-rules.md): Learn more about access rules in Reflag - [End-user opt-in](https://docs.reflag.com/product-handbook/feature-rollouts/end-user-opt-in.md): Let end users opt themselves or their company into beta and experimental features - [Flag clean-up and archival](https://docs.reflag.com/product-handbook/feature-clean-up-and-archival-beta.md): Managing the flag lifecycle in Reflag is straightforward with the clean-up guide, notifications, and automatic clean-up pull requests. - [AI code clean-up](https://docs.reflag.com/product-handbook/feature-clean-up-and-archival-beta/ai-code-clean-up-beta.md) - [Remote config](https://docs.reflag.com/product-handbook/remote-config.md): Learn more about remote config in Reflag - [Type safety](https://docs.reflag.com/product-handbook/type-safety.md): Reflag offers type safety which reduces errors and frustation - [Team permissions](https://docs.reflag.com/product-handbook/team-permissions.md): Invite, remove and manage roles for your team members - [Notification Policies](https://docs.reflag.com/product-handbook/notification-policies.md): Use notification policies to set defaults on whether to notify Slack and Linear when flag targeting is updated. - [Data residency](https://docs.reflag.com/product-handbook/data-residency.md): Reflag on data residency - [Anonymous users](https://docs.reflag.com/product-handbook/anonymous-users.md): How to use Reflag with anonymous users - [Launch monitor](https://docs.reflag.com/product-handbook/launch-monitor.md) - [Give feedback button](https://docs.reflag.com/product-handbook/launch-monitor/give-feedback-button.md): Adding a feedback button using Reflag SDKs in a few lines of code. - [Automated feedback surveys](https://docs.reflag.com/product-handbook/launch-monitor/automated-feedback-surveys.md): Learn more about automated feedback surveys in Reflag - [Feature entitlements](https://docs.reflag.com/product-handbook/feature-entitlements.md): Learn more about feature entitlements in Reflag - [Simple role-based entitlements](https://docs.reflag.com/product-handbook/feature-entitlements/simple-role-based-entitlements.md): Learn more about simple role-based entitlements in Reflag - [Creating segments](https://docs.reflag.com/product-handbook/creating-segments.md): Learn more about segments in Reflag - [Feature views](https://docs.reflag.com/product-handbook/feature-views.md): Learn more about views in Reflag - [Managing apps](https://docs.reflag.com/product-handbook/creating-and-managing-apps.md): Learn more about apps in Reflag - [Environments](https://docs.reflag.com/product-handbook/creating-and-managing-apps/environments.md): Learn more about environments in Reflag - [Data model](https://docs.reflag.com/product-handbook/concepts.md) - [App](https://docs.reflag.com/product-handbook/concepts/app.md) - [Environment](https://docs.reflag.com/product-handbook/concepts/environment.md) - [Flag](https://docs.reflag.com/product-handbook/concepts/feature.md) - [Flag view](https://docs.reflag.com/product-handbook/concepts/feature-view.md) - [Company](https://docs.reflag.com/product-handbook/concepts/company.md) - [Segment](https://docs.reflag.com/product-handbook/concepts/segment.md) - [User](https://docs.reflag.com/product-handbook/concepts/user.md) - [Track event](https://docs.reflag.com/product-handbook/concepts/event.md) - [Flag events](https://docs.reflag.com/product-handbook/concepts/feature-events.md) - [Feedback](https://docs.reflag.com/product-handbook/concepts/feedback.md) - [Release stage](https://docs.reflag.com/product-handbook/concepts/release-stage.md) - [Targeting rules](https://docs.reflag.com/product-handbook/concepts/targeting-rules.md) - [Filter](https://docs.reflag.com/product-handbook/concepts/filter.md) - [Service Resiliency](https://docs.reflag.com/product-handbook/service-resiliency.md): How Reflag keeps flag evaluation working during service disruptions. - [Flag import](https://docs.reflag.com/product-handbook/flag-import.md): The Reflag import tool lets you quickly migrate all your flags and segments from LaunchDarkly to Reflag - [Use Reflag in your CLI](https://docs.reflag.com/guides/use-reflag-in-your-cli.md): High-level guide to flagging features in your CLI - [Beta feature opt-in](https://docs.reflag.com/guides/self-opt-in.md): Build a beta feature opt-in page with the Reflag React SDK - [Toggle toolbar with a flag](https://docs.reflag.com/guides/toggle-toolbar-with-a-flag.md): Learn how you can control who gets the toolbar in production by toggling a feature flag on/off - [Get support](https://docs.reflag.com/support/get-support.md): Need support? We're here to help --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on a page URL with the `ask` query parameter: ``` GET https://docs.reflag.com/welcome/readme.md?ask=<question> ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
Share or continue the analysis
Share this audit
Discuss with AI
Added 9/30/2026