Pages and requests
From the Speed tab, every slow page and every slow request opens its own detail. The tab's filters (environment, time range, device) carry over to the detail.
A page
A page's detail (a route pattern like /checkout) shows:
- Each measure, split into Good, Needs work and Poor: what share of this page's views fell into each band. It's more useful than a single number: a page can have an acceptable 75th percentile and 15% poor views.
- Who's affected: the same measures, split by device, browser or country. It answers whether the problem is phones, a particular browser or a region far from your servers.
- Requests this page makes: the
fetchand XHR calls it made, with their duration. If the page is slow because it waits on an answer, it shows here. - Slow visits: this page's slowest views, each with its device, browser, country and release. Pick one to open the whole visit.
A request
A request's detail (a method and a route pattern, like POST /api/cart) says how long it takes as browsers saw it, from the call's start to its answer. That includes the network, not just your server:
- Duration (75th percentile), Calls and Failed: the share of calls that ended in a server error (5xx) or with no answer.
- Pages that make it: which pages call it.
- Slowest calls: each with when it started within its page, and a link to the visit it came from.
If a request is slow here and fast in your logs, the time is going into the network or the browser, not your server.