Crawl Response Timing Analyzer

It uses the `loadTime` value recorded by the crawl and compares pages with three- and five-second diagnostic bands. The value reflects the crawler and its environment; it is not a Lighthouse score, user load event, Core Web Vital, or field percentile.

There is no universal threshold that converts this crawl timing into user experience. Use the bands to find relative outliers under the same crawl conditions, then test important pages with controlled lab traces and real-user field data.

No. The displayed size is calculated from captured body-text length, not transferred HTML bytes or total images, CSS, JavaScript, fonts, video, and third-party requests. Use a browser network trace or performance tool for actual transfer sizes.

Yes. An initial guest scan is available without an account. A free account includes 5 scans per month; Pro and Agency plans include unlimited scans. Crawl coverage and timing vary with plan limits, website response, and the crawl environment.

Start with repeatable outliers on important user journeys, not a fixed page-type order. Consider traffic, conversions, task criticality, templates, geography, cache state, devices, networks, and field data before prioritizing work.

No. It does not attribute timing to images, JavaScript, CSS, caching, hosting, third parties, or rendering phases. Capture a trace, identify the dominant delay, test a relevant change, and verify both lab and field effects.