FPS Test
Your live frame rate, plus the numbers an average hides — 1% and 0.1% lows, frame time, and how many frames arrived late. Give it ten seconds to settle.
Frame time, newest on the right. Red bars are frames that took more than twice the median — those are the ones you feel.
Why the average is the least useful number
Frame rate is reported as an average almost everywhere, and the average is the figure that correlates worst with how smooth something feels. A session that averages 60 FPS but drops to 12 for one frame in every hundred will look and feel broken — and the average will still say 60.
That is why this test leads with the 1% low and 0.1% low: the frame rate during the slowest 1% and 0.1% of frames. Those are the hitches you actually notice. If your average and your 1% low are close together, delivery is consistent. If they are far apart, you have stutter, regardless of how healthy the average looks.
Reading your result
| Pattern | What it means |
|---|---|
| FPS matches your refresh rate, 1% low close behind | Healthy. Nothing to fix. |
| Exactly 60 on a high-refresh monitor | The panel is set to 60 Hz in the OS. A settings fix, not a hardware limit. |
| Average fine, 1% low far lower | Stutter. Background load, an extension, or thermal throttling. |
| FPS well below refresh rate on an idle page | Something is competing for resources, or battery saver is capping the CPU. |
| Collapses only during the stress test | Device limit rather than display limit. |
The ceiling is your monitor, not your hardware
A browser cannot present frames faster than the screen refreshes. On a 60 Hz display the highest honest reading is 60, however powerful the machine. This catches a lot of people out: a 144 Hz monitor reading exactly 60 almost always means the operating system has it configured at 60 Hz, which is how high-refresh monitors are frequently shipped. The refresh rate test confirms the panel's actual rate in a few seconds.
What this test cannot do
It cannot measure a game's frame rate. A web page has no visibility into another application, so anyone promising in-game FPS from a browser is measuring the browser. For games, use your GPU driver overlay or the game's built-in counter. What this measures — and measures accurately — is the frame delivery pipeline of your display and browser, which is what web performance, scrolling smoothness and video playback actually depend on.
Fixing a low reading
- Check the refresh rate first. Most "low FPS" reports are a monitor sitting at 60 Hz.
- Close other tabs. A single tab running heavy JavaScript steals frames from every other tab.
- Disable extensions temporarily. Some run work on every animation frame.
- Check the power plan. Battery saver caps CPU and GPU aggressively, and laptops often enter it silently.
- Watch for thermal throttling. If FPS starts high and decays over a minute, the device is getting hot.
- Confirm hardware acceleration is on in your browser settings.
If the problem is trails behind moving objects rather than frame count, that is a panel characteristic — the ghosting test covers it. To check the whole display in one pass, run the full monitor test.
More screen tools
Screen Resolution
Detect your display resolution, pixel ratio and viewport instantly.
Full Monitor Test New
Run every display check in one guided sequence and get a summary.
Monitor Size
Work out your physical screen size in inches from its resolution and DPI.
Online Ruler
A calibrated ruler in actual size — cm, mm, inches or pixels.
Refresh Rate Test New
Measure the true refresh rate of your display in Hz, live.
Dead Pixel Test New
Fullscreen solid colours that expose dead, stuck and hot pixels.
Screen Colour Test New
Check colour accuracy, gradients, banding and panel uniformity.
Aspect Ratio Calculator New
Work out and resize any aspect ratio, with a live to-scale preview.
Burn-in Test New
Check OLED and LCD panels for image retention, and try to clear it.
Touch Screen Test New
Find dead zones and check multi-touch by drawing on the screen.
Backlight Bleed Test New
Find light leaking around the edges of an LCD panel.
Ghosting Test New
Check motion blur, trailing and pixel response with moving objects.
Screen Size Comparison New
Put two displays side by side, drawn to true scale.
Frequently asked questions
How do I test my FPS?
The counter above is already measuring it. It times how quickly your browser presents successive frames and converts that into frames per second. Leave it running for ten to twenty seconds so the percentile figures have enough samples to be meaningful.
Why is my FPS capped at 60?
Because a browser cannot present frames faster than the display refreshes. If your screen runs at 60 Hz, 60 is the ceiling no matter how fast your hardware is. Seeing exactly 60 usually means the panel is set to 60 Hz — high-refresh monitors very often ship that way. Check with the refresh rate test.
What are 1% and 0.1% lows?
They are the frame rate during the slowest 1% and 0.1% of frames. An average hides stutter completely: a run averaging 60 FPS that drops to 12 for one frame in a hundred feels broken, and the average never shows it. The lows are the numbers that match what you actually perceive, which is why benchmarks report them.
My average looks fine but the 1% low is much lower. What does that mean?
That is stutter. Frames are arriving unevenly rather than infrequently. Common causes are background applications, a browser extension doing work on every frame, thermal throttling, or a power plan limiting the CPU. A big gap between average and 1% low is far more noticeable than a slightly lower average.
Is a browser FPS test accurate?
For measuring what the browser can present, yes. What it cannot do is measure a game's frame rate — a web page has no visibility into another application. Use your GPU driver overlay or the game's own counter for that. This test measures your display and browser pipeline.
What FPS should I be getting?
On an idle page, your FPS should sit at your monitor's refresh rate — 60 on a 60 Hz screen, 144 on a 144 Hz one. Anything meaningfully below that on a static page points at something competing for resources, not at weak hardware.
What does the stress test do?
It adds continuous animated work so you can see whether frame delivery holds up under load rather than only when the page is idle. If FPS collapses the moment it starts, the bottleneck is your device or browser rather than the display.