How to use it
- 1
Paste a public http(s) URL.
- 2
Choose a mobile or desktop strategy.
- 3
Compare start time, duration, and known transfer size for the returned resources.
What the tool can do
- Uses the network-requests audit from the Google PageSpeed Lighthouse response.
- Returns no more than 40 rows and explicitly separates found and returned requests.
- Removes user info, query strings, and fragments from resource URLs.
Common use cases
- Find late-starting or long-running resources in a specific Lighthouse run.
- Compare transfer size and resource type before deeper profiling.
- Check mobile and desktop strategies without exposing the PageSpeed API key to the browser.
How it works inside
The backend validates the URL before calling PageSpeed API with a server-side key.
Response bodies, request/response headers, cookies, screenshots, and traces are excluded from the contract.
Questions and answers
Why are no more than 40 requests shown?
This is an explicit limit for a safe, readable response. The found request count is retained separately.
Why does the URL not include a query string?
WebDiag removes query strings and fragments so tokens and other sensitive parameters from provider payloads are not displayed.