Low frame rates from the browser compositor
Learn how to tell when choppy browser animation comes from compositing, compare graphics performance, and test fixes for acceleration, scaling, and extensions.
A page scrolls in jumps, an animation stutters, or a browser game feels slow, even though the rest of your computer seems fine. One possible cause is the browser compositor, the part that combines page layers, video, and animations into the image you see.
You can compare graphics performance and narrow down whether the problem follows one page, one browser, or your whole computer. The Graphics Test provides a useful comparison, but it does not measure the browser compositor by itself.
Check whether the browser is causing the low frame rate
- Open the Graphics Test in the browser where you notice the stutter. Run it once and note the score. It tests graphics rendering in the browser at 1080p.
- Reproduce the problem in the same browser. Use the same page, window size, zoom level, and action each time, such as scrolling the same section or playing the same animation.
- Try the same page in another browser. Keep the window size and display the same. If only one browser stutters, the issue is more likely tied to that browser, its settings, or an extension than to a general graphics fault.
- Make the browser window smaller and repeat the action. If the motion becomes smoother, the browser may be struggling to compose or draw the larger number of pixels.
- Close other tabs and apps that use video or graphics, then repeat the check. This helps show whether competing work is taking time from the browser.
For a fair comparison, avoid changing several things at once. A different page, window size, browser, and display can all change how smooth an animation looks.
What the result means
The Graphics Test score is low, and other graphics tasks are slow
The computer may have limited graphics performance, or another process may be using its graphics processor, also called the GPU. Close demanding apps and repeat the test. A low score does not prove the GPU is defective, and it does not identify the browser compositor as the cause.
The test looks reasonable, but one page still stutters
The graphics processor can handle the test, but a particular page can still be difficult to render. Large animations, video effects, many transparent layers, or busy scripts can make one site slow. If the same page stutters in every browser, the page itself or the computer's available resources may be the limiting factor.
Only one browser stutters
This points toward that browser's settings, extensions, or a browser-specific bug. Try a private window, where many extensions are disabled by default, or compare after turning extensions off.
Turning graphics acceleration off changes the result
Acceleration lets the browser use the GPU for some drawing and compositing work. If disabling it helps, the browser's accelerated path may be having trouble. If disabling it makes things worse, the computer may rely on the GPU to keep up. Neither result alone proves a hardware failure.
How to fix browser compositor stutter
- Reload the page and close extra tabs. A page can get stuck after a temporary rendering problem, and many open tabs compete for memory and processing time. Close video, animation, and 3D tabs before testing again.
- Turn off extensions for a test. Content blockers, screen capture extensions, and appearance tools can change how pages are drawn. Disable them temporarily, reload the page, and turn them back on one at a time to find a cause.
- Compare hardware acceleration settings. In Chrome, open Settings › System and switch Use graphics acceleration when available. In Edge, open Settings › System and performance and change the same setting. The browser menus are the same on Windows 11 and macOS. Restart the browser after changing it, then repeat the same page test. If it gets worse, restore the original setting.
- Check the display resolution and scaling. A high-resolution display requires the browser to draw more pixels. On Windows 11, check Settings › System › Display. On macOS, open System Settings › Displays. Try the recommended resolution and scaling option, then compare again.
- Update the browser and system. Browser updates can fix rendering bugs. On Windows 11, check Settings › Windows Update. On macOS, check System Settings › General › Software Update. Restart after updates and retest before changing other settings.
- Test with a clean browser profile. If the problem remains in one browser, temporarily use a new profile with no extensions or custom settings. If the page becomes smooth there, the issue is likely in the old profile rather than the graphics hardware.
Why a graphics benchmark cannot confirm a compositor fault
The Graphics Test measures browser-based shading and fill rate, then gives a score out of 100. It is useful for comparing the same computer before and after a change, or for checking whether graphics work is generally slow. It does not reproduce every browser task, such as compositing a page with video, overlays, and many moving layers.
A browser also does not expose a simple, reliable test that can prove the compositor is the specific bottleneck. If the problem affects only one website, report the page, browser version, and steps that reproduce it. If all browsers and other graphics apps also stutter, investigate system load, display settings, and graphics drivers before assuming the browser is at fault.
