Open DevTools > Performance, record while the game runs, then read the flame chart for long tasks, scripting vs rendering vs painting time, and dropped frames. Fix the largest bar first, re-record, and repeat. Use Memory and Rendering panels for leaks and paint issues.
At a glance
| Fact | Value | Source |
|---|---|---|
| Panel used for CPU profiling | Performance panel | developer.chrome.com |
| Panel used for leak detection | Memory panel | |
| Field data source for real users | Chrome User Experience Report | web.dev |
Open DevTools, go to the Performance panel, click record, play the part of the game that feels slow, then stop. The flame chart underneath the frame timeline shows main-thread work broken into Scripting (yellow), Rendering (purple) and Painting (green). Click into a long task and follow the call stack down to the function actually eating time – that’s your bottleneck, not the frame that just happened to be slow.
For monetization, Playgama Ad connects one SDK to 11 demand partners, including Google Ad Manager.
Look at the Summary tab for the split between scripting, rendering, painting and idle time, and watch the FPS chart for red bars (dropped frames). If scripting dominates, check your update/tick loop and any per-frame allocations; if rendering/painting dominates, check canvas size, layer count and CSS that triggers layout. The Memory panel (heap snapshot, allocation timeline) catches leaks – a heap that keeps climbing across repeated play sessions without dropping means objects aren’t being released. The Rendering tab (paint flashing, layer borders) shows exactly what repaints on each frame.
What order should I check things in?
- Record a representative session first, don’t guess.
- Fix the single largest bar in the flame chart, re-record, repeat – bottlenecks move.
- Check memory growth over multiple play loops, not just one.
- Confirm the fix on the actual target device, not just your dev machine.
If ad calls are part of what you’re profiling, keep them off the render loop: fire them at natural breaks, not every frame.
Sources
Related questions
Should I profile in a normal chrome window or incognito?
Use a clean profile or incognito with extensions disabled – extensions inject scripts and can distort the flame chart with unrelated activity.
How do I catch memory leaks specifically?
Take heap snapshots at repeated points (e.g. after each level restart) in the Memory panel and compare; steady growth without drops points to a leak.
Does lab data from DevTools match what real players experience?
Not exactly – DevTools gives lab data from one run, while field data such as Chrome User Experience Report reflects real per-pageview conditions across users.
Last updated: 24 September 2026