diff --git a/mailpoet/tests/performance/README.md b/mailpoet/tests/performance/README.md
index ad3c10738b..52ef295b57 100644
--- a/mailpoet/tests/performance/README.md
+++ b/mailpoet/tests/performance/README.md
@@ -189,8 +189,6 @@ Groups are used to organize common logic in the test scripts and can help with t
 
 There are checks inside the tests but they aren't failing tests, instead, they are more of a check that the process we use in tests are finished.
 
-Currently, there are 36 checks in total for the nightly build, and 19 checks for the pull requests.
-
 If you find less than this in our CI runs over to Grafana streaming, that means some of the tests are failing in execution and they require investigation, whether due to maintance or bug found.
 
 ## Other Resources
diff --git a/mailpoet/tests/performance/scenarios.js b/mailpoet/tests/performance/scenarios.js
index 44e52449cf..7a628138cd 100644
--- a/mailpoet/tests/performance/scenarios.js
+++ b/mailpoet/tests/performance/scenarios.js
@@ -86,7 +86,7 @@ if (scenario) {
 }
 
 // Run those tests against a pull request build
-// Note: there are 19 checks in total
+// Note: there are 20 checks in total
 export async function pullRequests() {
   await onboardingWizard();
   await newsletterListing();
@@ -103,7 +103,7 @@ export async function pullRequests() {
 }
 
 // Run those tests against trunk in a nightly build
-// Note: there are 36 checks in total
+// Note: there are 37 checks in total
 export async function nightly() {
   await newsletterListing();
   await newsletterStatistics();