WebmasterID logoWebmasterID
Search bots

Lighthouse and PageSpeed Insights fetchers

Lighthouse is Google's open-source page-quality auditing tool, and PageSpeed Insights is the hosted service that runs Lighthouse audits and reports field and lab performance data. Both fetch a page on demand to measure it, not to index it for search. Their fetches are user-triggered performance audits and appear in logs as a single page load with related resource requests, not a crawl.

Verified against primary sources

What this means

Lighthouse audits a page for performance, accessibility, SEO, and best practices. PageSpeed Insights runs Lighthouse on Google's infrastructure and combines it with real-user field data from the Chrome User Experience Report. When you test a URL, the service loads that page and its resources to measure them.

This is measurement, not indexing. Running PageSpeed Insights does not crawl your site and does not change rankings by itself; it reports how the tested page performs.

How it appears in logs

An on-demand audit appears as a load of the tested URL plus the resources that page references — scripts, stylesheets, images — usually from Google's PageSpeed infrastructure when run via the hosted service. It is a single-page event, not a multi-page crawl.

Lighthouse run locally (in Chrome DevTools or the CLI) originates from the operator's own environment, so it may not look like Google traffic at all. The reliable signal is the single-URL, resource-heavy audit pattern rather than a broad crawl.

How it appears in analytics and logs

A Lighthouse or PageSpeed Insights fetch means someone ran a performance audit of one URL. It is a measurement fetch, not a crawl and not a human visit; treat it as automation triggered by a person.

Diagnostic use case

Recognise performance-audit fetches from Lighthouse and PageSpeed Insights in logs, separate them from search crawling, and avoid counting them as audience.

What WebmasterID can help detect

WebmasterID classifies performance-audit fetches server-side as bot/automation traffic, so audits do not inflate human analytics or look like search-crawl coverage.

Common mistakes

Privacy and accuracy notes

Identification uses the request user-agent and audit context only. Although a person triggered the audit, no visitor identity is exposed; WebmasterID records it as a bot/automation event.

Related pages

Sources and verification notes

Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.