GPU test score in a remote session: what to check

Your gaming desktop may feel fast at its desk but sluggish through a remote session. A low browser graphics score can point to the remote display path or browser settings, not necessarily a failing graphics card.

Use the Graphics Test to compare its 1080p shading and fill-rate results. The test runs on the computer where the browser is running, so first make sure you know whether that is the gaming desktop or the device you are connecting from.

Compare the GPU score locally and remotely

1. Open the Graphics Test in a browser on the gaming desktop itself. If you are using a remote desktop app, open the browser inside the session on the desktop, not on your local laptop or tablet.
2. Close games, video editors, GPU benchmarks, and other demanding apps. Keep the desktop plugged into power and use the same browser for each run.
3. Run the test at the desktop, if you can access its physical screen. Note the shading and fill-rate scores, then run the test again in the remote session on that same desktop.
4. Keep the remote session at a similar display resolution if possible. Record whether the scores are both lower remotely or whether one result changes more than the other.

If you cannot use the desktop screen directly, compare repeated runs in the remote session after closing other apps. Treat that as a useful check of the current setup, not a direct comparison with local performance.

What the score means

The local and remote scores are close

The browser is getting similar graphics performance in both situations. Small changes between runs are normal because background activity, browser timing, and system load can vary. A close score does not prove that every game will run equally well remotely, since the remote connection adds its own delays and video encoding.

The remote score is much lower

The session may be using a virtual display adapter, a different graphics path, or a lower-power graphics option. Remote desktop software can also change the resolution and how the desktop is drawn. This result alone does not show that the gaming GPU is defective.

Both scores are low

The cause may affect the desktop in either session, such as a browser using software rendering, a power-saving setting, another app using the GPU, or heat-related slowdown. Compare the result with what you normally expect from this same computer, not with an unrelated PC's score.

The score changes sharply between runs

Something may be competing for graphics time, or the desktop may be switching power or performance states. A browser test is a short workload, so it cannot show the exact cause or predict a game's frame rate by itself.

How to fix a low remote score

1. Close other graphics-heavy apps. Exit games, video playback, streaming software, and other benchmarks before testing. Also close extra remote sessions if they are displaying the same desktop.
2. Check that the browser uses graphics acceleration. In Chrome, open Settings › System and turn on Use graphics acceleration when available, then restart the browser. In Edge, look under Settings › System and performance for the same setting. Menu labels can vary by browser version.
3. Prefer the gaming GPU in Windows. On Windows 11, open Settings › System › Display › Graphics, select or add the browser, choose Options, and select High performance if that choice is available. Restart the browser and test again. This setting may not override how a remote session assigns its display adapter.
4. Try a practical remote display resolution. Set the remote desktop to a resolution the gaming PC can handle comfortably. A very high resolution can add graphics work, while a low resolution can change the test conditions. Keep the same resolution when comparing runs.
5. Reconnect the remote session. End the session fully and connect again. If the score improves only after reconnecting, the session may have started with a different graphics or display configuration.
6. Update the graphics driver and browser. Use the desktop manufacturer's or graphics-card manufacturer's supported update process. Restart Windows afterward, then compare the local and remote scores again.

On macOS, a browser's graphics acceleration option is in its own settings, not a matching Windows graphics preference. If you are testing a Mac host, run the browser locally on that Mac as a baseline, then compare it with the remote session.

When the graphics card may be the problem

Suspect a broader graphics problem if the local score is consistently far below that computer's usual result, and you also see glitches, crashes, missing textures, or poor performance in locally running games. A browser score cannot diagnose a faulty graphics card or its memory. Check for driver and cooling problems first, and seek repair or warranty service if the symptoms continue across several local apps.

Why remote sessions can change the result

A remote desktop sends a picture of the desktop to another device. Depending on the app, driver, and session type, the host may draw that picture through its gaming GPU, a virtual display driver, or a mix of both. The remote device may also receive a compressed video stream at a different size or frame rate. These steps can change the browser test result even though the physical GPU has not changed.

The Graphics Test measures browser-based shading and fill rate at 1080p, with a score out of 100. It is a comparison tool for the current browser and session, not a game benchmark, a GPU temperature reading, or a test that identifies the exact graphics card. Run it on the computer you want to check, and use the local result as a baseline whenever you can.