Testing methodology
Browser tests measure a particular workload on a particular browser. This guide explains how to repeat a run and interpret its limits.
What the numbers measure
FPS counts browser animation callbacks per second. It includes JavaScript, rendering, and browser scheduling. Frame consistency is an index calculated from FPS variation, not a hardware health certificate. A display refresh limit can cap FPS even when the GPU has spare capacity.
A repeatable comparison
Use the same browser version, viewport, zoom, power mode, and workload settings. Close competing tasks, keep the tab visible, allow a short warm-up, then repeat three times. Change one variable at a time; record all results rather than choosing the highest.
Keep a run record
Record the date, browser and OS versions, renderer if available, viewport, workload settings, duration, and FPS readings. Read temperature and clock speed separately with a supported hardware monitor.
How guides are maintained
Guides describe this site's implementation and link to API documentation where relevant. Illustrative examples are labeled; they are not lab measurements. Translations are provided for access to the same information. Send unclear wording or factual corrections to our contact address.
What this test cannot establish
This site cannot read GPU temperature, power draw, clock speed, or utilization through WebGL. Use a separate hardware monitor for those readings. A successful run does not guarantee stability in games, rendering software, or other workloads.