Two minutes · ten checks

Can a new visitor understand your homepage?

Score the first buying path without analytics, plugins, or an account. Answer based on what an unfamiliar visitor can actually see—not what your team already knows.

Private by design: the checklist runs entirely in this page. Answers are not sent or stored.

1. Is the intended buyer clear above the fold?

A visitor should not have to infer the audience from feature names.

2. Does the headline promise a concrete outcome?

Mechanisms such as “AI-powered” are supporting detail, not the outcome.

3. Can a visitor tell what the product actually is?

For example: browser extension, API, hosted workspace, Mac app, or service.

4. Does the main CTA say what happens next?

“Start free” or “Book a demo” carries more information than “Get started.”

5. Is one action visually dominant?

Competing buttons force visitors to decide how to navigate before deciding to buy.

6. Is there concrete product evidence near the promise?

A real interface, workflow, output, or example is stronger than decorative art.

7. Is the expected cost or commitment clear?

If pricing is not public, state what happens before a visitor is asked to commit.

8. Does the page answer the biggest reason not to buy?

Common objections include setup effort, privacy, migration, accuracy, and lock-in.

9. Are trust claims specific and verifiable?

Named evidence, transparent limits, and real examples beat unsupported superlatives.

10. Does the first mobile screen preserve the promise and CTA?

Cookie banners, navigation, and oversized art often push the decision path away.

Your self-check

Fix these first:
    Get the $9 rewrite kit Request the full $49 teardown

    Both routes start with a public GitHub intake. No payment is collected until the delivery route is confirmed.