Test private QA, dev & staging sites

Includes how to prevent SpeedCurve and Lighthouse tests from being blocked by your firewall or bot manager.

It's easy to use SpeedCurve to test URLs that are publicly available, but sometimes you might want to test URLs that are private (password protected or inside your corporate firewall). We have several ways of making this work.

Basic authentication

If you need to keep your development or staging site private, SpeedCurve supports basic authentication allowing you to put it online behind a username and password. To give SpeedCurve access to the site, edit your Settings and add a basic authentication username and password for the site. The username and password are stored unencrypted so we recommend using a dummy throw away account for testing pages.

Click the padlock icon next to a URL to add basic authentication details.


Adding a username and password for Basic HTTP Auth

Login forms, headers & cookies

If your site is behind a login form, you can find some example scripts in our article about testing pages that require authentication.

User-agent sniffing

You can give the SpeedCurve testing agents access to your site by searching for the string "PTST/SpeedCurve" in the user-agent request header and whitelisting that traffic. Lighthouse uses this user-agent string that you can whitelist: Chrome-Lighthouse.

Whitelisting IP addresses

SpeedCurve test agents run in Amazon datacenters and don't have static IP addresses that can be added to a whitelist. You could allow all traffic from Amazon AWS, but we don't recommend doing that.

Private test agents

Customers on annual plans valued at $12,000 or more can deploy their own synthetic test agents inside the firewall.