Who actually needs the Standard tier?
Picking a plan shouldn't feel like a gamble. So instead of selling you the biggest box, here is plainly who each tier is for, and why starting small is almost always the right move.
Start with Starter
If you're curious about how your website is really doing across speed, accessibility, SEO and privacy, Starter is the right place to begin. It gives you automated daily testing of your main page, a handful of extra landing pages, and a monthly audit, all in plain language. You don't need a data team to make sense of it.
Most people should start here. You'll quickly learn what your site does well and where it slips, and whether continuous quality is a habit worth building. There's no sense paying for capacity you haven't grown into yet.
And if you outgrow it, upgrading is painless. Just reach out to move from Starter to Standard. You pay the difference and you're up and running, without cancelling, re-signing, or starting over.
Standard is for teams with a process
Standard is built for organisations that already treat quality as part of how they ship, and it pays off precisely because you have a process to plug it into.
You're likely a good fit for Standard if this sounds like you:
-
You run a UAT stage. UAT, user acceptance testing, is the environment where a change is validated, both functionally and technically, before it's allowed anywhere near production. If nothing reaches your users without passing through a gate like this, Standard fits the way you already work. It lets you test that staging or UAT site (including from static IP addresses, so we can reach it behind a firewall) and catch problems before your visitors ever see them.
-
You work with a performance budget. A performance budget is a set of limits you agree on up front, such as a cap on page weight, on how long the page takes to become usable, or on the number of requests, so that quality can't quietly erode release after release. If you're actively defending against regressions (something that used to work well getting worse, usually right after a deploy), Standard gives you the coverage and history to do it properly.
-
You need to be told, not to go looking. Webhooks, below, cover that one.
Webhooks tell you the moment a score slips
A webhook is a signal Standard can send to a system you control the instant a test run finishes. Instead of remembering to log in and check, your tools get notified automatically, and you can act on it however you like.
That turns Webperf from something you check into something that watches your back. A few examples:
- Post an alert to your team chat when a page's score drops below a threshold you've set.
- Fail a deployment, or flag a release, when a change pushes a page past its performance budget.
- Open a ticket automatically so the regression is on someone's list before the next standup.
For a team with a UAT gate and a performance budget, this closes the loop. A change ships, a test runs, you get notified, you act.
So which one is you?
- Curious, getting started, or a single site you want to keep a close eye on? Start with Starter. Upgrading later is just an email and the difference in price.
- You already have a UAT process, defend a performance budget, and want to be notified the moment something regresses? Go with Standard.
Not sure yet? Look at the plans side by side, or just ask us. We'd rather point you at the right tier than the biggest one.
Not sure which tier fits your team? We're happy to talk it through at hello@webperf.cloud.