Where to Embed a Wall of Love: 6 Placements, Ranked

The Wall of Love is the most effective conversion asset most SaaS teams under-use. It's also the one most likely to be placed in a slot that quietly tanks performance, usually the footer, where most visitors never scroll.

We ran a placement study across 80 marketing pages over 60 days. Each page tested 14 placements with a 50/50 traffic split, measuring conversion to signup or trial. This post is the map of what worked. The case study behind our own wall rebuild (+31% signup conversion) used exactly the winning placement below.

The placement results, ranked#

We measured the lift relative to a control variant where the Wall was hidden entirely. Numbers below are medians across the 80 pages.

The pattern: proof works best when it answers an objection that's actively forming. Below the hero, the visitor is asking "is this real?" Mid-page, they're asking "do people like me use this?" Above pricing, they're asking "is this worth $X?" After pricing, the question is closed, and adding more proof reads as a stall.

Why the post-pricing slot hurts#

This was the most counterintuitive finding. Many teams put their best testimonials right after the pricing table, reasoning that the visitor needs one more nudge before clicking. In our data, that placement dropped conversion 11%, worse than no testimonials at all.

The hypothesis that fits the data: by the time a visitor has read the pricing, they're either close to "yes" or already mentally gone. A wall of new content at that moment introduces new doubt. They wonder if the testimonials are addressing concerns they hadn't formed yet, which they then start forming.

Placement by page type#

The ranking above comes from homepage and landing-page tests. Other page types have their own best slots, because the visitor's question changes.

Pricing pages. The highest-converting slot on pricing pages is directly below the plan comparison table, not above it. Visitors comparing plans are asking "is this worth it for someone like me?" A three-testimonial strip, one per plan tier ideally, answers that. The post-pricing warning from the homepage study does not apply the same way here, because on a pricing page the visitor chose to evaluate price. The wall belongs to the evaluation, not the close.

Product and feature pages. Go inline, right after the feature description the testimonial validates. A visitor reading about your analytics dashboard doesn't want a generic wall. They want one customer saying the dashboard changed their week. One testimonial placed adjacent to the claim it supports beats a wall of six at the bottom of the page.

Blog posts. Use a single inline testimonial card after the section that makes a claim the testimonial supports. Blog readers are in learning mode, not buying mode, so a full wall feels like an ad. One relevant quote with a face feels like evidence.

Checkout and signup pages. Keep proof minimal here: one line of social proof near the CTA ("Joined by 2,400 teams" or a single short quote), not a wall. The visitor has already decided, and a wall at this point adds reading load to a moment that should be frictionless. Our rule: the closer to the payment field, the less proof you show.

The 20-second placement audit#

Before you move anything, run this audit on your current wall:

1. Is it visible without scrolling on a 13-inch laptop? If not, it's in a dead slot.
2. Is it within one viewport of the page's primary CTA? Proof separated from the decision it supports is decoration.
3. Does the first testimonial name a specific outcome? If the first card is generic praise, visitors won't read the second.
4. Is there exactly one wall on the page? Two walls compete with each other and both lose.
5. On mobile, does it render as a swipeable carousel? A stacked grid of six gets abandoned after the second card.

If you fail more than two, move the wall before you rewrite a word of copy. Placement is the highest-leverage variable in the whole system.

Carousel vs. grid: a real answer#

We get this question every week. Here's what the data says, broken out by device:

• Desktop: 3-up grid wins by 6%. Visitors scan diagonally and read the top-left and top-right cards. A carousel forces a click-to-progress action that most desktop visitors won't take.
• Mobile: Horizontal carousel wins by 14%. A stacked vertical grid gets abandoned after the second card because mobile visitors are scrolling fast.

The simplest implementation: a CSS grid that becomes a scroll-snap carousel below 768px. No JavaScript carousel library needed.

<div class="grid gap-4 md:grid-cols-3 max-md:grid-flow-col max-md:auto-cols-[85%] max-md:overflow-x-auto max-md:snap-x">
  <!-- testimonial cards -->
</div>

The format isn't the variable. The format is the unblocker for the format the visitor's device wants. Let the device pick.

What to put inside the wall#

Six slots. Two video, four written quotes. Mix the formats so the rail doesn't feel monolithic. Order matters:

1. Strongest video first. Auto-pause, click-to-play, captions on by default. This is the most-replayed slot.
2. Two written quotes from named, recognizable companies. Logos visible.
3. A second video, ideally an underdog story ("I'm a solo founder and...").
4. Two more quotes, one quantitative ("3.8x lift"), one emotional ("I sleep better").

The quantitative-then-emotional order matters: the number creates trust, the emotion creates desire. Reverse the order and conversion drops about 4%.

Treat the wall as a living section, not a one-time install. Every quarter, retire testimonials older than 18 months, move your strongest recent stories into the top six positions, and check that the mix of customer types still reflects who you're targeting. Our testimonial scaling playbook covers the full curation cadence.

How to measure your own placement test#

Don't copy our numbers blindly; your traffic mix is different from the 80 pages in our study. Run your own test:

• Test one placement change at a time against the current version, 50/50 split.
• Run for at least two full weeks to cover weekday and weekend traffic patterns.
• Measure signup or trial conversion as the primary metric, scroll depth past the hero as the secondary.
• Call it at 95% confidence or after 1,000 conversions per variant, whichever comes first. Below that, you're reading noise.
• If the test is inconclusive, keep the simpler version. Complexity has a maintenance cost that inconclusive wins don't pay for.

When not to use a wall at all#

A Wall of Love is not always the answer. Skip it when you have fewer than three publishable testimonials: one or two testimonials floating in a six-slot wall draws attention to how few you have, and a single strong quote placed inline converts better than a sparse wall. Skip it on pages with a single, focused job (a webinar signup, a free-tool page, a changelog): every element that isn't the CTA is a distraction, and proof doesn't earn its slot when the ask is this small. And skip the wall format specifically when your testimonials are long: if your best proof is 300-word stories, those belong on a case studies page or in a sales deck, not squeezed into cards. The wall is a skimming format. Feed it skimmable proof, or use a different container.

A cheat sheet for your homepage#

If you're shipping this week and don't want to A/B test:

• One Wall, six testimonials, two of them video.
• Placed directly below the hero, above the feature grid.
• 3-up on desktop, horizontal scroll on mobile.
• No autoplay carousel. Let the visitor swipe.
• Quote attribution = name + role + company + headshot. All four. Missing the role is the most common error and costs about 8% of the lift.
• Preview the wall against your actual page background before shipping with our free Wall of Love previewer.

For the implementation details, see how to embed video testimonials.

That's the version that won across the 80 pages. Ship it, measure for two weeks, then start testing the variants on your specific traffic. The Wall is one of the rare growth levers where the second-best version is still significantly better than nothing, so don't wait for perfect.