HTML5 games are not demanding. Ours draw a few dozen simple shapes per frame, which any device from the last decade can do sixty times a second without effort. So when a browser game stutters, the cause is almost never the game's complexity — it is something competing with it.
Check these four first
- Battery saver or low-power mode. The most common single cause. These modes cap frame rates — often to 30 — and increase input latency. Turn it off or plug in.
- Heavy background tabs. Browser games run on the main thread. A video call, a streaming tab, or a page with a busy script competes for it directly. Close what you are not using.
- Hardware acceleration disabled. Some people turn this off to fix an unrelated problem and forget. Canvas rendering is much smoother with it on; check your browser's performance settings.
- Extensions. Ad blockers, password managers and privacy tools all inject scripts into every page. Try a private window with extensions disabled and compare.
In our experience those four account for the large majority of reported stutter.
Settings that matter less than people think
| Suggestion | Verdict |
|---|---|
| Lower your screen resolution | No effect — these games are not resolution bound |
| Switch browsers | Marginal; modern engines are close for canvas work |
| Clear your cache | No effect on frame rate |
| Install a "game booster" extension | Counterproductive — more main-thread work |
| Keep zoom at 100% | Worth doing; zoom adds scaling work and can hide controls |
Why a high-DPI screen can look soft
A canvas has two sizes: its CSS size on the page and its backing-store size in actual pixels. If a game ignores your device pixel ratio, the browser scales a low-resolution image up and everything looks slightly blurred.
Ours accounts for it, capped at 2.5x to avoid drawing an absurd number of pixels on very high-density displays. If a game elsewhere looks soft on a good screen, that is usually the reason — and it is a one-line omission rather than anything you can fix from your side.
Reduced motion and other preferences
If your system is set to reduce motion, this site honours it: page transitions and hover effects are disabled. Gameplay is unaffected, because a game's movement is the game rather than decoration.
The same applies to your colour theme. The site follows your system preference and remembers an explicit choice in local storage, and neither affects performance.
Diagnosing a specific game
If one game stutters and others do not, try this order:
- Reload the page. A one-off hiccup during loading is common and does not recur.
- Try a private window. This rules extensions in or out in one step.
- Try a different game on the site. If all of them stutter, the cause is your environment rather than the game.
- Try another device on the same network. If it is fine, the issue is local.
If a game is genuinely broken, please tell us through the contact page — the game's name, your browser and version, and your device type is enough to start.
What the games need from your browser
Very little, and it is worth stating so you know nothing exotic is required:
- JavaScript enabled. Without it, no game will run — although every article and policy page works fully.
- Canvas support, which every browser has had for well over a decade.
- Local storage, if you want your high scores remembered. Blocking it does not break gameplay; the games simply forget.
No plugins, no WebGL, no permissions, no downloads. How HTML5 Football Games Work explains the technology, and How to Reduce Input Lag covers latency specifically.
A five-step diagnosis
If a game is not running smoothly, this order finds the cause in a couple of minutes without changing anything you will regret.
- Reload the page. A hitch during initial load is common and does not recur.
- Open a private window. This disables most extensions in one step. If the game is smooth there, an extension is the cause.
- Check your power mode. Battery saver caps frame rates, often at 30. Plug in or turn it off.
- Close everything else. Particularly video calls, streaming tabs and anything playing audio.
- Try a different game on the site. If all of them stutter, the cause is your environment. If only one does, tell us — that is a bug worth knowing about.
In our experience steps two and three account for the large majority of reported problems, and neither involves changing a setting you need to remember to change back.
What "hardware acceleration" actually does
Worth clarifying because the advice to disable it circulates widely and is usually wrong for canvas games.
With acceleration on, the browser hands compositing and much of the drawing to your graphics hardware, which is built for exactly that. With it off, the processor does the work instead — slower for graphics, and competing with the game's own logic for the same core.
For a 2D canvas game the difference is normally in favour of leaving it on. The advice to disable it comes from a genuine but narrow case: some older drivers had bugs that produced visual artefacts. If you turned it off years ago for that reason, it is worth turning back on and seeing what happens.
