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.
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.
Can I limit my monthly checks?
If you have a number of teams in SpeedCurve, you can adjust and allocate your checks budget across all your teams.
To do this, go to your Team > Team Info page (from the bottom-left navbar), edit the number of checks, and then 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 (URLs) x Regions x Browsers x Test Times x 3 Checks = Total site 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 x 3 Checks = Total "Test Now" / Deploy
Then we just add the site checks and any deployment checks you've triggered via the API to get the total number of checks for the month:
Site 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 CI/CD 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.
"Adding another URL would take you over your checks per month budget. Upgrade your account to increase your number of checks."
If you get this message, it means you don't have enough checks to accommodate the new sites / URLs / browsers / regions / test times you're trying to add to your Synthetic test settings.
You have a few options:
Go through your test settings and deselect a few parameters. This will free up some checks in your budget.
If you have multiple teams, go to your Admin > Teams page and check to see if any of your other teams have unused checks that you can allocate to your team. (You need to be an Org Admin to see the Admin > Teams page.)
If you don't have any unused checks from other teams, then you'll need to buy more checks for your plan. If you're on a plan with credit card billing, you can do this via your Admin panel on the SpeedCurve website. Otherwise, email us at email@example.com.