Cart and Checkout Page Check

What it checks

At most every 10 minutes, PRO loads your WooCommerce checkout page and cart page from your own server and looks at the answer. A page that errors, times out or says it is gone counts as a failed check.

When it raises an issue

One failed check is ignored, because a single slow answer is common. An issue is raised when a page fails 2 checks in a row (about 20 minutes).

The issue clears on its own once the page loads again, and you get a short “resolved” email if PRO had emailed you about it. It lowers the Checkout Health Score (Medium −10, High −30, Critical −45) and appears on the Issues, Health (Checkout bar) and Recommendations screens.

When it does not judge

If the page answers 401, 403 or 429, PRO does not judge it. A firewall, security plugin, Cloudflare rule or rate limit may be blocking the check rather than the page being broken, so nothing is raised and any existing issue is left as it is.

What it cannot prove

• It reads what your server returns, not what a browser draws. A page can load and still have a JavaScript error, a hidden payment button or broken styling.
• It does not add anything to a cart, place an order or contact a payment provider. For a fuller walk-through, use the Checkout test.
• It cannot run while your site or its background tasks are not running.

When you see this issue

1. Open the checkout and cart pages in a private browser window.
2. Check your host’s error log and recent plugin or theme changes.
3. If the pages load for you but PRO says they fail, check whether a firewall or caching rule treats your own server’s request differently.