How to interpret shader performance in a browser test

A browser graphics test reports shader performance, fill rate, or a score, and it is not always clear what those numbers mean. A low result does not automatically mean your graphics card is failing, and a high result does not promise a certain frame rate in a game.

The Graphics Test measures shading power and fill rate at 1080p, then gives a score out of 100. Here is how to run it consistently, understand what each result suggests, and decide what to check next.

Run the graphics test

1. Open the Graphics Test on the computer you want to check.
2. Close games, video editors, and other graphics-heavy apps. Pause large downloads or video playback so they do not compete for resources.
3. Run the test and let it finish. Keep the browser tab visible, and avoid moving or resizing the window while it works.
4. Note the shading power, fill rate, and score out of 100. If you want to compare results, record the browser and whether the computer was plugged in.

For a useful comparison, run the same test on the same computer under similar conditions. Repeat it once after the first run, with the computer at a similar temperature. A large change between runs can point to changing power, heat, background activity, or browser conditions, rather than a permanent change in the graphics hardware.

What the result means

Shading power

A shader is a small program that calculates how graphics should look, such as the color, lighting, or texture of a part of an image. Shading power indicates how quickly the graphics processor handles the test's shader work. A higher value means it completed that particular work more quickly. It is not a direct measure of game frame rate, nor does it identify the exact graphics chip.

Fill rate

Fill rate describes how quickly the graphics processor can draw pixel-sized parts of an image in this test. It can be affected by the amount of graphics work per pixel and the speed of the graphics hardware. The test runs at 1080p, but its result is not a promise that every app will draw at that resolution or speed.

The score out of 100

Use the score as a simplified result for this browser test, not as a percentage of the graphics card's maximum capacity. It is not a rating where 80 means the computer is 80 percent as fast as every other computer, and it is not a guaranteed gaming benchmark. Browser graphics tests use a limited workload. Games can use different graphics features, settings, resolutions, and drivers.

If you need to compare a browser benchmark with gaming performance, see Can a browser benchmark predict gaming FPS?

One result is much lower than you expected

A single run cannot tell you whether the graphics processor is faulty. The browser may be using a different graphics processor, hardware acceleration may be off, or the computer may be in a low-power or hot state. Compare repeated runs under the same conditions before drawing a conclusion.

Shading and fill rate do not match

That is not automatically a fault. The two measurements emphasize different parts of the test, and graphics hardware can be stronger at one type of work than another. A difference can also reflect software and power limits. Look for a repeatable pattern rather than expecting the numbers to match.

How to investigate a low or inconsistent result

1. Repeat the test under quiet conditions. Close graphics-heavy apps and unnecessary browser tabs, then run the test again. If the score changes a lot, check for background work or a computer that is getting warm before suspecting hardware.
2. Connect the laptop to power. Battery-saving modes can limit performance. In Windows 11, check Settings › System › Power & battery › Power mode. On a Mac laptop, check System Settings › Battery and turn off Low Power Mode if it is enabled.
3. Check browser graphics acceleration. In Chrome or Edge, open the browser's settings and look under System or System and performance for the graphics acceleration setting. If you change it, restart the browser before testing again. The exact wording can vary by browser version.
4. Check which graphics processor the browser can use. On Windows 11, open Settings › System › Display › Graphics, select the browser, choose Options, and check the available graphics preference. On most Macs, macOS manages graphics selection automatically, so there may not be a per-app choice.
5. Update the browser and system software. On Windows 11, check Settings › Windows Update for updates. On macOS, check System Settings › General › Software Update. If the issue began after a graphics driver change, check the computer maker's recommended driver as well.
6. Compare at the same settings and conditions. Use the same browser, keep the test tab visible, and test at a similar power state. Do not compare a plugged-in run with a battery-powered run and treat the difference as proof of a defect.

What this test cannot diagnose

A browser test cannot confirm that a graphics card is healthy, identify defective video memory, or reproduce every workload in a game or creative app. It measures a specific graphics workload in a browser. A normal score does not rule out an issue that appears only in another program, and a low score alone does not prove that a component is broken.

If other apps also show artifacts, crashes, or sudden slowdowns, note when they happen and check the computer's cooling and graphics driver. If the problem persists across apps after updates and a restart, use the computer maker's diagnostics or have the graphics hardware inspected. The browser result is a clue to compare, not a repair diagnosis.