Quick answer: Reduce object counts and per-tick events, cut WebGL effects and overdraw, shrink and atlas images, and profile with the debugger to find the heaviest part.

A Construct 3 game that lags only on mobile is asking more of the device than it can give. The fixes target the most expensive things on weak hardware. Here is where to look.

How to fix it

1. Reduce object count and collisions

Hundreds of objects with collision checks each tick crush mobile. Destroy off-screen objects, lower spawn counts, and disable collisions on objects that do not need them.

2. Cut effects and overdraw

WebGL effects and many overlapping transparent objects are expensive on mobile GPUs. Remove non-essential effects and reduce large stacked transparencies.

3. Optimize images and profile

Large textures eat mobile memory and fill rate. Shrink images, use spritesheets, and run the debugger's profiler to see which events and objects cost the most, then target those.

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 Construct 3 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.

The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.