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.

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

Login Forms, Headers and Cookies


If your site is behind a login form, SpeedCurve supports the WebPageTest scripting language which can be used to fill out the form or add cookies/headers in order to be authenticated. For more information about adding WebPageTest scripts to your Settings, see this article.

User-Agent Sniffing


SpeedCurve testing agents use the standard WebPageTest User-Agent string. You can give the SpeedCurve testing agents access to your site by searching for the string "PTST" in the User-Agent string and not blocking that traffic.

! (IP Addresses)


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

Private Test Agents


Customers on the Enterprise Platinum Plan can deploy their own WebPageTest agents inside the firewall. With a little extra work on our side we can make those agents selectable from within your SpeedCurve Settings, thus allowing you to schedule tests and collect results for an internal site. To run your own private test agent you need to set up a test machine following the WebPageTest instructions and then point the test agent to the SpeedCurve WebPageTest instance. The agent then polls our server for work and software updates so we don't need remote access to the agent behind your firewall and as long as you keep the agent up and running we'll be able to use it to run tests and show results within the standard SpeedCurve UI.

Did this answer your question?