> For the complete documentation index, see [llms.txt](https://docs.ingestlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ingestlabs.com/site-performance/configure-test-suites.md).

# Configure Test Suites

You can configure as many Test Suites as required to test site performance. You can use the standard Google Lighthouse Standard Variant or create a new variant. The standard variant tests site performance on mobile browsers with slow 3G network connectivity. Users can also create a new variant to test site performance on different networks and devices. You can select from different parameters for testing site performance.

The following elements are mandatory to add a new test suite:

| Column Name      | Description                                                                                                                                                                                                                                                                                                                   |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name             | Denotes the Test Suite Name.                                                                                                                                                                                                                                                                                                  |
| URL              | <p>Denotes the URL of the website to be tested for performance.<br>Click <strong>Check URL</strong> to verify the URL.</p>                                                                                                                                                                                                    |
| Description      | Denotes the description of the test suite.                                                                                                                                                                                                                                                                                    |
| Status           | <p>Denotes the status of the Provider.<br>• <strong>Production</strong>: The Provider is in the Production process.<br>• <strong>Staging</strong>: The Provider is in the Staging process.<br></p>                                                                                                                            |
| Audit Categories | <p>Denotes the parameters to test site performance. While Performance is selected by default, the other categories include:<br>- Accessibility<br>- Best Practices<br>- Progressive Web App (PWA)<br>- Search Engine Optimization (SEO)<br>- Media Tags (Select this only if Media tags are deployed through Ingest Labs)</p> |

## Related Topics: <a href="#relatedtopics" id="relatedtopics"></a>

The Configure Test Suites section includes the following topics:

* [Add a New Test Suite](https://docs.ingestlabs.com/site-performance/configure-test-suites/add-a-new-test-suite.md)
* [Edit a Test Suite](https://docs.ingestlabs.com/site-performance/configure-test-suites/edit-a-test-suite.md)
* [Delete Test Suite](https://docs.ingestlabs.com/site-performance/configure-test-suites/delete-a-test-suite.md)


---

# 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.ingestlabs.com/site-performance/configure-test-suites.md?ask=<question>&goal=<user_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.
