Poor16.9%

AWCS

What the AWCS is, and how it is measured

The figures the index is made of, with their own series: a technology whose index is flat can still have moved on one dimension.

Measured on 3,455 pages, 96.5% of which carried the agentic category, with a confidence margin of ±0.90.

▲ +1.6
AWCS over 4 months

10.6%16.9%

Read

What Read measures

Lighthouse builds the accessibility tree an agent would traverse and scores the page pass or fail. The denominator is only the pages the audit could evaluate: a notApplicable or an error is excluded rather than counted as a failure, and the fraction that could be evaluated is published beside it as the coverage.

n=3,455 · coverage 96.5% · margin ±0.90 pp.

53% of the score
Read on its full scale

Poor24.6%

Read: 4 months, up▲ +3.4 pp
Guide

What Guide measures

The llms-txt audit passing: a file is served AND Lighthouse considers it valid. The denominator is every sampled page, so this is a fraction of the whole web and not of the sites that have a file. This is the figure the index uses, because a broken file does not guide an agent.

n=3,580 · coverage 100.0% · margin ±0.89 pp.

27% of the score
Guide on its full scale

Poor14.9%

Guide: 4 months, no significant change= −0.5 pp
Act

What Act measures

A count, not a percentage: how many sampled sites register WebMCP tools that an agent can call. It is the audit that defines the Act dimension — the other two WebMCP audits measure how good those tools are, not whether they exist.

n=3,455 · coverage 96.5% · margin ±0.90 pp.

20% of the score
Act on its full scale

Very poor1.4%

Act: 4 months, no significant change= −0.2 pp
Reachable

What Reachable measures

Read from the robots.txt of the sampled sites: of the AI agents we track, how many are NOT disallowed. Gradual and not a yes or no — turning away one agent out of seventeen is not the same as turning away all of them. A site with no robots.txt blocks nobody, so it counts as fully reachable: that is a measurement, not a gap. This is the only figure that MULTIPLIES the index instead of adding to it, because it is a precondition: if an agent cannot fetch the page, nothing else about the page matters. One caveat we would rather state than hide: a blanket Disallow under User-agent: * is not counted, because the corpus-wide measurement cannot see it either, and we would rather be consistent than clever.

n=3,580 · coverage 100.0% · margin ±0.89 pp.

multiplies the rest
Reachable on its full scale

Excellent97.3%

Reachable: 4 months, no significant change= −0.2 pp

By major version

Does upgrading help? 25 majors of Bootstrap clear the sample gate, oldest first. Each one is measured on its own sites, so a version with few of them carries a wide margin — the tooltip has it.

Bootstrap 0

What Bootstrap 0 measures

The AWCS of the sites where Bootstrap 0 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=36 · coverage 100.0% · margin ±8.83.

Bootstrap 0 on its full scale

Very poor2.9%

Bootstrap 0: 4 months, no significant change= +2.9
Bootstrap 1

What Bootstrap 1 measures

The AWCS of the sites where Bootstrap 1 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=13 · coverage 100.0% · margin ±14.70.

Bootstrap 1 on its full scale

Poor17.3%

Bootstrap 1: 4 months, no significant change= +12.1
Bootstrap 2

What Bootstrap 2 measures

The AWCS of the sites where Bootstrap 2 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=19 · coverage 90.5% · margin ±12.16.

Bootstrap 2 on its full scale

Poor20.2%

Bootstrap 2: 4 months, no significant change= −9.8
Bootstrap 3

What Bootstrap 3 measures

The AWCS of the sites where Bootstrap 3 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=874 · coverage 96.2% · margin ±1.79.

Bootstrap 3 on its full scale

Poor12.6%

Bootstrap 3: 4 months, no significant change= +1.5
Bootstrap 4

What Bootstrap 4 measures

The AWCS of the sites where Bootstrap 4 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=761 · coverage 96.3% · margin ±1.92.

Bootstrap 4 on its full scale

Poor14.8%

Bootstrap 4: 4 months, up▲ +6.1
Bootstrap 5

What Bootstrap 5 measures

The AWCS of the sites where Bootstrap 5 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=345 · coverage 96.1% · margin ±2.85.

Bootstrap 5 on its full scale

Poor15.8%

Bootstrap 5: 4 months, down▼ −3.3
Bootstrap 6

What Bootstrap 6 measures

The AWCS of the sites where Bootstrap 6 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=5 · coverage 100.0% · margin ±23.70.

Bootstrap 6 on its full scale

Weak37.3%

Bootstrap 6: 4 months, no significant change= +8.9
Bootstrap 8

What Bootstrap 8 measures

The AWCS of the sites where Bootstrap 8 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=13 · coverage 100.0% · margin ±14.70.

