Report · September 2026
Runtime performance on a real phone
A slot game animated with the GreatSprites runtime, measured against 23 of the most-played web slots on a major operator, on one real Android phone. Measured 20 September 2026.
Summary
- 2nd lightest of 24 in JavaScript per frame (4.0 ms p95 against a median of 7.7 ms).
- The shortest blocking task while loading of all 24 (182 ms against a median of 393 ms).
- 3rd fastest to the first picture on screen (956 ms against 1,453 ms).
- In the lighter half for GPU memory (9th), download (8th) and draw calls (10th).
Device and journey
- Phone: Android 15, MediaTek MT6768, Mali-G52 MC2 GPU, 4 GB RAM, 720×1600 screen at device pixel ratio 2, Chrome.
- Journey for every game: load, intro, idle, three spins, idle.
- Probe: in-page; JavaScript time per frame, long tasks, draw calls, GPU texture bytes, back buffers and every downloaded byte.
- Reference set: the most-played slots on the operator's listing that day; 25 captured, 23 measurable (two never drew a frame in the test browser). Titles are anonymised.
Results
| Metric | Median | p75 | Min | Max | Animated game (rank of 24) |
|---|---|---|---|---|---|
| GPU texture memory, peak (MB) | 94.0 | 131.8 | 35.6 | 329.9 | 82.7 (9) |
| JavaScript heap, peak (MB) | 44.1 | 159.3 | 9.5 | 256.5 | 55.7 (13) |
| Draw calls per frame, p50 | 62 | 126 | 9 | 237 | 47 (10) |
| JavaScript per frame, p95 (ms) | 7.7 | 10.9 | 0.6 | 27.7 | 4.0 (2) |
| Download (MB, measurable floor) | 23.7 | 29.0 | 8.6 | 56.5 | 15.9 (8) |
| Back buffers (MB) | 8.1 | 8.1 | 7.8 | 15.6 | 12.2 (21) |
| Longest blocking task while loading (ms) | 393 | 487 | 231 | 953 | 182 (1) |
| First picture on screen (ms) | 1,453 | 1,721 | 796 | 4,996 | 956 (3) |
| Frame rate, minimum over the spins | 59.8 | 60.0 | 28.4 | 60.0 | 54.5 (4) |
Rank reads "k of 24": k − 1 reference titles are at or below the animated game's value; 1 is the lightest.
Session steadiness
On the same phone the animated game ran 29 minutes of autoplay. Every minute averaged 57–59 frames per second; there were no long frames, no errors and no slowdown as the phone warmed up.
What this report does not say
- It is one device. Other phones are measured as they become available and listed in later reports.
- The animated game is ours. It shows what the runtime allows; a game that loads much more animation will cost more, which is why every project shows its budget.
- Back buffers are a property of the game's own renderer settings, not of the animations.
Two free tests on your own picture
Make two animations from your own art, play them in your own build, and see what they cost the device. No card.
Join early access →