Running a five-second test on your pricing page

The five-second test is research at its cheapest and most humbling. You show someone your page for five seconds, hide it, and ask what they remember. If their answer doesn't match what you set out to communicate, the page is lying to you — even if every word on it is technically true.

Pricing pages are where this hits hardest. You've spent weeks on positioning; your prospect spends eleven seconds on the page before deciding whether to scroll. Five-second tests close that gap fast.

What to show

A full-page screenshot. Top to bottom. Desktop and mobile if you can — the two often behave like different pages.

The most common mistake is cropping. You show the pricing table, skip the header, and miss the fact that half your participants couldn't find the plan they were looking for because the filter was above the fold you chopped off. The test works because it captures first impressions of the actual page, not the part you're proud of.

The three questions to ask

Rotate these; don't ask all three in one test.

1. "What is this page for?" Catches whether the purpose lands. If the answer is "a product page" or "not sure," your hierarchy is buried.
2. "What would it cost to use this?" Catches whether the price actually registers. You'll be surprised how often people report a number that's nowhere on the page.
3. "What's the first thing you'd do next?" Catches whether the call-to-action is clear, and whether it's the one you wanted.

How to read the answers

Don't look at individual responses. Look at the mismatch between what you designed the page to communicate and what participants consistently report remembering.

If eighty percent of people miss the free tier, the free tier is invisible. If half of them remember the wrong price, your presentation of the tiers is confusing. The pattern is the signal; any single response is noise.

What to do when the results are mixed

Fifty-fifty looks like noise but usually isn't. Mixed results on a pricing page almost always mean the page is saying two things at once — and people latch onto whichever one their recent context primed them for.

If half your participants report "simple monthly pricing" and half report "enterprise-focused," you've built a page that reads differently depending on where the reader's eyes land first. That's a layout problem, not a copy problem. Look at your visual weight, not your word choice.

Next step

A five-second test is a filter, not an answer. It tells you when a page has a problem; it doesn't tell you what the fix is. When the pattern is clear, move to a longer prototype test — something like a ten-minute usability session where participants narrate their thinking — to find out what, specifically, is getting in the way. The five-second test gets you the right question to dig into. The longer test gets you the answer.