Bootstrap 8 on its full scale

Fair55.4%

Bootstrap 8: 3 months, up▲ +55.4
Bootstrap 9

What Bootstrap 9 measures

The AWCS of the sites where Bootstrap 9 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=1 · coverage 100.0% · margin ±53.00.

Bootstrap 9 on its full scale

Very poor0.0%

Bootstrap 9: 3 months, no significant change= −46.8
Bootstrap 21

What Bootstrap 21 measures

The AWCS of the sites where Bootstrap 21 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=1 · coverage 100.0% · margin ±53.00.

Bootstrap 21 on its full scale

Very poor0.0%

Bootstrap 21: 2 months, down▼ −53.3
Bootstrap 38

What Bootstrap 38 measures

The AWCS of the sites where Bootstrap 38 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=1 · coverage 100.0% · margin ±53.00.

Bootstrap 38 on its full scale

Fair53.3%

Bootstrap 40

What Bootstrap 40 measures

The AWCS of the sites where Bootstrap 40 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=1 · coverage 100.0% · margin ±53.00.

Bootstrap 40 on its full scale

Excellent100.0%

Bootstrap 41

What Bootstrap 41 measures

The AWCS of the sites where Bootstrap 41 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=1 · coverage 100.0% · margin ±53.00.

Bootstrap 41 on its full scale

Weak26.7%

Bootstrap 48

What Bootstrap 48 measures

The AWCS of the sites where Bootstrap 48 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=1 · coverage 100.0% · margin ±53.00.

Bootstrap 48 on its full scale

Very poor0.0%

Bootstrap 92

What Bootstrap 92 measures

The AWCS of the sites where Bootstrap 92 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=1 · coverage 100.0% · margin ±53.00.

Bootstrap 92 on its full scale

Very poor0.0%

Bootstrap 183

What Bootstrap 183 measures

The AWCS of the sites where Bootstrap 183 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=1 · coverage 100.0% · margin ±53.00.

Bootstrap 183 on its full scale

Very poor0.0%

Bootstrap 0286

What Bootstrap 0286 measures

The AWCS of the sites where Bootstrap 0286 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=1 · coverage 100.0% · margin ±53.00.

Bootstrap 0286 on its full scale

Fair53.3%

Bootstrap 337

What Bootstrap 337 measures

The AWCS of the sites where Bootstrap 337 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=1 · coverage 100.0% · margin ±53.00.

Bootstrap 337 on its full scale

Very poor0.0%

Bootstrap 384

What Bootstrap 384 measures

The AWCS of the sites where Bootstrap 384 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=1 · coverage 100.0% · margin ±53.00.

Bootstrap 384 on its full scale

Fair53.3%

Bootstrap 677

What Bootstrap 677 measures

The AWCS of the sites where Bootstrap 677 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=63 · coverage 100.0% · margin ±6.68.

Bootstrap 677 on its full scale

Fair44.0%

Bootstrap 750

What Bootstrap 750 measures

The AWCS of the sites where Bootstrap 750 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=33 · coverage 97.1% · margin ±9.23.

Bootstrap 750 on its full scale

Fair47.7%

Bootstrap 864

What Bootstrap 864 measures

The AWCS of the sites where Bootstrap 864 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=1 · coverage 100.0% · margin ±53.00.

Bootstrap 864 on its full scale

Excellent80.0%

Bootstrap 2023

What Bootstrap 2023 measures

The AWCS of the sites where Bootstrap 2023 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=1 · coverage 100.0% · margin ±53.00.

Bootstrap 2023 on its full scale

Very poor0.0%

Bootstrap 4412

What Bootstrap 4412 measures

The AWCS of the sites where Bootstrap 4412 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=1 · coverage 100.0% · margin ±53.00.

Bootstrap 4412 on its full scale

Very poor0.0%

Bootstrap 7513

What Bootstrap 7513 measures

The AWCS of the sites where Bootstrap 7513 was detected, on its own sample. Swapping one version for another does not change a site by itself — this says what sites on that version score, which is what makes «does upgrading help?» answerable at all.

n=1 · coverage 100.0% · margin ±53.00.

Bootstrap 7513 on its full scale

Very poor0.0%

Measured, and not part of the index

These are signals, not scores. They are kept apart on purpose: mixed in with the dimensions, a low one reads as a bad grade for something the index never counted.

53.5%
Google's category score

Google's category score

Sample
n=3,453
Coverage
96.5%

The score Lighthouse gives the agentic-browsing category, read from the report as published. We republish it as a declared reference and never as a figure of ours: it includes cumulative-layout-shift — a rendering metric — at half the weight, and its weights are conditional and undocumented. A number whose calculation we do not control is not a number we cite as our own.

