Fix List
The fix list is an automatically generated attention list in the collapsible drawer on the board. It surfaces page groups that have counted script errors or a significant number of slow-load visits in the selected range, with a link to the relevant help article for each entry.
How the fix list is built
The fix list is generated from the data already on your board. It does not require any separate configuration or monitoring setup. Every time you load the board, the system scans the error-classes data and the load-speed data for the selected range and adds a row to the fix list for any page group that meets the trigger conditions.
A page group triggers a fix-list row if it has any counted script errors in the selected range. It also triggers a row if a significant share of its visits fall in the slow load bands — the 1–3 s, 3–8 s, or over-8 s bands. The fix list shows up to eight rows, ordered by the severity of the signal that triggered them.
The fix list is advisory. It shows you where to look, not what to do. A page on the fix list may have a one-time error that was already resolved, or a load-speed issue caused by a third-party resource you cannot control. The list is a starting point for investigation, not a definitive problem report.
Reading a fix-list row
Each row in the fix list shows the page group path, a short description of why it appeared, and a Help link. The description is one of two fixed phrases: "Error class counts are high on this page group" for error-triggered rows, or "Visit beacons in a slow load band" for load-speed-triggered rows.
The Help link takes you to either the error-classes article or the load-bands article depending on the trigger. Those articles explain what the data means and what steps are commonly useful for investigation.
If a page group has both errors and slow load, it may appear twice in the fix list — once for the error trigger and once for the load trigger. The list does not deduplicate by page group; it deduplicates by trigger type within the page group.
When the fix list is empty
If no page group in the selected range has counted errors and no page group has visits in the slow load bands, the fix list shows a message: "No error-class or slow-band page groups yet." This is a healthy state — it means your pages are not reporting JavaScript errors and the load-speed distribution for the range does not include slow visits.
The fix list can also be empty because the selected range is too narrow. A range of a single day with low traffic may not have enough data to trigger any rows. Widening the range to last 7 days or last 30 days gives the fix list more data to work with.
The fix list is not a comprehensive code quality report. It surfaces the signals StatelessID has — error class counts and load bands — and nothing else. A page could have poor user experience for reasons that do not appear in either of those signals. The absence of a fix-list row for a page does not mean that page is free of problems.
Acting on a fix-list entry
When a page group appears with an error trigger, the first step is to open a browser developer tools session on that page and reproduce the error locally. Check the Console tab for JavaScript errors. The error-classes card can tell you how often the error occurs; developer tools can tell you which line of code causes it and what the error message is.
When a page group appears with a load trigger, check the load-speed distribution in the Load speed card in the main board and in the collapsible drawer. A high fraction of slow visits on a specific page group suggests that page has heavier resources than others. Common causes include large unoptimised images, large third-party scripts, or blocking render resources.
Fixing a JavaScript error or improving page load speed on your site will cause the fix-list entry to drop out of the list naturally as the event counts for the improved state accumulate in subsequent ranges. You do not need to manually dismiss fix-list entries.
Fix list and the errors-off toggle
If error collection is disabled in your Filters settings, error-triggered rows will never appear in the fix list, even if JavaScript errors are occurring on your pages. The fix list can only surface what StatelessID has counted. Load-speed triggered rows still appear regardless of the errors-off setting, because load-speed data comes from the page view beacon, not the error beacon.
If you have disabled error collection and later see load-speed rows in the fix list, you can enable errors in Filters to also get error visibility for future ranges. Historical ranges when errors were off will remain without error rows.
Troubleshooting
If the fix list is not visible, confirm you have expanded the collapsible drawer near the bottom of the board. The fix list is inside the drawer. If the drawer is open but the fix list section is not showing, confirm the selected range is wide enough to have accumulated load-speed or error data.
If a page group keeps appearing in the fix list across many ranges and you have already investigated and believe the issue is resolved, check whether the fix-list range window is including dates before your fix was deployed. Switch to a custom range starting from the date of your fix to see whether the entry has dropped out for the post-fix period.