Your SpeedCurve Synthetic plan is billed based on the number of performance checks you make a month. With a Pay-As-You-Go plan, you pay only for the checks you use. With an Enterprise plan, you pay for a pre-determined number of monthly checks, at a 10-20% discount over PAYG. (See our pricing guide for more information.)

No matter what type of plan you have, it's in your best interest to manage your monthly checks to get the best value out of SpeedCurve.

What is a check?

Each check equals a single page being loaded by one of our testing agents using a real web browser with the resulting performance metrics and video frames being recorded. (If you've used before, then a check is like a "run" in WebPageTest terminology.)

We check each URL that you added to your Settings a minimum of 3 times and select the median result. This makes your results more robust and evens out any variations from a single check running slower or faster than the norm.

Do I ever need more or less than 3 checks per test?

We recommend 3 checks as a minimum starting point, but if you're finding that your results are too variable, then we suggest increasing that number to 5. This will help reduce the impact of outliers and unnecessary spikiness in your data. If your graphs are still too spiky, then increase the number of checks to 7, etc. (Just keep using odd numbers so that you get identifiable medians.)  

How do I find out how many checks I'm using each month?

On your Admin > Plan & Usage page, you can see how many checks per day you are currently using, as well as an estimate for the number of checks you'll use in the current billing month:

Every time you change your settings to add URLs, browsers, locations, etc., you should check your Admin panel to see what the new estimate is.

Do Pay-As-You-Go accounts have a monthly cap?

All PAYG plans have a default cap of 50K checks per month. This is to ensure that people don't accidentally use more checks than they want to pay for and get any unpleasant surprises on their monthly bill. We can increase this cap for you if you wish, but it has to be done manually at our end.

Can I limit my monthly checks?

As mentioned above, by default your PAYG plan gives you 50K checks per month. If you use all these checks, your monthly bill will be $500. If you have a strict budget for how much you can spend on testing each month, the best way to stay under budget is to adjust your maximum checks. To do this:

1. Go to Admin > Teams. There you'll see the checks budget for your team, like this:

2. Click on the "Checks Budget" number. This will take you to your "Edit a Team" page, where (among other things) you can edit your number of checks. Remember that the price per check is $0.01, so for example, if you have a strict budget of $100 per month, you'll want your checks budget to be 10,000.

3. Hit the green "Edit team" button to save your changes.

How many checks do I need?

The number of checks is based on first combining the number of settings you add:

Sites x Templates x Regions x Browsers x Times x 3 Checks = Total site checks

If you enable responsive testing on your main site, which is the first site in your account, then we also add additional checks for the 5 extra responsive viewport widths:

1 Main Site x Templates x Regions x 5 Viewports x Times x 3 Checks = Total responsive checks

Every time you use the "Test Now" button or do a deploy using the API we do an extra round of tests on your main site:

1 Main Site x Templates x Regions x Browsers (& viewports if responsive enabled) x 3 Checks = Total "Test Now" / Deploy

Then we just add the site checks, any responsive checks and also any deployment checks you've triggered via the API to get the total number of checks for the month:

Site checks + Responsive checks + Deploy checks = Total number of checks per month

How can I manage my checks budget?

We recommend that most people test their pages 2-4 times a day. If you're testing more often than this, then it's a good idea to investigate why. 

One reason why you might have so many daily tests scheduled is because you're monitoring performance alongside your CD/CI process. If that's the case, then we suggest that you switch to using our deploy API to run tests after each deploy

If you're testing competitors' sites alongside your own, we suggest testing those just once per day, unless you have a compelling reason for testing more often than that.

Did this answer your question?