Quick answer: Move heavy, parallelizable work to a web worker, communicate via messages with transferable objects, and keep rendering and input responsive on the main thread.

Main-thread jank from heavy logic is single-threaded blocking. A web worker offloads it. Here is how.

How to fix it

1. Offload heavy work to a worker

Move CPU-heavy, parallelizable work — pathfinding, procedural generation, simulation — to a web worker so it runs off the main thread, keeping rendering and input smooth.

2. Use transferable objects

Pass large data to and from the worker as transferable objects (or SharedArrayBuffer) rather than copying, so the message overhead does not negate the benefit of offloading.

3. Keep the main thread for render and input

Reserve the main thread for rendering and input, consuming worker results as they arrive. Splitting the work this way removes the jank that came from doing everything on one thread.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every HTML5 error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Most of the time the fix is small. Seeing the failure clearly is the part that actually costs you.