#llmsmap.me

Independent technical audit

jazz.tools

jazz.tools

Overall AI readiness score

A combined result across all audit signals.

64of 100Average
AI readiness audit: 9/28/2026Public technical data

Overall AI readiness assessment

How ready jazz.tools is for AI systems

64/100

Documentation (jazz.tools) received an AI-readiness score of 64/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 0 declared sitemaps. 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-09-28T02:19:45.009Z.

Audit context

llms.txt is accessible and contains 1,416 tokens. An expanded llms-full.txt is also available with 84,319 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 was not found, so explicit crawler policy could not be confirmed. 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 94/100, Accessibility 87/100, Best Practices 100/100, SEO 90/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

Priority improvements

  1. 1Publish robots.txt with explicit search and AI crawler rules.
  2. 2Declare the current sitemap.xml in robots.txt.
  3. 3Add JSON-LD for the organisation, website, and core entities.
  4. 4Complete OpenGraph and canonical homepage metadata.
llms.txt tokens1,416
llms-full.txt tokens84,319
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.

Mobile · Lighthouse
94

Performance

87

Accessibility

100

Best Practices

90

Technical SEO

67

Agentic Browsing

What these results mean

The mobile page renders efficiently; its largest visible content block appeared in 2.9 s.

Accessibility scored 87/100, Best Practices 100/100, and technical SEO 90/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

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.

FCP1.8 s

First content

LCP2.9 s

Main content

CLS0.002

Layout stability

TBT10 ms

Blocking time

SI1.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.
9/28/2026Lighthouse 13.5.0Mobile profile

AI readiness checks

Machine-readable files, crawler policy, discovery, and homepage markup.

llms.txt

File found and accessible

https://jazz.tools/llms.txt
llms-full.txt

Full version is available

https://jazz.tools/llms-full.txt
ai.txt

ai.txt file was not found

robots.txt

robots.txt file was not found

Sitemap in robots.txt

Sitemap is not declared in robots.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
# Documentation

- [FAQ](/docs/faq): Frequently asked questions about Jazz.
- [Overview](/docs): The database that syncs.
- [Quickstart](/docs/quickstart): Scaffold a synced local-first app in one command.
- [Authentication](/docs/auth/authentication): Create accounts, authenticate identities, and link ordinary provider JWTs.
- [Lifecycle](/docs/auth/lifecycle): One session owns account selection, graceful client replacement, logout, and recovery.
- [Local-first auth](/docs/auth/local-first-auth): Start offline with a recoverable account, then link an external identity without changing ownership.
- [Permissions](/docs/auth/permissions): Jazz's approach to row-level security using relationship-based access controls, and how to build policies of varying complexity.
- [Sessions](/docs/auth/sessions): Read account ownership, exact authorship, and provider claims from the current session.
- [Branches](/docs/concepts/branches): Model application-owned branches with ordinary columns and head-over-base views.
- [How Sync Works](/docs/concepts/how-sync-works): An overview of how Jazz syncs data between clients, covering query subscriptions, infrastructure tiers, offline behavior, and eventual consistency.
- [Local-First Data Model](/docs/concepts/local-first-data-model): An overview of how Jazz manages local state, row histories, conflicts, and loading behavior.
- [Client Setup](/docs/getting-started/client-setup): Set up Jazz in your app — works out of the box with most frameworks, with manual configuration available when needed.
- [Server Setup](/docs/getting-started/server-setup): Hosted and self-hosted database server configuration, app provisioning, and backend context setup.
- [Client](/docs/install/client): Build a local-first to-do app with Jazz, step by step.
- [TypeScript Server](/docs/install/typescript-server): Build a server-side to-do API with Jazz and Hono, step by step.
- [Testing](/docs/recipes/testing): Patterns for testing Jazz applications.
- [Transactions](/docs/writing/transactions): Group related reads and writes into one mergeable or exclusive transaction.
- [Writing Data](/docs/writing/writing-data): Insert, update, and delete APIs with local-first execution, framework context hooks, and an intro to durability tiers.
- [Column Types](/docs/schemas/column-types): Every column type available in the TypeScript DSL and its SQL equivalent.
- [Defining Tables](/docs/schemas/defining-tables): Define tables and relationships in schema.ts using the TypeScript DSL.
- [Migrations](/docs/schemas/migrations): Change your schema while keeping older clients working.
- [Agent skills](/docs/reference/agent-skills): Project-local guidance installed by create-jazz for coding agents working in a Jazz app.
- [Durability Tiers](/docs/reference/durability-tiers): API reference for read and write durability tiers: the options that control how far data must propagate before an operation confirms.
- [Examples](/docs/reference/examples): What each example app in the Jazz monorepo uniquely demonstrates.
- [Framework Patterns](/docs/reference/framework-patterns): Side-by-side reference for React/Expo, Vue, Svelte, and Solid Jazz APIs.
- [Inspector](/docs/reference/inspector): Standalone admin client for exploring Jazz sync servers, schemas, permissions, and subscriptions.
- [Advanced Internals](/docs/reference/internals): How Jazz works under the hood: raw tables, row histories, sync, the query pipeline, and the browser architecture.
- [Local-first auth internals](/docs/reference/local-first-auth-internals): How a local signing identity founds an offline account and links ordinary provider identities through the core registry.
- [WHERE Operators](/docs/reference/where-operators): Full reference for filter operators available in Jazz query builders, with examples for each column kind.
- [Filters, Sorting & Pagination](/docs/reading/filters-and-sorting): Filter rows with where(), sort with orderBy(), and paginate with limit/offset.
- [Includes & Relations](/docs/reading/includes-and-relations): Resolve references with include(), pick columns with select(), inspect permissions, and run recursive queries.
- [Queries](/docs/reading/queries): One-shot queries, subscriptions, framework hooks, Suspense integration, and read durability options.
- [Auth provider integration](/docs/recipes/auth/auth-provider-integration): Connect an external auth provider to Jazz with JWT validation, with examples for Better Auth and WorkOS.
- [Better Auth Adapter](/docs/recipes/auth/better-auth-adapter): Use Better Auth with Jazz as the database adapter.
- [Nested data with permission inheritance](/docs/recipes/data-patterns/nested-data): Model a project/task/comment hierarchy with inherited permissions, queries, and multi-level inserts.
- [Real-time collaborative list](/docs/recipes/data-patterns/real-time-collaborative-list): Multiple users subscribing to the same data and seeing each other's changes in real-time.
- [Group permissions](/docs/recipes/access-control/group-permissions): Model a workspace with role-based access control using a members table and existence-based permissions.
- [Invite links](/docs/recipes/access-control/invite-links): Let users share a URL that grants another user access to a private resource without knowing their identity in advance.
- [Shared access between users](/docs/recipes/access-control/shared-access): Grant other users access to your data using a shares table and existence-based permissions.
- [User-owned data](/docs/recipes/access-control/user-owned-data): End-to-end walkthrough of the most common Jazz pattern: data that belongs to the user who created it.
Share or continue the analysis
Share this audit
Discuss with AI
Added 9/28/2026
jazz.tools - AI readiness audit | llmsmap.me