GA9Z — Gaming Performance Check | ga9z.net
Your monitor's refresh rate sets the FPS target, VRR decides whether the measured number is real, and lag in milliseconds is a separate axis you must measure on its own.
Monitor refresh rates and their matching FPS targets: 60 Hz pairs with a steady 60 FPS, 75 Hz with 75 FPS, 120 Hz with 120 FPS, 144 Hz with 144 FPS, 240 Hz with 240 FPS and 360 Hz with 360 FPS — the figure competitive panels are marketed on. What changes in feel is motion clarity: each step up makes fast tracking visibly cleaner, while the 1% low decides whether that clarity survives the busiest scenes.
VSync versus VRR is the comparison that decides whether a flat frame rate is a setting or a limit. VSync caps the frame rate at the display refresh rate and raises input lag. VRR standards — DisplayPort Adaptive-Sync, optional from 2009 and formal in DisplayPort 1.2a in 2014, AMD FreeSync, Nvidia G-Sync launched in 2014, HDMI 2.1 VRR — remove tearing inside their stated range instead of capping the frame rate, and follow the game's frame rate, for example from 30 Hz through 144 Hz. Standard sync points inside that range include 24, 25, 29.97, 30, 50, 59.94 and 60 FPS.
On narrow screens, swipe or scroll the plate sideways.
Input lag is measured in milliseconds and follows its own thresholds: below 100 ms (a 10 Hz-equivalent) is considered necessary for playability, and demanding online play aims below 20 ms (a 50 Hz-equivalent). These figures describe the whole chain from input to visible response, so a fast GPU does not rescue a slow network route.
The physical floor for network lag is fixed by the speed of light: the lowest physically possible ping for a connection crossing the whole planet is 133 ms. A route that adds much more than that over a short distance is paying for hops and processing, not for distance.
Frame rate and lag are separate axes and a high FPS number does not imply responsive play. Measure each on its own: log your frame figures with the five-step check, then read your ping against the 100 ms and 20 ms thresholds before deciding whether the problem is the PC or the connection.
Further reading