Low frame rates in the browser game usually come from the browser, not the game: hardware acceleration is off, or a laptop is running the browser on its weaker built-in graphics chip. Fix those two first, close other heavy tabs, then lower shadows and view distance. Phones and tablets are capped at 30 fps on purpose.

Low FPS or Stutter in the Browser Game: What to Check

Fixes, most likely first

1. Turn on hardware acceleration and restart the browser. Chrome: Settings > System > "Use graphics acceleration when available". Edge: Settings > System and performance, the same switch. Firefox: Settings > General > Performance, untick "Use recommended performance settings", tick "Use hardware acceleration when available". 2. On a Windows laptop with two graphics chips, give the browser the fast one: Windows Settings > System > Display > Graphics, add or pick your browser, choose High performance, and restart the browser. 3. Plug the laptop in. On battery, many laptops slow the graphics chip down. 4. Close other game tabs and heavy pages. A second game tab shares the same graphics card and takes frames from the first. 5. Lower the graphics options in the game's System > Graphics panel, starting with shadows and view distance. 6. Reload with Ctrl+F5 so you are on the newest version.

What the game sets for you

On its first run the page looks at the device. A computer with 4 GB of memory or less, 4 processor cores or fewer, or a built-in graphics chip gets a lighter set of options: shadows, ambient occlusion, sun shafts and water reflections off, a shorter view distance, and less ground clutter and fewer particles. Textures stay at full size. Anything you change afterwards is kept. Phones and tablets get their own settings and a cap of 30 frames per second. Macs draw through WebGPU.

What we measured

- Windows desktop, RTX 3070, Chromium, WebGL 2: about 140 fps on the Wandering Isle (2026-11-14). - MacBook Pro M1 Pro at 1800x1009: 20 to 25 fps on WebGL 2, 46 to 65 fps on WebGPU, which is why Macs now use WebGPU (2026-11-10). - Phones: 30 fps, the cap. We have no published numbers from a real phone yet.

Known and fixed

- 2026-11-10: a frame limiter held desktops at about 64 fps. Fixed. - 2026-11-13: frames arrived unevenly at the frame cap, which looked like stutter at a steady 30 fps. Fixed. - 2026-11-14: opening the spellbook and other windows froze the game for up to a second while pictures downloaded. Fixed. Short hitches in the first minutes are the game streaming data for a place you have not visited before; see Stuck on the loading bar or slow to load.

Still stuck?

Ask on our Discord (linked from https://shadopan.com) or use the Support page. Tell us your computer or phone model, graphics card, browser, the zone you were in and the frame rate you get. On a computer, pressing F10 on the game page shows its log; a screenshot of the last lines helps. The page sends a crash report by itself when the game stops, as described on the privacy page.