Run a 20-second browser test to see your frame rate, frame time and 1% low. The result tells you whether your browser and display are running normally — not how many FPS a game will get.
This is a browser FPS test, not a game benchmark. It runs a fixed 2D canvas workload for 20 seconds and reports how many frames your browser renders per second, plus average frame time, 1% low and frame-time consistency. Use it to check that your display, browser and system settings are working normally — a 60Hz display will usually cap the browser near 60 FPS even on a fast GPU. To measure FPS in a game, use the Steam, NVIDIA, AMD or Xbox Game Bar overlay described below.
| What it measures | Average FPS, average frame time, 1% low, slowest frame and frame-time consistency |
|---|---|
| Method | requestAnimationFrame timestamps over a 20-second run |
| Load | Fixed 960×540 canvas with 800 particles and two rotating rings — identical on every device |
| Warm-up | The first 1 second is discarded before measurement starts |
| Requirements | A modern browser with JavaScript and hardware acceleration; keep the tab visible and in front |
| Not measured | Game FPS, your GPU model, or whether an FPS booster will help |
| Last checked | October 19, 2026 |
FPS and frame time are two views of the same thing: FPS is 1000 divided by the average frame time in milliseconds. A 60 FPS result means frames take about 16.7 ms; 120 FPS is about 8.3 ms; 144 FPS is about 6.9 ms. Frame time is the better number when you care about stutter, because an average can hide a few very slow frames.
| Number | What it tells you |
|---|---|
| Average FPS | Frames per second across the measured part of the run. Useful as a headline, but it can hide short hitches. |
| Average frame time | Milliseconds per frame. Lower is smoother; 16.7 ms is 60 FPS, 8.3 ms is 120 FPS. |
| 1% low | The average of the slowest 1% of frames, shown as FPS. This is where stutter shows up: a 60 FPS average with a 30 FPS 1% low will not feel smooth. |
| Slowest frame | The single longest frame. A large spike usually means something interrupted rendering — another tab, a background task, a driver hitch. |
| Observed rate | The typical frame rate during the run. In a browser this usually matches the display's refresh cap, so a 60Hz screen reports about 60 FPS. |
The note under your result uses these numbers to describe the run, not to grade your PC. A stable 60 FPS on a 60Hz display is a normal, healthy browser result; it does not mean your GPU can only run games at 60 FPS.
Every major platform has a built-in overlay. Turn one on, play the same scene for two to three minutes, and note both the average and the 1% low if the overlay shows it. A menu screen is not a benchmark; gameplay is the measurement.
Open Steam > Settings > In Game and set In-game FPS counter to a corner. The counter appears while a game is running. Shift+Tab opens the overlay if you need to change it mid-game.
Press Alt+R to open the performance overlay (or Alt+Z for the main overlay) and enable the metrics you want: FPS, GPU utilization, CPU utilization and latency. Exact labels vary by app version.
Press Ctrl+Shift+O to toggle the performance overlay, or open Performance > Metrics and choose the values you want to see.
Press Win+G, open the Performance widget, and pin it. It can show FPS, GPU, CPU and memory while a game is running.
The browser test draws a light 2D scene; a game draws a full 3D world with lighting, shadows, physics and post-processing. A browser at 60 FPS says nothing about a game at 1440p with ray tracing. If your game FPS is lower than you expect, work through the 12 checks in our low FPS guide — wrong GPU, refresh rate, power, thermals, drivers, background apps, in-game settings and bottlenecks.
If the test shows a stable rate at your display's cap, your browser and display are fine; the bottleneck is in the game or its settings. If it shows a low or unstable rate, close other tabs and apps, check that hardware acceleration is on, plug in a laptop, and run it again. If the game is still slow after the checks, compare boosters in our FPS booster guide — but treat a booster as the last 5%, not the first 50%.
An FPS test measures how many frames a device renders per second. This one uses requestAnimationFrame to time the browser's rendering loop over 20 seconds and reports average FPS, frame time, 1% low and the slowest frame.
It is accurate for what it measures: the browser's rendering rate under a fixed 2D canvas load. It is not a game benchmark, and browsers are usually capped by the display's refresh rate, so a 60Hz screen will show about 60 FPS even on a fast GPU.
Browsers normally synchronize rendering to the display's refresh rate. On a 144Hz monitor, check that Windows is set to 144Hz and that the browser is not running in a power-saving mode; if the test still shows 60, the browser or the page may be capped at 60. The test reports the observed rate, not the monitor's specification.
No. It measures a 2D canvas workload, not a 3D game. Use an in-game benchmark or an overlay such as Steam, NVIDIA, AMD or Xbox Game Bar for game FPS.
Browsers throttle background tabs to save power, so requestAnimationFrame slows down or stops when the tab is hidden. This test pauses and asks you to run it again with the tab visible.
1% low is the average of the slowest 1% of frames, expressed as FPS. It shows how bad the worst moments are; a game can average 60 FPS but have a 1% low of 30 FPS, which feels like stutter.