Is Three.js ready for AI agents?

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=57 · coverage 87.7% · margin ±7.02 pp.

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=65 · coverage 100.0% · margin ±6.57 pp.

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=57 · coverage 87.7% · margin ±7.02 pp.

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=65 · coverage 100.0% · margin ±6.57 pp.

The AWCS of the sites where Three.js 86 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=2 · coverage 100.0% · margin ±37.48.

The AWCS of the sites where Three.js 88 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.

The AWCS of the sites where Three.js 89 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.

The AWCS of the sites where Three.js 105 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.

The AWCS of the sites where Three.js 108 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=2 · coverage 100.0% · margin ±37.48.

The AWCS of the sites where Three.js 111 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.

The AWCS of the sites where Three.js 117 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=2 · coverage 100.0% · margin ±37.48.

The AWCS of the sites where Three.js 127 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=4 · coverage 100.0% · margin ±26.50.

The AWCS of the sites where Three.js 128 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=15 · coverage 93.8% · margin ±13.68.

The AWCS of the sites where Three.js 136 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.

The AWCS of the sites where Three.js 139 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.

The AWCS of the sites where Three.js 147 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=2 · coverage 100.0% · margin ±37.48.

The AWCS of the sites where Three.js 150 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=2 · coverage 66.7% · margin ±37.48.

The AWCS of the sites where Three.js 151 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.

The AWCS of the sites where Three.js 152 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.

The AWCS of the sites where Three.js 157 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.

The AWCS of the sites where Three.js 158 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.

The AWCS of the sites where Three.js 160 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.

The AWCS of the sites where Three.js 169 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=2 · coverage 100.0% · margin ±37.48.

The AWCS of the sites where Three.js 172 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.

The AWCS of the sites where Three.js 175 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=3 · coverage 100.0% · margin ±30.60.

The AWCS of the sites where Three.js 177 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.

The AWCS of the sites where Three.js 180 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.

The AWCS of the sites where Three.js 182 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.

The AWCS of the sites where Three.js 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=2 · coverage 100.0% · margin ±37.48.

The AWCS of the sites where Three.js 184 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=3 · coverage 100.0% · margin ±30.60.

The AWCS of the sites where Three.js 185 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.