How we test
Short and plain, so you can judge our numbers for yourself.
Tested by us
We ran it ourselves. The result names the hardware we used, the date, and the file we ran it on. If we cannot say all three, it does not get the badge.
Not tested
We have not run it. The card shows public facts from the maker's own page and nothing more. Not tested says nothing about quality, good or bad.
Made by us
We built it. Our own tools follow the same rules as everyone else's.
Will it run? numbers
- Frame rate: the median frames per second over 8 seconds of a slow orbit, after a 2 second warm-up. It cannot go above the screen's refresh rate.
- Load time: the time from opening a scene until every splat is on screen.
- JS memory: the page's JavaScript memory as the browser reports it. Many browsers do not share it, and it does not include graphics memory.
- Each result names the device and browser it came from, as the browser reports them.
Your own result depends on your device, your browser, other open tabs and battery settings. Treat one run as one data point.
What we never do
- We never sell a score, a rank or a badge.
- We never publish review text written by automation. A person writes and checks every verdict.
- We never call something tested when we only read about it.
What a computer does help with
A tracker on our server watches makers' release pages and flags changes, so the "last checked" date and the latest release line stay current. A person reviews every change before it shows.
Found a mistake? Tell us.