Check how quickly a website responds.
Timing a cross-origin request accurately from the browser is unreliable and restricted — this measures the response time from a small WeVivid server endpoint instead, giving a consistent baseline.
A single request can be skewed by momentary network noise. Averaging three gives a more representative figure, though it's still just one measurement location and moment in time.
Under 300ms is generally considered fast for a server response (before the browser renders anything), 300ms-1s is moderate, and over 1 second is worth investigating for a production site.