How to get a reliable result
- Plug in a laptop or phone and close games, video and other heavy tabs.
- Press Run benchmark and keep this tab in front. The test stops by itself if you switch tabs or minimise the window, because browsers slow down background tabs and the number would be wrong.
- It runs WebGL 2 for about 7 seconds and then WebGPU for about 7 seconds where your browser has it (10 seconds of WebGL 2 otherwise). The preview shows the scene now and then; with reduced motion turned on in your system it only shows the last frame.
- Run it two or three times. Each run adds a row, so you can see how steady the result is.
What the numbers mean
Median is the typical number of 1920 × 1080 frames the GPU finished per second, and frame time the same figure in milliseconds per frame. Slowest 5% is the frame time only the slowest twentieth of batches exceeded: close to the median means steady clocks; much higher means something interfered, such as another app, thermal throttling or a power limit kicking in.
The shader is a Julia-set fractal computed 160 times per pixel with no shortcuts, so it mostly measures shader arithmetic and how fast the GPU fills pixels. That is what browser games, maps and 3D viewers lean on, but a full GPU benchmark also tests video memory, geometry and ray tracing, which this doesn’t. A software renderer typically manages only a few frames per second: if that is your result, the hardware acceleration notice on this page explains how to fix it.