> For the complete documentation index, see [llms.txt](https://docs.hology.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hology.app/gameplay/performance/target-slower-devices.md).

# Target slower devices

Your computer is likely faster than what players of your games are using, especially if they are on mobile devices like smartphones and tablets. As you add more and more features to your game over time, it is likely going to require more CPU. It is therefore useful to enable CPU throttling when testing your game to ensure that it runs smoothly even on slower devices.

In Chrome Dev Tools, go to Performance, then expand using the cog wheel on the right to show the CPU throttle options. The amount that is useful to throttle will depend on your own device so it can be best to re-calibrate so you can select a mid or low-tier mobile setting.

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.hology.app/gameplay/performance/target-slower-devices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
