Check your browser frame rate, animation smoothness, frame time, jitter, and stability with a live FPS counter. Start the test, watch the moving canvas scene, and compare current FPS, average FPS, minimum FPS, maximum FPS, dropped frames, and local best.
This Elementor-ready frame rate test is useful for gamers, streamers, browser game players, monitor checks, performance debugging, and anyone who wants to understand whether motion feels smooth or choppy on their current device.
For the cleanest reading, keep this tab visible, close heavy background apps, wait at least 10–30 seconds, and compare results on the same monitor/browser setup.
requestAnimationFrame. It is not the same as an in-game GPU overlay such as Steam, NVIDIA, AMD, Xbox Game Bar, or MSI Afterburner, because browser throttling, tab visibility, power mode, browser zoom, and page load can affect readings.An FPS counter measures frames per second. In simple terms, FPS tells you how many visual frames are drawn every second. Higher FPS usually means smoother motion, lower visual stutter, and more responsive gameplay, especially when the display can actually show those frames.
In gaming, FPS is one of the most common performance numbers. A game running at 30 FPS updates the image about thirty times per second. A game running at 60 FPS updates about sixty times per second. On high refresh rate monitors, 120 FPS, 144 FPS, 165 FPS, 240 FPS, or higher can feel smoother when the monitor supports those refresh rates and the system delivers consistent frame times.
This browser FPS counter works by measuring the time between animation frames. When the browser is ready to repaint the animated canvas, it calls the test loop. The tool records how much time passed since the previous frame, converts that into FPS, and calculates averages, minimums, maximums, frame time, jitter, and long frames.
Raw FPS is useful, but frame pacing is just as important. A game or animation can average 60 FPS while still feeling choppy if frame times jump unevenly. That is why this page includes frame time and jitter. Stable frame timing creates smooth motion. Unstable timing creates stutter even when the average FPS number looks acceptable.
The tool uses a canvas animation and tracks frame timestamps. When the test starts, the page draws a moving scene using the browser’s animation loop. Each frame receives a timestamp. The difference between the current timestamp and the previous timestamp becomes the frame time. The current FPS is calculated from that difference.
To make the reading more useful, the tool does not only show one instant number. It keeps a sample history for the session. It displays average FPS, minimum FPS, maximum FPS, estimated refresh rate, jitter, long frames, and local best average. A long frame is a frame that takes much longer than expected, often causing visible stutter. In this widget, frames above 50 ms are counted as long frames.
The stress scene toggle adds more moving objects to the canvas. This is not a professional GPU benchmark, but it can show whether your browser or device drops frames when more animation work is happening. If normal mode is smooth but stress mode is unstable, your device may be struggling with heavier browser animation.
Shows the latest measured frame rate from the animation loop.
Shows the session average, which is more reliable than a single instant reading.
Shows how many milliseconds the latest frame took. Lower is usually better.
Shows frame-time variation. Lower jitter usually means smoother motion.
Counts frames above 50 ms, which are likely to feel like stutters.
Approximates the display refresh based on recent stable frame intervals.
FPS and frame time are two ways to describe the same performance. FPS is easier for gamers to read, while frame time makes stutter easier to understand.
| FPS | Frame Time | Gaming Feel | Best Use Case |
|---|---|---|---|
| 24 FPS | 41.67 ms | Cinematic but not ideal for responsive gaming. | Video-like motion, older hardware, casual viewing. |
| 30 FPS | 33.33 ms | Playable but less responsive and less smooth. | Console quality modes, low-end systems, slow games. |
| 60 FPS | 16.67 ms | Smooth baseline for most modern gaming. | General gaming, browser games, streaming-friendly gameplay. |
| 90 FPS | 11.11 ms | Very smooth when supported by monitor and hardware. | VR, action games, high refresh displays. |
| 120 FPS | 8.33 ms | Highly responsive and smooth. | Competitive shooters, racing, high refresh monitors. |
| 144 FPS | 6.94 ms | Excellent competitive feel on 144 Hz monitors. | Esports, FPS games, fast camera motion. |
| 240 FPS | 4.17 ms | Extremely responsive if system and display support it. | High-end competitive gaming and low-latency setups. |
FPS matters because games are interactive. The image on screen must update quickly enough for your actions to feel connected. When FPS is low, camera movement looks rough, aim adjustments feel delayed, and fast motion becomes harder to track. When FPS is high and frame pacing is stable, motion feels clearer and inputs feel more immediate.
Competitive games benefit the most from stable high frame rates. In first-person shooters, fighting games, racing games, rhythm games, and battle royale games, small timing differences can affect how quickly you react and how clearly you track motion. A higher FPS does not automatically make you better, but it can reduce visual delay and improve the smoothness of the information you see.
For story games, strategy games, simulation games, and slower RPGs, 60 FPS may already feel excellent. For esports players, 120 FPS or 144 FPS is often preferred because it matches common high-refresh monitors. The best target depends on your monitor refresh rate, hardware power, game type, graphics settings, and whether you value visuals or responsiveness more.
FPS and refresh rate are related but not identical. FPS is how many frames your system or browser produces per second. Refresh rate is how many times your monitor can refresh the image per second, measured in Hertz. A 60 Hz monitor can show up to 60 refreshes per second. A 144 Hz monitor can show up to 144 refreshes per second.
If your game runs at 144 FPS but your monitor is 60 Hz, you may not see all those frames, though input latency can still improve in some situations. If your monitor is 144 Hz but your game runs at 60 FPS, the monitor is capable of more, but the game is not delivering enough unique frames to fill it. Smoothness is best when performance and display capability work together.
Variable refresh rate technologies such as G-SYNC, FreeSync, and Adaptive Sync can help reduce tearing and smooth out varying FPS by matching display refresh behavior to frame delivery. They do not magically create more frames, but they can improve perceived smoothness when frame rate changes during gameplay.
Average FPS can hide problems. Imagine one test averages 60 FPS with every frame near 16.67 ms. That will feel smooth. Another test also averages 60 FPS, but some frames take 8 ms and others take 35 ms. The average may look similar, but the second test feels uneven because frame pacing is inconsistent.
Frame time is often the better troubleshooting number. A sudden frame time spike creates a visible hitch. Jitter is a simple way to describe how much recent frame times vary. Lower jitter usually means more consistent animation. Long frames show serious pauses that are likely to be noticed by the user.
Motion looks rough because not enough frames are produced.
Average FPS can be fine, but uneven timing creates stutter.
Large frame delays feel like hitches, freezes, or sudden jumps.
Lower FPS and long frame times can make controls feel less responsive.
Downloads, recording, streaming, browser tabs, and thermal throttling can affect stability.
Hidden tabs or battery saver modes may reduce animation frequency.
Your monitor may be 60 Hz, browser vsync may limit animation, the OS may be set to 60 Hz, or the test is running on a 60 Hz display.
Most browsers throttle or pause animation callbacks in background tabs to save power and battery.
Look at frame time and jitter. Uneven pacing can feel choppy even if average FPS is high.
Battery saver modes may reduce CPU/GPU speed and browser animation frequency. Plug in or change power mode for testing.
Browser rendering and game rendering are different. Use an in-game overlay for real game performance.
Run the test longer, close background apps, avoid moving windows, and keep the tab visible.
| Use Case | What to Check | Good Result | Warning Sign |
|---|---|---|---|
| Browser Gaming | Average FPS, frame time, jitter. | Stable near monitor refresh rate. | Frequent long frames or unstable jitter. |
| Monitor Setup | Refresh estimate and motion smoothness. | Refresh estimate matches display setting after running. | Estimate stays near 60 on a high-refresh monitor. |
| Performance Debugging | Normal mode vs stress scene. | Small drop under stress. | Large FPS collapse or long frame spikes. |
| Streaming Setup | FPS while streaming or recording. | Stable animation during capture. | Frame pacing worsens when recording starts. |
| Laptop Power Mode | Battery vs plugged-in performance. | Similar stable FPS in preferred mode. | Battery mode heavily throttles animation. |
A browser FPS counter is convenient, but it has limits. It measures animation frames inside the current browser tab. It does not directly measure GPU output from a full-screen game, and it cannot see what your game engine is doing internally. Browser compositing, operating system scheduling, display scaling, extensions, tab visibility, and power-saving features can change results.
The test can still be valuable because browser animation relies on similar smoothness concepts: frame rate, frame time, and pacing. If this page shows heavy jitter or frequent long frames, your device may be overloaded, your browser may be throttled, or your display settings may need checking. But for exact in-game performance, use the game’s built-in FPS counter or a trusted overlay.
For more accurate refresh-rate verification, run the test for longer and compare with specialized display tests. A stable reading needs time. If you just opened the page, the first few seconds may include loading, font rendering, or browser warm-up effects.
This page covers FPS counter, frame rate test, browser FPS test, gaming FPS meter, frame time test, refresh rate test, FPS checker, online FPS counter, animation FPS, requestAnimationFrame FPS, frame pacing, jitter test, dropped frames, long frames, monitor refresh rate, 60 FPS, 120 FPS, 144 FPS, 240 FPS, gaming performance test, browser game performance, and smoothness test.
An FPS counter measures frames per second, which means how many frames are displayed or rendered each second. Higher FPS usually means smoother motion when the display supports it.
It uses a browser animation loop and measures the time between frames. The tool converts frame time into FPS and calculates average FPS, min FPS, max FPS, jitter, and long frames.
No. This tool measures browser animation FPS. For exact game performance, use an in-game counter or a trusted GPU overlay. Browser throttling and tab visibility can affect results.
Your monitor may be 60 Hz, the browser may be synchronized to a 60 Hz display, or the operating system display setting may be set to 60 Hz. Check your monitor refresh-rate settings.
Frame time is how long one frame takes to render, usually measured in milliseconds. Lower frame time means higher FPS. For example, 16.67 ms is about 60 FPS.
Uneven frame pacing can cause choppy motion even when average FPS is high. Look at jitter, frame time spikes, and long frames to understand smoothness better.
60 FPS is a strong baseline for most games. 120 FPS or 144 FPS feels smoother on high-refresh monitors. Competitive players often prefer higher FPS with stable frame times.
Refresh rate does not create FPS, but it limits how many unique frames your display can show per second. A 144 Hz monitor can display more frames than a 60 Hz monitor if your system delivers them.
Browsers often pause or throttle animation callbacks in hidden tabs to save power and battery. Keep the tab visible while testing.
Close background apps, lower graphics settings, update GPU drivers, check temperatures, use the correct monitor refresh rate, and disable power-saving modes when testing performance.
The stress scene adds more moving canvas objects. It is not a full GPU benchmark, but it can reveal browser animation drops under heavier visual workload.
It saves your best average FPS locally in your browser on the same device. It does not sync across devices or create a public leaderboard.
Start the FPS counter, let it run for a while, and compare current FPS, average FPS, frame time, jitter, and long frames. Smooth gaming is about stable frame pacing, not only a big FPS number.