Where the data comes from and how the math works

Game requirements and readiness

• Official requirements come from publisher and platform pages when they exist.
• Before official data exists, requirements are a labeled prediction based on comparable games.
• GPUs and CPUs sit on a shared numeric tier scale so parts can be compared across games.
• A readiness verdict compares your parts to the minimum and recommended profiles, capped by your weakest part.

Sensitivity conversion

Conversions preserve cm/360, the physical distance your mouse travels for a full turn, or eDPI where that is the better match. Games that use a linear yaw convert cleanly. Games with a non-linear scale, like Fortnite, are converted to a close starting point and labeled as an estimate, because an exact feel cannot be guaranteed across different scales.

Minecraft and download math

• Shader and server-hosting estimates use device tier, player count, and view distance as inputs.
• Download time uses file size and connection speed, with a real-world efficiency factor because links rarely hit their rated speed.
• These are estimates for planning, not guarantees for a specific network or save file.

Server status

Status pages combine anonymous player reports with a link to each service's official status page. A service is flagged when reports spike above a threshold and recovers when they fall back. This is a community signal plus the authoritative source, not a private feed from the publisher. When a service has no reliable data, its page says so instead of inventing a status.

Benchmark scores

The in-browser benchmark runs a short GPU workload and produces a relative score, then frames it against game targets. A score describes the machine and browser it ran on, so results vary with drivers, thermals, and background load. Benchmarked claims are labeled as such.

For how these methods turn into the verdicts you see, readhow FrameReady works.