> For the complete documentation index, see [llms.txt](https://docs.mapsindoors.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mapsindoors.com/help-center/performance/my-solution-is-loading-very-slow.md).
# My solution is loading very slow
**1. Check the MapsIndoors Status Page**
Visit the[ MapsIndoors status page](https://status.mapsindoors.com/) to see if there are any current or past incidents that might be affecting performance.
**2. Review Media File Sizes**
Ensure that any images, 2D models, or 3D models that you are using meet the recommended size guidelines. You can find these guidelines on the[ MapsIndoors documentation site](https://docs.mapsindoors.com/products/cms/media-library).
**3. Update Your Browser or SDK**
Make sure that you are running the latest version of your web browser if you are loading your map in a browser. If you have built your own web or mobile app using the MapsIndoors SDKs, ensure that you are using the latest version of the SDK. You can find the latest SDK versions on the[ MapsIndoors documentation site](https://docs.mapsindoors.com/).
**4. Review Your Code (Web Apps)**
If you have built your own web app using the MapsIndoors SDKs, check your code for any performance-related issues.
**5. Check the Performance Article (Mobile Apps)**
If you have built your own mobile app using the MapsIndoors SDKs, refer to THIS ARTICLE for tips on how to improve performance.
**Other Potential Causes**
If none of these steps resolve the issue, slow map loading and performance might be related to your internet connection or your device's hardware.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.mapsindoors.com/help-center/performance/my-solution-is-loading-very-slow.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.