How Can We Help?

Browser-based FPS measurements get pulled around by background tabs, OS processes, GPU drivers, and general browser overhead. Try closing the other tabs and apps, then reload the page fresh before running the test. Your in-game FPS will almost always be noticeably higher than what the browser test shows.

The FPS test measures browser rendering frame rate, not in-game performance. It is a useful baseline for understanding what your display and browser pipeline can do, but the number you get here will not match the FPS counter inside a specific game. Treat it as a sanity check, not a benchmark.

Browser polling rate detection counts mousemove events per second, and some browsers throttle those events for various reasons. Move the mouse smoothly and continuously during the test for the cleanest reading. If your result is lower than the rate printed on the mouse, that is usually a browser limit, not a hardware problem.

For the cleanest result, grab an actual physical ruler, measure exactly how far the mouse moves, and enter that value. Drag the mouse in a straight horizontal line on a flat surface. Run the test two or three times and average the results, since natural hand variation will throw off any single reading.

Press F11 (or Fn plus F11 on a lot of laptops) to put your browser into full screen mode before running the dead pixel test. That makes sure the test pattern covers the whole display. On macOS, use the View menu in your browser to enter full screen.

The browser might be running at a lower refresh rate than the monitor is actually capable of. Common reasons are power saving settings, an HDMI cable that cannot carry full bandwidth at your resolution, or the OS display settings being capped lower than the maximum. Check your display settings and confirm the refresh rate is set to the highest your monitor supports.

No. Every tool on the site runs entirely inside your browser. No performance data, test results, or hardware information ever gets sent to a server. Everything is calculated locally on your device and stays there. There is nothing to log, no database to leak, no profile to build.

Chrome and Microsoft Edge tend to give the most accurate results because the V8 engine implements timing APIs reliably. Firefox and Safari sometimes show slightly different readings since they restrict high-precision timers for privacy reasons. Chrome is the recommendation if you want the most consistent numbers.