WebGL build in Unity - Performance & Optimization

Performance: WebGL build

HIGH IMPACT

This affects the page load speed and runtime rendering performance of Unity games running in the browser.

Loading a Unity WebGL game efficiently

Unity

Use asset bundles, compression (gzip or Brotli), and strip unused code/assets before build.

Smaller download size speeds up loading and reduces time to interactive.

📈 Performance GainReduces bundle size by 50-80%, cutting load time and improving LCP.

Loading a Unity WebGL game efficiently

Unity

Build with all assets included and no compression or asset bundling.

Large build size causes slow download and delays first contentful paint.

📉 Performance CostBlocks rendering for several seconds depending on asset size; adds 10-50MB to bundle.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Uncompressed large WebGL build	Minimal DOM changes	0 reflows	High paint cost due to delayed rendering	[X] Bad
Compressed and optimized WebGL build	Minimal DOM changes	0 reflows	Lower paint cost with faster rendering start	[OK] Good

Rendering Pipeline

The WebGL build is downloaded, decompressed, and parsed by the browser, then the Unity runtime initializes and renders frames using GPU acceleration.

→Network Download

→Parsing & Decompression

→Initialization

→Rendering

⚠️ BottleneckNetwork Download and Initialization delay the Largest Contentful Paint.

Core Web Vital Affected

LCP

This affects the page load speed and runtime rendering performance of Unity games running in the browser.

Optimization Tips

1Compress WebGL build files to reduce download size.

2Strip unused assets and code before building.

3Lazy load large assets to improve initial load speed.

Performance Quiz - 3 Questions

What is the main performance issue with a large uncompressed Unity WebGL build?

A Slow network download delays game start

B Too many DOM nodes cause reflows

C Excessive CSS selectors slow rendering

D JavaScript syntax errors block execution

DevTools: Network

How to check: Open DevTools, go to Network tab, filter by .wasm, .data, and .js files, and check their sizes and load times.

What to look for: Look for large file sizes and long download times indicating unoptimized builds.

Practice

1. What is the main purpose of creating a WebGL build in Unity?

easy

A. To export games as console packages

B. To create mobile apps for Android and iOS

C. To run Unity games directly in web browsers without installation

D. To build desktop applications for Windows and Mac

Solution

1. Step 1: Understand WebGL build purpose

   WebGL build allows Unity games to run inside web browsers without needing users to install anything.

2. Step 2: Compare with other build targets

   Other build targets like Android or desktop require installation, unlike WebGL.

3. Final Answer:

   To run Unity games directly in web browsers without installation -> Option C

4. Quick Check:

   WebGL build = run in browser [OK]

Hint: WebGL = play games in browser, no install needed [OK]

Common Mistakes:

• Confusing WebGL with mobile or desktop builds
• Thinking WebGL requires app installation
• Assuming WebGL builds are for consoles

2. Which Unity menu option do you use to switch your project to WebGL build target?

easy

A. Window > Package Manager

B. Edit > Preferences

C. File > New Project

D. File > Build Settings

Solution

1. Step 1: Locate build target settings

   Unity uses the Build Settings window to select and switch build targets like WebGL.

2. Step 2: Confirm correct menu path

   The Build Settings window is accessed via File > Build Settings, not other menus.

3. Final Answer:

   File > Build Settings -> Option D

4. Quick Check:

   Switch build target = Build Settings [OK]

Hint: Build Settings is where you pick WebGL target [OK]

Common Mistakes:

• Choosing Edit > Preferences which is for editor settings
• Selecting Window > Package Manager which manages packages
• Confusing File > New Project with build settings

3. After building a Unity WebGL project, which file do you open in a browser to start the game?

medium

A. game.exe

B. index.html

C. main.unity

D. build.json

Solution

1. Step 1: Identify WebGL build output files

   Unity WebGL build creates an index.html file to launch the game in browsers.

2. Step 2: Understand file roles

   Other files like .exe or .unity are not used for WebGL browser launch.

3. Final Answer:

   index.html -> Option B

4. Quick Check:

   Open index.html to run WebGL game [OK]

Hint: Open index.html to play WebGL game in browser [OK]

Common Mistakes:

• Trying to open .exe files which are for desktop
• Confusing build.json as launch file
• Attempting to open .unity files directly

4. You built your Unity project for WebGL but the game does not load in the browser. What is a common cause?

medium

A. Not running a local or remote web server to serve the files

B. Using the wrong Unity version for WebGL

C. Forgetting to save the scene before building

D. Not installing the WebGL module in Unity Hub

Solution

1. Step 1: Understand WebGL file loading requirements

   WebGL builds require serving files via a web server; opening index.html directly from file system often fails due to browser security.

2. Step 2: Check other options

   While Unity version and modules matter, the most common cause is missing a web server.

3. Final Answer:

   Not running a local or remote web server to serve the files -> Option A

4. Quick Check:

   WebGL needs web server to load files [OK]

Hint: Always use a web server to test WebGL builds [OK]

Common Mistakes:

• Opening index.html directly without server
• Ignoring Unity Hub WebGL module installation
• Assuming saving scene fixes loading issues

5. You want to optimize your Unity WebGL build to reduce loading time. Which approach helps achieve this?

hard

A. Enable Compression Format (e.g., gzip or Brotli) in Player Settings

B. Increase texture resolution for better quality

C. Add more scenes to the build to preload content

D. Disable WebGL memory size limit in Player Settings

Solution

1. Step 1: Identify optimization methods for WebGL loading

   Compression formats like gzip or Brotli reduce file sizes, speeding up downloads and load times.

2. Step 2: Evaluate other options

   Increasing texture resolution or adding more scenes increases load size; disabling memory limits can cause crashes.

3. Final Answer:

   Enable Compression Format (e.g., gzip or Brotli) in Player Settings -> Option A

4. Quick Check:

   Compression reduces WebGL load time [OK]

Hint: Use compression to shrink WebGL build files [OK]

Common Mistakes:

• Increasing texture size which slows loading
• Adding many scenes unnecessarily
• Disabling memory limits causing instability