Is your WooCommerce store costing you sales?

What this tool checks

Enter a URL and this tool fetches the site's public homepage and first confirms WooCommerce is actually in use. Once that's confirmed, it probes /checkout/ — the single most expensive page on any store to get wrong — for the causes documented in WooCommerce Site Down or Broken?: whether checkout is being served from a cache, whether it's on HTTPS, and whether a working payment method is actually present. It also looks at homepage-level plugin count as a bloat signal, and opportunistically compares shop and checkout page weight when there's time left in the scan.

Why checkout, not cart

Cart and checkout share the exact same rule: both must be excluded from any page cache, and both need to run correctly under a live session. Checking checkout is an honest, sufficient proxy for that shared requirement — a separate /cart/ request would add another outbound fetch without changing what this tool could tell you. If checkout needs fixing, cart's caching exclusion is worth checking at the same time.

How to read the result

The verdict names a likely cause instead of handing you a raw score. Checkout risk means a real, specific problem was found at checkout — caching, HTTPS, or a missing payment method — and it always takes priority over anything else this tool finds. Inconclusive means checkout couldn't be confirmed publicly; this is deliberately never reported as clean, since checkout is the one page this tool most needs to see. Store issues means checkout is fine but something else — usually plugin count — is worth a look. Watch means nothing major, and clean means checkout is reachable, on HTTPS, uncached, and a payment method was detected, with no other issues found either.

What this can't do

It only sees what's publicly reachable right now — the homepage, checkout, and (when there's time) the shop page. It can't log in to wp-admin, see every product page individually, or catch a setting that changes the moment after this scan runs. The plugin count is a lower bound from what actually loads in the public markup, not a real plugin-list read, and the shop-versus-checkout page weight comparison is opportunistic context, not a verdict on its own — if it's skipped or fails, that never counts against your store.

If it comes back with a checkout risk, or inconclusive

A checkout that's cached, not on HTTPS, or missing a payment method is losing orders right now, not eventually — see WooCommerce Checkout Not Working for the full diagnostic path, or WooCommerce Fixes for a direct fix, tested with real transactions before it's called done. If the result came back inconclusive, that's worth the same attention — it means the most important check this tool runs couldn't complete, not that everything is fine.