FPS Test

How do you use the FPS test?

A frame rate number is useful only when you know what it describes. This browser FPS test gives you a repeatable animation workload, a live frames-per-second reading, and a few extra measurements that show whether motion stays steady. It’s a quick way to check display smoothness and browser graphics performance, although it isn’t a substitute for a game-specific benchmark.

For a useful comparison, keep the same load, duration, browser, and display each time. Then run the test under similar conditions. A single score can be interesting, but a pattern across several runs tells you much more about performance, frame pacing, and the effect of background work.

1. Pick a load level. Low is a gentle starting point for phones and older devices. Medium gives a balanced check, while High and Extreme create more work for stronger hardware and make motion trails easier to inspect.
2. Choose a duration. A 15-second run gives a quick snapshot. Runs of 30, 45, or 60 seconds give the average and 1% low more time to reveal short stutters or heat-related slowdowns.
3. Start the test. The animated scene runs while the dashboard updates with the current frame rate and supporting metrics.
4. Read the result. When the timer ends, compare the average, minimum, maximum, and 1% low FPS. Use the refresh-rate estimate as a clue about the display you tested.

What does each FPS metric mean?

The headline FPS number is only one part of a smoothness check. Average FPS shows the general level, while 1% low FPS and the minimum show what happens during the rough moments. Reading the values together helps you tell the difference between a consistently modest result and a high result interrupted by visible stutter.

1. Frame Rate

   This is the live number of frames produced in the current moment. It’s the FPS value people usually mean when they describe how fast a scene feels.

2. Refresh Rate

   This is an estimate of the display’s refresh rate based on the fastest stable frame rate the test observes. Treat it as a quick Hz clue, not a laboratory measurement.

3. Average FPS

   This is the mean frame rate across the complete run. It gives you the clearest high-level comparison between two tests that use the same settings.

4. 1% Low

   This averages the slowest one percent of the measured frames. A low value beside a strong average often points to brief stutters or uneven frame pacing.

5. Min and Max FPS

   These are the lowest and highest individual readings. A wide gap can show that the workload did not stay even, although one unusual frame can affect the minimum.

6. Pixels Per Frame and Per Sec

   These values describe how many pixels the animation draws per frame and per second. They provide a simple sense of how much visual work the device is handling.

Can you use this as a refresh rate or Hz test?

You can use the result as a quick refresh-rate check. If the frame rate settles near a familiar value such as 60, 120, or 144, that may match the display mode currently active in your browser. However, browser scheduling, power settings, variable refresh rate, another monitor, or a busy tab can affect the reading. Because of that, the number is a useful clue rather than proof of the panel’s advertised maximum.

Close heavy tabs, set the browser zoom to its usual value, and run the test on the exact display you want to check. If you use more than one monitor, move the browser window to the target screen before starting. Repeat the run a few times and look for the value that stays stable instead of relying on the highest single number.

How can you use the FPS test as a ghosting check?

Ghosting is a visible trail behind a moving object when a display’s pixels don’t change quickly enough. To make a basic ghosting check, choose High or Extreme, start the animation, and watch the edges of the moving shapes. A sharp edge is easier to follow, while a pale smear or repeated image can suggest slower pixel response.

This visual check can’t replace a monitor response-time test with a controlled camera and known refresh modes. It can still help you compare two display settings on the same screen. Turn off any motion blur effect you added in the display menu, keep the viewing distance consistent, and remember that room lighting and your own vision can change what you notice.

What is a good FPS for gaming?

The right frame rate depends on the game, the display refresh rate, and the kind of motion you care about. A strategy game may feel fine at 30 FPS, while a competitive shooter benefits from a steadier higher rate. The ranges below are practical reference points, not a promise that every game will feel the same at the same number.

A display can’t show every extra frame beyond its active refresh rate, so the best target is a stable rate that matches the screen. A steady 60 FPS on a 60Hz monitor may feel better than a score that jumps between 80 and 200. If you’re comparing results, prioritize consistency and 1% low FPS as well as the average.

Why does FPS drop during a longer run?

A falling frame rate often means that another process is competing for CPU, GPU, memory, or power. Background tabs, downloads, video playback, battery-saving modes, and thermal limits can all change the result. If the average looks acceptable but the 1% low is much lower, the problem may be short interruptions. If the score gradually falls, heat or power management becomes a more likely clue.

• Close heavy tabs. Video, canvas, and advertising scripts can compete with the test.
• Plug in a laptop. Battery modes can reduce performance to extend runtime.
• Keep the settings the same. Use the same load and duration when comparing devices or browser changes.
• Run it more than once. A repeated pattern is more useful than one unusually high or low score.
• Match the display. Move the browser window to the monitor or phone screen you actually want to inspect.
• Use full screen only when comparing full-screen runs. A larger animation area changes the workload, so record the setting with your result.

Frequently asked questions