> For the complete documentation index, see [llms.txt](https://docs.gmetri.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gmetri.com/guidelines-compatibility/guidelines/experience-optimizations/scene-optimizations/performance-monitor.md).

# Performance Monitor

This feature is designed to help you monitor the performance of your metaverse scenes. It provides valuable information about how your experience is performing, allowing you to make informed decisions about optimising it.

## Getting started with Performance Monitor

To use the Performance Monitor feature, you can access it from the navbar in the editor. 

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

## Using the Performance Monitor

The Performance Monitor provides you with several key metrics that you can use to monitor the performance of your metaverse experience. These metrics include:

1. A number of Elements and Lights - This metric measures the number of elements and lights that are being rendered per second. The lower this number, the smoother your experience will be.
2. Triangle Count and Vertex Count - This metric measures the total size of all geometries generated in the scene. A lower triangle and vertex count mean a more responsive experience.
3. Texture Count - This metric measures the total number of textures used in the scene. This number includes all images included from image/gif/icon elements and 3D models.
4. Scene Size - This metric measures the total size of the scene. This metric includes all the elements and their geometries and textures. It is important to monitor this metric to ensure that your experience is not using too much memory, which can cause performance issues.
5. Avg Load Time - This metric is estimated based on a 4G connection (\~5MBps), lower the number, faster the load time.&#x20;

## Optimizing your metaverse experience:

Once you have identified performance issues using the Performance Monitor, you can take steps to optimize your metaverse experience. This may include optimizing your scenes, reducing the number of assets being loaded, or adjusting the quality of images/3D models added to your experience.


---

# 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.gmetri.com/guidelines-compatibility/guidelines/experience-optimizations/scene-optimizations/performance-monitor.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.