The server responds slowly

Before the browser can show anything, it waits for the server's first response. If that takes more than a second and a half, visitors look at a blank page for a long time; on mobile many give up, and Google factors loading time into rankings.

We measure the time to the first response for the start page and up to two further pages the scan loads anyway, from our server in Germany. We only report when the start page takes more than 1.8 seconds — the threshold at which web.dev rates the time as “poor” —, a second request for the start page at the end of the scan does too, and the measurements are above it on average. A single slow moment is not enough. Responses from a cache do not count, because there you measure the cache, not the app.