Group and Filter Load Test Results by URL

Group and filter your results by URL

When a load test hits many URLs, especially dynamic ones that carry IDs or query strings, the results table can list thousands of separate rows. The Settings panel on the results page has two Display controls that collapse those into clean, aggregated views: Ignore Query Params and Group By URL.

Open it from the results page by clicking Settings in the results sidebar. Both controls apply per test and are saved in your browser, so each test keeps its own view. Changing a setting reloads the results with the new grouping applied.

Ignore Query Params

Turn Ignore Query Params on to drop the query string from every URL before results are grouped. Requests that differ only by their query parameters are then counted as a single URL.

For example, with the toggle on:

• https://example.com/search?q=shoes
• https://example.com/search?q=hats

are both reported as https://example.com/search.

This is useful when your test drives the same endpoint with many parameter combinations and you want one row per endpoint instead of one row per parameter value.

Automatic for large tests: if a test produces more than 1000 distinct URLs, LoadFocus turns this setting on for you to keep the results readable and fast to load. You can switch it back off if you want every URL listed separately.

Group By URL

Group By URL aggregates every request whose URL starts with a prefix you provide into a single grouped row. Use it when your test hits many dynamic paths that share a common base.

1. Under Group By URL, type a full URL into the URL Prefix field, for example https://api.example.com/users/.
2. Click Add prefix to add more prefixes, or the trash icon to remove one.
3. Click Save.

With the prefix https://api.example.com/users/, these requests:

• https://api.example.com/users/123
• https://api.example.com/users/456

are grouped and reported together under that prefix instead of as separate rows.

Each prefix must be a full, valid URL, including the scheme such as https://. Invalid entries are skipped with a notice, and duplicate prefixes are removed automatically.

Where these settings are stored

Both controls are saved in your browser and scoped to the individual test by its name. They are not shared between browsers or teammates, and they never change the raw data LoadFocus collected; they only change how results are grouped for display. Saving reloads the results page so the new view takes effect.

See also: How to Check Load Test Results.