Why disabling extensions can improve a graphics test

Your graphics test score changes after you turn off browser extensions, or a test runs more smoothly in a fresh browser profile. That can happen even when your graphics hardware has not changed.

Extensions can add work to a page, change how it is drawn, or use browser resources in the background. The Graphics Test gives you a way to compare results under the same conditions and see whether extensions are affecting this browser test.

Compare the graphics test with extensions on and off

1. Open the Graphics Test in the browser you normally use. Keep the browser window in front and close other demanding apps and tabs.
2. Run the test and note the score out of 100. The test measures shading power and fill rate at 1080p, so use the same computer and display setup for each run.
3. Turn off your browser extensions temporarily, then reload the test page and run it again. Do not change the browser, screen resolution, power mode, or other settings between runs.
4. Repeat each condition at least twice. Compare the typical scores, not just the single highest result. If the score changes consistently with extensions off, repeat the comparison after turning them back on.

Some browsers let you use a private window for a quick comparison, but extensions can be allowed in private windows too. A separate browser profile with extensions disabled is a more reliable check.

What the result means

The score is consistently higher with extensions off

An extension may be adding work or interfering with how this page runs. Extensions that inject scripts or visual elements, monitor page activity, or repeatedly update content can compete for browser time. That does not mean the extension has damaged your graphics card, or that the graphics card itself became faster when you disabled it.

Turn extensions back on one at a time and repeat the test to identify a likely cause. The change may apply only to this browser test, not to games or other graphics apps.

The scores are about the same

Your extensions probably are not making a noticeable difference in these test conditions. An extension may only run on certain websites, or its background work may not overlap with the test. Similar scores also do not prove that every extension is harmless in every app.

The score changes in both conditions

Small differences can come from normal run-to-run variation. Browser scheduling, other open tabs, background tasks, and heat can all affect a benchmark. Keep the test in the foreground, let the computer cool between longer runs if it gets warm, and compare several runs before drawing a conclusion.

The test remains slow with extensions off

Extensions are unlikely to be the main cause. A browser graphics test is not a full diagnosis of the graphics card. Browser settings, graphics acceleration, drivers, heat, or other system activity may be involved. A low score alone does not prove that the GPU is faulty.

How to find and fix an extension slowdown

1. Close extra tabs and apps. Other pages, video playback, and demanding applications can compete for processor and graphics time. Close them before each run, and keep the test tab visible.
2. Disable extensions for a comparison. In Chrome on Windows 11 or macOS, open the browser menu and choose Extensions › Manage extensions. In Microsoft Edge on either system, open the menu and choose Extensions › Manage extensions. Turn extensions off temporarily, then reload the test page.
3. Test extensions one at a time. If the score improves with all extensions off, turn them back on individually and rerun the test after each change. This helps separate one extension's effect from the rest. Restore your usual settings when you finish.
4. Check whether an extension affects this site. Some extensions have site access controls or only run on selected pages. If you find a likely cause, adjust its access for the test page if you trust the extension, or leave it disabled while benchmarking.
5. Update the browser and extensions. An outdated version can have bugs or compatibility problems. Update through the browser's built-in update and extension controls, then restart the browser and compare again.
6. Compare with a clean browser profile. Create a temporary profile with no extensions and run the same test there. This can help distinguish an extension issue from a setting or saved profile state. Do not assume a private window is extension-free, since some extensions can be permitted there.

Keep the comparison focused. Changing graphics settings or installing drivers at the same time makes it difficult to tell whether extensions caused the score change. If other browser graphics tests also fail, check browser graphics support and system behavior separately rather than relying on one score.

Why extensions can affect a graphics benchmark

Extensions usually do not directly change the graphics hardware or its driver. Instead, they can change what the browser has to do around a test. For example, an extension might add page elements, run scripts, watch for content, or use processor time in the background. That extra activity can affect when the browser runs the benchmark's work and how consistent the result is.

Not every extension uses graphics resources, and blocking an extension does not guarantee a higher score. Some extensions do almost nothing while the test is running. The useful evidence is a repeatable difference when you change only the extension setting, then see the difference reverse when you restore it.

The Graphics Test score describes performance in this browser workload, not a guaranteed frame rate in a game or the condition of every part of your graphics card.