Independent technical audit

litdb.dev

Overall AI readiness score

A combined result across all audit signals.

Average

AI readiness audit: 9/28/2026Public technical data

Overall AI readiness assessment

How ready litdb.dev is for AI systems

66/100

litdb (litdb.dev) received an AI-readiness score of 66/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:05:12.504Z.

Audit context

llms.txt is accessible and contains 583 tokens. An expanded llms-full.txt is also available with 12,064 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: 0. 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 70/100, Accessibility 91/100, Best Practices 100/100, SEO 92/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
Strong Google agentic signals

Priority improvements

1Declare the current sitemap.xml in robots.txt.
2Add JSON-LD for the organisation, website, and core entities.
3Complete OpenGraph and canonical homepage metadata.
4Reduce mobile rendering delay and main-thread work.

llms.txt tokens583

llms-full.txt tokens12,064

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

Performance

Accessibility

100

Best Practices

Technical SEO

100

Agentic Browsing

What these results mean

Mobile performance is 70/100, with the largest visible content block appearing in 8.3 s and the browser main thread blocked for 20 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 100/100, and technical SEO 92/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.

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.

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.

Optimise images and their loading order

Serve correctly sized modern formats, prioritise the primary visual, and lazy-load content below the first viewport.

Reduce network delay

Improve server response time, remove unnecessary redirects and repeat downloads, and use compression, caching, and selective preconnect hints.

FCP2.1 s

First content

LCP8.3 s

Main content

CLS0

Layout stability

TBT20 ms

Blocking time

SI4.9 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://litdb.dev/llms.txt

llms-full.txt

Full version is available

https://litdb.dev/llms-full.txt

ai.txt

ai.txt file was not found

robots.txt

File found

https://litdb.dev/robots.txt

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

# litdb

## Docs

Home
 - [Overview](https://raw.githubusercontent.com/litdb/litdb.dev/refs/heads/main/MyApp/_pages/overview.md)
 - [Install](https://raw.githubusercontent.com/litdb/litdb.dev/refs/heads/main/MyApp/_pages/install.md)
 - [Models](https://raw.githubusercontent.com/litdb/litdb.dev/refs/heads/main/MyApp/_pages/models.md)
 - [Customize](https://raw.githubusercontent.com/litdb/litdb.dev/refs/heads/main/MyApp/_pages/customize.md)
 - [Report Issue](https://raw.githubusercontent.com/litdb/litdb.dev/refs/heads/main/MyApp/_pages/bug-report.md): Creating a good Bug Report

Drivers
 - [SQLite (Bun)](https://raw.githubusercontent.com/litdb/litdb.dev/refs/heads/main/MyApp/_pages/bun-sqlite.md): litdb for Bun SQLite
 - [SQLite (Node.js)](https://raw.githubusercontent.com/litdb/litdb.dev/refs/heads/main/MyApp/_pages/better-sqlite.md): litdb for Node.js better-sqlite3
 - [PostgreSQL](https://raw.githubusercontent.com/litdb/litdb.dev/refs/heads/main/MyApp/_pages/postgres.md): litdb for postgres.js
 - [MySQL](https://raw.githubusercontent.com/litdb/litdb.dev/refs/heads/main/MyApp/_pages/mysql2.md): litdb for mysql2

Queries
 - [Schema](https://raw.githubusercontent.com/litdb/litdb.dev/refs/heads/main/MyApp/_pages/schema.md): Schema APIs
 - [Select](https://raw.githubusercontent.com/litdb/litdb.dev/refs/heads/main/MyApp/_pages/select.md): SELECT Examples
 - [Joins](https://raw.githubusercontent.com/litdb/litdb.dev/refs/heads/main/MyApp/_pages/joins.md): JOIN Examples
 - [Where](https://raw.githubusercontent.com/litdb/litdb.dev/refs/heads/main/MyApp/_pages/where.md): WHERE Examples
 - [Group By](https://raw.githubusercontent.com/litdb/litdb.dev/refs/heads/main/MyApp/_pages/group-by.md): GROUP BY Examples
 - [Having](https://raw.githubusercontent.com/litdb/litdb.dev/refs/heads/main/MyApp/_pages/having.md): HAVING Examples
 - [Order By](https://raw.githubusercontent.com/litdb/litdb.dev/refs/heads/main/MyApp/_pages/order-by.md): ORDER BY Examples
 - [Insert](https://raw.githubusercontent.com/litdb/litdb.dev/refs/heads/main/MyApp/_pages/insert.md): INSERT Examples
 - [Update](https://raw.githubusercontent.com/litdb/litdb.dev/refs/heads/main/MyApp/_pages/update.md): UPDATE Examples
 - [Delete](https://raw.githubusercontent.com/litdb/litdb.dev/refs/heads/main/MyApp/_pages/delete.md): DELETE Examples

Share or continue the analysis

Share this audit

Discuss with AI

Added 9/28/2026