Why Did My Tests Fail?

If your tests have failed there could be a number of reasons.

Firewalls and Bot Managers

A frequent reason for test failure is the blocking of Niteco Performance Insights tests by Firewalls and Bot Managers that prevent traffic from automated sources.

Response Time

A test may fail if the page load time exceeds 2 minutes.

Response Type

Tests will only be run if the server returns an HTTP 200 response. If the server returns any other response type the test will fail.

Understanding Response Codes:

Codes 204, 302, 400, 403, 404, 500, 502, 503, 524 are common HTTP response status codes.

Failed Tests

If your scheduled or manually triggered tests fail, you can view their status in the Test Management page.

Select the test that failed from the test list and click on Detailed Result to open the full report.

You can view the exact reason why each test run failed in the report and even dig deeper into test results by analyzing each tab in the report.

Failed Deploys

If tests included in deploys have failed, you can view their status in the Deploys page.

Select the deploy that failed from the deploy list and click on Detailed Result to open the full report.

You can view the exact reason why each test run in the deploy failed in the report and even dig deeper into test results by analyzing each tab in the report.

Preventing Tests being Blocked

To avoid having Niteco Performance Insights tests obstructed by your bot management or firewall settings, the simplest solution is to add the Niteco Performance Insights user-agent to your safelist. You can achieve this by permitting all HTTP traffic that includes the user-agent string "NitecoPerfmon"

For additional strategies, please refer to our guide on testing private websites.

Preventing Lighthouse Tests being Blocked

Lighthouse tests can fail for many of the same reasons Niteco Performance Insights tests can fail. Lighthouse uses a distinct user-agent from standard Niteco Performance Insights tests. To prevent blockage, you should allow all HTTP traffic that contains the user-agent string "Chrome-Lighthouse" to avoid blocking tests coming from Lighthouse. Please not that Lighthouse tests also do not support scripting.

Getting help

If you are experiencing problem with failed tests and need help, please contact [email protected] for assistance.