Google's category score: 4 months, up▲ +2.0
7.5%
Sites with an AI crawler policy

Sites with an AI crawler policy

Sample
n=3,580
Coverage
100.0%

Not a Lighthouse audit: it is read from the robots.txt of the sampled sites, checking whether the file names any of the AI crawlers we track. It measures HAVING AN EXPLICIT POLICY and not permitting: blocking AI crawlers is a legitimate decision, and penalising it would be a value judgement dressed up as a measurement. What is a sign of maturity is having decided.

Sites with an AI crawler policy: 4 months, no significant change= +0.0 pp
36.8%
Sites serving an llms.txt

Sites serving an llms.txt

Sample
n=3,580
Coverage
100.0%

The same llms-txt audit as the figure below, read differently: this one counts SOMETHING being served at /llms.txt, valid or not. Read that literally, because the distance between the two figures is large and it is the interesting part: of the pages that serve something, fewer than two in five serve a file that parses. Our reading — and we cannot verify it without fetching those files ourselves, which we do not do — is that a good share of the rest are soft 404s: a server answering 200 with an HTML error page. So the figure to cite is the valid one below, and this one is best read as an upper bound. Pages whose audit errored are excluded from both, and the coverage says how many that was.

Sites serving an llms.txt: 4 months, no significant change= +0.2 pp

Against the rest of UI frameworks

The 39 technologies in this category with a published index, and the web overall for scale. Bootstrap is the highlighted bar.

Flutter
Flutter: 51.2%
51.2%
Aura
Aura: 40.0%
40.0%
Mantine
Mantine: 35.6%
35.6%
Radix UI
Radix UI: 30.7%
30.7%
shadcn/ui
shadcn/ui: 30.0%
30.0%
UnoCSS
UnoCSS: 29.2%
29.2%
MUI
MUI: 26.7%
26.7%
Naive UI
Naive UI: 26.7%
26.7%
Flowbite
Flowbite: 26.7%
26.7%
Tailwind CSS
Tailwind CSS: 26.4%
26.4%
Ant Design
Ant Design: 25.5%
25.5%
SvelteKit
SvelteKit: 24.0%
24.0%
Chakra UI
Chakra UI: 22.5%
22.5%
Vuetify
Vuetify: 21.1%
21.1%
Angular Material
Angular Material: 20.0%
20.0%
All sites
All sites: 19.9%
19.9%
Marko
Marko: 17.3%
17.3%
Bootstrap
Bootstrap: 16.9%
16.9%
Headless UI
Headless UI: 16.3%
16.3%
Material Design Lite
Material Design Lite: 15.1%
15.1%
Element UI
Element UI: 14.5%
14.5%
Kendo UI
Kendo UI: 14.4%
14.4%
Panda CSS
Panda CSS: 13.3%
13.3%
Semantic UI
Semantic UI: 13.3%
13.3%
UIKit
UIKit: 12.7%
12.7%
Animate.css
Animate.css: 11.6%
11.6%
ZURB Foundation
ZURB Foundation: 10.4%
10.4%
Base UI
Base UI: 10.0%
10.0%
MDBootstrap
MDBootstrap: 7.9%
7.9%
CivicTheme
CivicTheme: 6.3%
6.3%
Pure CSS
Pure CSS: 5.3%
5.3%
Automatic.css
Automatic.css: 0.0%
0.0%
Bulma
Bulma: 0.0%
0.0%
Clarity
Clarity: 0.0%
0.0%
CoreUI
CoreUI: 0.0%
0.0%
Flat UI
Flat UI: 0.0%
0.0%
Layui
Layui: 0.0%
0.0%
Materialize CSS
Materialize CSS: 0.0%
0.0%
Preline UI
Preline UI: 0.0%
0.0%
W3.CSS
W3.CSS: 0.0%
0.0%
00.250.500.751.0
Every UI frameworks technology the census can publish, against the web overall (19.9%). The scale is always 0–1.

What else we measure here

53.5%
Google's category score

Google's category score

Sample
n=3,453
Coverage
96.5%
7.5%
Sites with an AI crawler policy

Sites with an AI crawler policy

Sample
n=3,580
Coverage
100.0%
97.3%
Agents that can reach the site

Agents that can reach the site

Sample
n=3,580
Coverage
100.0%
24.6%
Pages an agent can parse

Pages an agent can parse

Sample
n=3,455
Coverage
96.5%
36.8%
Sites serving an llms.txt

Sites serving an llms.txt

Sample
n=3,580
Coverage
100.0%
14.9%
Sites with a valid llms.txt

Sites with a valid llms.txt

Sample
n=3,580
Coverage
100.0%
49
Sites exposing tools

Sites exposing tools

Sample
n=3,455
Coverage
96.5%

How this was measured