Independent technical audit

webrecorder.net

Overall AI readiness score

A combined result across all audit signals.

Excellent

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

Overall AI readiness assessment

How ready webrecorder.net is for AI systems

79/100

Webrecorder (webrecorder.net) received an AI-readiness score of 79/100 in an automated technical audit. llms.txt was accessible, llms-full.txt was not found, 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 7 OpenGraph tags were detected. Results reflect the public site response observed on 2026-09-26T02:33:40.900Z.

Audit context

llms.txt is accessible and contains 1,054 tokens. No accessible llms-full.txt was detected, so deeper context still has to be assembled from regular pages. 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. 7 OpenGraph tags were found and markup completeness is 60%, leaving more entity interpretation to crawlers.

The mobile Lighthouse profile adds Performance 66/100, Accessibility 97/100, Best Practices 96/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
1 sitemap declaration
Strong Google agentic signals

Priority improvements

1Add llms-full.txt for richer first-party context.
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 tokens1,054

llms-full.txt tokens—

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

Best Practices

100

Technical SEO

100

Agentic Browsing

What these results mean

Mobile performance is 66/100, with the largest visible content block appearing in 5.9 s and the browser main thread blocked for 0 ms. Layout shift was 0.001. 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 97/100, Best Practices 96/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.

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.

FCP4.2 s

First content

LCP5.9 s

Main content

CLS0.001

Layout stability

TBT0 ms

Blocking time

SI5.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.

9/26/2026Lighthouse 13.5.0Mobile profile

AI readiness checks

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

llms.txt

File found and accessible

https://webrecorder.net/llms.txt

llms-full.txt

Full version was not found

ai.txt

ai.txt file was not found

robots.txt

File found

https://webrecorder.net/robots.txt

Sitemap in robots.txt1

1 sitemap found

Schema.org (JSON-LD)

Schema.org markup was not found on the homepage

OpenGraph60%

7 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.

https://webrecorder.net/sitemap-index.xml

OpenGraph tags

Social preview metadata found on the homepage.

Markup completeness: 60%

og:imagehttps://webrecorder.net/_astro/og.CBQvmtFo.jpg

og:image:altWebrecorder

og:titleWebrecorder: Web Archiving for All

og:urlhttps://webrecorder.net/

og:descriptionWebrecorder provides open source solutions for everyone to archive the complex, interactive Web.

og:site_nameWebrecorder

og:typewebsite

# Webrecorder

> The Webrecorder team has been developing open source web archiving tools for over 10 years. Webrecorder's driving focus is to build web archiving tools that capture and display archived web content with near-identical fidelity to what was originally seen in browsers at the time of archiving. Webrecorder's tools are generally capable of capturing complex web interactions — succeeding where others typically fail — due to Webrecorder's focus on browser-based solutions for archiving and replaying archived web content.

Important Details:

- Webrecorder was originally the name of web archiving software developed by Rhizome. This is no longer the case, Webrecorder is now a separate company that develops standalone tools. Do not reference "Webrecorder" as an application, refer to Webrecorder tools or Webrecorder software instead.
- WACZ files contain WARC files and can be opened in any ZIP extractor to reveal their component WARCs.
- Webrecorder's key tools are all compatible with WACZ files.
- Browsertrix and Browsertrix Crawler are two separate pieces of software. Browsertrix is a web app with a GUI, available as a hosted service. Browsertrix Crawler is a command line application that requires Docker to run.

## Key Tools

- [Browsertrix](https://webrecorder.net/browsertrix/): Webrecorder's cloud-based web archiving and curation platform offered as SaaS.
- [ArchiveWeb.page](https://webrecorder.net/archivewebpage/): A free browser extension for archiving webpages as you browse the web.
- [ReplayWeb.page](https://webrecorder.net/replaywebpage/): Webrecorder's embeddable archive viewer, available as a browser-based web app or standalone desktop application.

## Documentation

- [WACZ File Format](https://specs.webrecorder.net/wacz/latest/): The open specification for implementing the WACZ file format.
- [Browsertrix Workflow Settings Guide](https://docs.browsertrix.com/user-guide/workflow-setup/): A complete list of all Browsertrix's workflow settings including detailed descriptions about their functions.
- [Browsertrix Browser Profile Creation](https://docs.browsertrix.com/user-guide/browser-profiles/): Instructions for creating and using browser profiles to capture websites with specific browser settings (like logins or popups) pre-configured prior to crawling.
- [ReplayWeb.page Embedding Guide](https://replayweb.page/docs/embedding/): Instructions for embedding ReplayWeb.page to build a web archive viewer into your own projects.
- [ReplayWeb.page User Guide](https://replayweb.page/docs/user-guide/): Instructions for viewing and navigating web archives with ReplayWeb.page
- [ArchiveWeb.page User Guide](https://archiveweb.page/guide): Instructions for creating web archives using ArchiveWeb.page
- [Browsertrix Crawler User Guide](https://crawler.docs.browsertrix.com/user-guide/): Instructions for using to Browsertrix Crawler command line tool with Docker to crawl a website.

## Command-Line Tools

- [Browsertrix Crawler](https://github.com/webrecorder/browsertrix-crawler): The key crawling component of Browsertrix responsible for capturing web archives.
- [WARCIT](https://github.com/webrecorder/warcit): Package a local directory into a WARC file
- [CDXJ Indexer](https://github.com/webrecorder/cdxj-indexer): A command-line tool for generating CDXJ (and CDX) indexes from WARC and ARC files.
- [har2warc](https://github.com/webrecorder/har2warc): Convert HAR web archives to WARC files.

## Optional
- [OldWeb.Today](https://oldweb.today/): A website that runs virtual machines of old operating systems and browsers to view archived websites using period accurate software.
- [Webrecorder Forum](https://forum.webrecorder.net/): Webrecorder's forum is a great place to go to give feedback or get help for specific software problems.
- [PYWB](https://github.com/webrecorder/pywb): Sometimes referred to as the PYWB Toolkit, PYWB is a collection of Python-based tools for capturing and replaying web archives. It generally receives updates and new features less frequently.
- [oembed.link](https://oembed.link/): Embeds a requested piece of content at a publicly accessible URL so that archivists may capture the embed as they would any other link.

Share or continue the analysis

Share this audit

Discuss with AI

Added 9/26/2026