Homepage trust signals case study: revenue per visitor up 57.9% on desktop in 12 days

What was the homepage missing?

The store's homepage said nothing about the three questions online shoppers ask before they spend: what will shipping cost, do other buyers rate this store, and is my payment safe? In the original version, the control, the page went straight from the hero banner to a row of product tiles. A visitor had to find those answers later, or leave to look for them.

Each of those questions is a reason to hesitate. Shipping costs are a common surprise at checkout. Reviews tell a first-time visitor that other people bought and were happy. A secure checkout message tells them their card and personal details will be handled safely. None of it was visible where most visitors land first.

What are homepage trust signals?

Homepage trust signals are short, specific facts on a store's homepage that answer a shopper's doubts before they browse: the shipping offer, proof from other buyers, and a promise that payment is secure. They work best stated plainly, near the top of the page, where a visitor sees them before deciding where to click next.

What was the hypothesis?

The hypothesis was that showing shipping, reviews and security information on the homepage would raise the order completion rate and revenue per visitor. If visitors knew from the first screen what the shipping offer was, that other buyers had left five star reviews, and that checkout was secure, more of them would keep moving toward a purchase.

The test was built to answer one question: does stating these facts early change what visitors do, or do they only matter once a visitor reaches the cart?

What changed on the homepage?

The test version kept the homepage as it was and added one band directly under the hero banner, above the first product tiles. The band held a short heading and three items, each with a simple icon:

1. Shipping. The free shipping offer and the order size it applied to.
2. Reviews. The number of five star reviews the store had collected.
3. Security. A line saying visitors could shop and check out securely.

On desktop the three items sat side by side in one row. On mobile they stacked, one above the other, in the same place under the hero.

How was the test run?

The homepage trust signals test was an A/B test of the original homepage against the version with the trust strip, run on desktop and mobile for 12 days. Results were read separately for each device, on two measures: the rate of order completion and revenue per visitor. Convertica also tracked each step of the funnel from the homepage to a completed purchase.

Should you act on a result at 93% confidence?

A result at 93% confidence is a strong signal, not proof. The usual standard is 95%, so the desktop lift carries a somewhat higher chance of being overstated than the mobile one. Convertica recommended rolling the strip out on mobile, where the result was significant, and advised rolling it out on desktop too.

That call made sense here for three reasons. The change was small and easy to reverse. Desktop moved in the same direction as mobile, which did reach significance. And every funnel step improved, not just one number. When a change is cheap, low risk and consistent across devices, waiting for a few more points of confidence can cost more than it protects. When a change is expensive or hard to undo, keep the test running.

To check a result of your own, use the statistical significance calculator. To plan a test that reaches significance on each device, the A/B test sample size calculator shows how much traffic you need.

Why did it work?

The trust strip most likely worked because it answered doubts at the point where visitors decide whether to explore the store at all. A visitor who already knows the shipping offer, that other buyers rated the store highly, and that checkout is secure has fewer reasons to stop on the way to the cart. Because the lift appeared at every funnel step, the effect seems to have carried from the homepage all the way through.

The test cannot say which of the three items did the most work, because all three were added at once. A follow-up test could show each one alone.

How do you add trust signals to your homepage?

You can apply this test to any store homepage in six steps: find the doubts your buyers have, state the facts that answer them in one short strip near the top of the page, and test it against your current homepage on desktop and mobile separately. For the rest of the homepage, see the guide to ecommerce homepage UX.

1. List your buyers' doubts. Shipping cost, returns, product quality and payment safety are the usual ones. Your support inbox and reviews will tell you which matter most.
2. Answer each with a specific fact. "Free shipping on orders over a set amount" beats "fast shipping". A real review count beats "loved by customers".
3. Keep it to three items. One short line each, with a simple icon. The strip should be read in a glance.
4. Put it under the hero. That is where this test placed it, before the first products, where most visitors will see it.
5. Check that every claim is true. A review count, a shipping threshold or a security promise must match what happens at checkout.
6. Test it, and read each device on its own. Here both devices won, but the mobile and desktop results differed. Other tests in this series won on one device only.

One check did not exist when this test ran: can an AI shopping agent find the same facts? An agent comparing stores may never see a strip of icons. If your shipping terms, returns and review data exist only as images or design elements, state them in plain text on the page as well. Agent readiness is one of the eight checks in Convertica's free CRO audit.

For another trust test further down the funnel, read the policy visibility case study, which put shipping and refund policies on the cart page. The reviews section case study moved product reviews higher on the product page. For the badges themselves, see the guide to trust badges.

Homepage trust signals case study FAQ