When analyzing a page or executing a monitor, if Speed Analysis Lab can’t access the page properly, an error message will be displayed.
There are two error categories:
- HTTP status of the page sends back an error (404, 403, 500, etc)
- No response or timeout
If you see this type of error we recommend double-checking the URL (and advanced parameters of your speed test if you use any). Next, check locally on your web browser to confirm the page is working properly.
If you can access the page but not Speed Analysis Lab, a security mechanism may be preventing Speed Analysis Lab from accessing the page. Go to this section to see recommended actions.
HTTP status of the page error
Use the table to see a list of common errors and recommended actions.
Error type | Details and recommended action |
404: Page not found | Potential typo in the URL |
401: Unauthorized | The page is not public and you made need to use a Basic Auth in the advanced settings or configure a scenario to login to access the page (depending on the situation) |
403: Forbidden | The page is not public and you made need to use a Basic Auth in the advanced settings or configure a scenario to login to access the page (depending on the situation) or a security protection issue |
500: Internal Server Error | Likely a temporary issue. You can retry if the website begins to work |
503: Service Unavailable | Likely a temporary issue. You can retry if the website begins to work |
No response or timeout
In certain situations the web page may not respond at all or respond very slowly, leading to a timeout.
Speed Analysis Lab will try to reach the page for up to 20 seconds before sending back a timeout error message.
No response can be due to a security issue (firewall) blocking our technology from accessing the webpage.
How to make sure Speed Analysis Lab can access your page
We recommend that our IP addresses are allow-listed by a security/bot detection technology that could prevent the access.
Alternative temporary workarounds (which may allow Speed Analysis Lab to access the page).
- Use another test location
- Use another User Agent