Smoke Run
Run a free teardown

Sample run

Watch it find a broken Buy button

Below is a small made-up shop with one thing wrong. Press the button and the same engine that runs the free teardown walks it like a stranger would, then writes up what it found, in dollars, with how sure it is.

What we broke on purpose

Every Buy now and Add to cart button links to /buy, a page that was never built, so it answers HTTP 404. The engine is not told this. It reads the pages and follows the links the way any visitor would.

Read the sample's source

GET / 200

<!doctype html>
<html lang="en"><head><title>Cedar & Salt Candles (sample)</title>
<meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1">
<script async src="https://www.googletagmanager.com/gtag/js?id=G-SAMPLE0001"></script>
<script>window.dataLayer=window.dataLayer||[];function gtag(){dataLayer.push(arguments)}gtag("js",new Date());gtag("config","G-SAMPLE0001");</script>
</head><body>
<nav><a href="/">Home</a> <a href="/shop">Shop</a> <a href="/about">About</a></nav>
<h1>Cedar & Salt Candles</h1><p>Hand-poured soy candles. Sample store, not a real business.</p>
<a class="btn" href="/buy">Buy now</a>
<script>!function(f,b,e,v,n,t,s){if(f.fbq)return;n=f.fbq=function(){n.callMethod?n.callMethod.apply(n,arguments):n.queue.push(arguments)};}(window,document);fbq('init','1234567890');fbq('track','PageView');</script>
</body></html>

GET /shop 200

<!doctype html>
<html lang="en"><head><title>Shop - Cedar & Salt Candles</title>
<meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1">
<script async src="https://www.googletagmanager.com/gtag/js?id=G-SAMPLE0001"></script>
<script>window.dataLayer=window.dataLayer||[];function gtag(){dataLayer.push(arguments)}gtag("js",new Date());gtag("config","G-SAMPLE0001");</script>
</head><body>
<nav><a href="/">Home</a> <a href="/shop">Shop</a> <a href="/about">About</a></nav><h1>Shop</h1><p>$28 per candle.</p><a class="btn" href="/buy">Add to cart</a>
</body></html>

GET /buy 404

Not Found

Pick a version of the sample

Buy now leads to a page that was never built

The engine finished cedar-and-salt.sample.test: 4 pages, 13 checks, 12 requests, in 91 ms.

Sample teardown output

You are likely losing about $650 per month. A call to action a visitor would click does not work. Example /buy (404). Reproduced 3 of 3 across repeated checks.

$650per month, estimated from outside

Coverage · 4 pages, 13 checks, 4 synthetic customers, 91ms

Every dollar figure is a conservative estimate and we show our assumptions. We would rather undercount than claim something we cannot defend. Connect read-only and we replace it with the exact count from your last 50 orders and leads.

Confirmed broken
1
At risk
3
Healthy
1

Your money system

This is the stack your revenue runs on, detected from your own funnel. We can see each piece is there. What we lock is the one thing only read-only access can answer, whether the money actually moves through it.

Lead captureNot seen

No lead form seen on this page.

Behind the walls

We submit a traced test lead and confirm it actually arrives, with the right fields.

Connect read-only and we prove it. [Locked]at risk · unsized from outside
PaymentsNot seen

No payment processor seen on this page.

Behind the walls

We confirm a real order actually charges and lands in your payments account, every day.

Connect read-only and we prove it. [Locked]at risk · unsized from outside
Your CRMNot seen

No CRM signal on this page (it may be server side).

Behind the walls

We confirm the lead actually reaches your CRM as a real contact, not a dropped submission.

Connect read-only and we prove it. [Locked]at risk · unsized from outside
Confirmation emailNot seen

Your email provider runs server side, so it is invisible from outside.

Behind the walls

We confirm the confirmation or receipt email actually sends to the customer.

Connect read-only and we prove it. [Locked]at risk · unsized from outside
TrackingDetected

Google Analytics 4, Meta Pixel detected. We cannot confirm from outside whether it fires on your purchase event.

Behind the walls

We confirm your tracking actually fires on the purchase, so the numbers your ad platform optimizes on are real.

Connect read-only and we prove it. [Locked]at risk · unsized from outside

The money path

The path a paying customer walks, from the click to Stripe, your CRM and the inbox. This is where a silent break costs you the most.

  • BrokenConfirmed
    $650/mo

    A call to action a visitor would click does not work. Example /buy (404). Reproduced 3 of 3 across repeated checks.

    Call to action links

    What we saw. deadLinks: 1, reproduced: 3 of 3, confidence: high, verifiedInBrowser: false

    What to do. Click every call to action as a visitor and confirm none of them 404 or loop.

  • Worth checkingConnect to confirm

    A checkout path is implied but we found no direct link to probe. We confirm it on a connected run.

    Checkout is reachable

    What we saw. verifiable: with access

    What to do. Run a full test purchase on desktop and mobile and confirm it reaches the pay step.

  • Worth checkingConnect to confirm

    A tag is present, but we cannot confirm from outside that it fires on your purchase event. That is the most common silent leak and we watch it end to end on a connected run.

    Ad pixel and analytics

    What we saw. tagPresent: true, paidTraffic: false

    What to do. Open the thank you page and confirm the purchase event fires with a value, not just the base tag.

  • WorkingConfirmed

    The landing page loads for a visitor.

    Landing page loads: https://cedar-and-salt.sample.test/

    What we saw. httpStatus: 200

Across the whole site

Everything else the teardown turned up while crawling your pages.

  • Worth checking

    A page a visitor can reach is down (404).

    /buy

    What we saw. status: 404

    What to do. Open this page yourself and confirm it loads, or remove the links that point to it.

What this run could not verify

These came out of the same run. The engine named each one and attached no dollar figure, because nothing visible from outside a site can settle it.

  • Checkout is reachable. A checkout path is implied but we found no direct link to probe. We confirm it on a connected run.
  • Ad pixel and analytics. A tag is present, but we cannot confirm from outside that it fires on your purchase event. That is the most common silent leak and we watch it end to end on a connected run.

Where the dollar figure comes from

The sample has no real traffic, so the engine used the defaults it uses for any site where it knows nothing about the business. The range is $650 to $1,600 per month, and the headline is the low end. On your own site, the figure moves with your real numbers.

  • Assumed a conservative 15 orders a month.
  • Assumed an average order value of $150 because none was given.
  • Counted a conservative 30 to 70 percent of affected orders as truly lost.
Every request the engine made (12)

All of it was answered from memory by the sample. Nothing left this server, and nothing was a form submission, a login, or a charge.

#MethodAddressStatus
1GETcedar-and-salt.sample.test/200
2GETcedar-and-salt.sample.test/robots.txt404
3GETcedar-and-salt.sample.test/shop200
4GETcedar-and-salt.sample.test/about200
5GETcedar-and-salt.sample.test/buy404
6HEADcedar-and-salt.sample.test/200
7HEADcedar-and-salt.sample.test/shop200
8HEADcedar-and-salt.sample.test/about200
9HEADcedar-and-salt.sample.test/buy404
10GETcedar-and-salt.sample.test/buy404
11GETcedar-and-salt.sample.test/buy404
12GETcedar-and-salt.sample.test/buy404

Run it on your own site

The free teardown does this to your public pages. No account. It reads your site and never submits a form or starts a charge.

Run the free teardown
We can look, we cannot touch. The report above is the engine's own output for a sample. No customer, result or figure on this page is real.