Optimising for the Web
summary
Aim for something visible within 1 second because beyond ~3 seconds bounce spikes and Google data shows 5s raises bounce probability dramatically (roughly +90%). Reduce initial download by using Unity Addressables or split PCK bundles in Godot, load scenes and menus async, and stream large assets. Compress builds with Brotli compression (typical 15–30% savings), strip unused engine code and remove the Unity logo (saves ~1 MB), and adopt WebGPU for heavy GPU work (WebGPU 120k bullets at 60 FPS demonstrated).
AI-written summary · about
chapters (11)
- 0:00Web game optimization intro
- 3:14Fast load times matter
- 6:47Three phases of loading
- 7:49Unity Addressables downloads
- 13:03Godot PCK bundles
- 15:51Compressing assets
- 19:24Reducing Unity build size
- 21:53Stripping engine code
- 24:18Runtime performance tips
- 28:12Future of WebGPU
- 29:16Q&A
related talks
20mOptimizing assets for graphics heavy Web Applicatoins: tips and tricks from the game dev background
23mOptimizing HTML5 Games: 10 Years of Learnings
29mSpeed Essentials: Key Techniques for Fast Websites
46mThink Fast!
33mSaving the Web 16 Milliseconds at a Time
58mNeed for speed 8, performance tuning of your web application
23mOptimizing page load speed on front end side
01h 03mSpeed up your Web Application
