# Unity

Big WebGL builds = slow first launch. Slow launch = fewer players. Many platforms also limit initial package size

Build size depends on:

* Unity runtime and generated code
* assets included in the build (textures, audio, shaders)
* compression (Gzip/Brotli)
* how content is delivered (e.g., Addressables)

This guide shows how to reduce the initial build without changing game logic.

Example (Fast 4G in browser DevTools)

* No optimization — full game in the initial download
* Addressables only — heavy assets loaded on demand
* Addressables + this guide — minimal initial package

Same game, different setup — much less data before the first interaction and faster startup.<br>

<figure><img src="/files/CRRTx6cCYtJ5TJ5wmHLi" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.playgama.com/playgama/performance-and-optimization/unity.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.