My space
EN

Pedagogical sample

What a UXClarity report looks like

This is the real deliverable structure: clarity index, summary, four pillars, pins on the first screen, CRO plan. The store below is fictional. No sales figures, no invented conversion rate.

Pedagogical example. Fictional store “Atelier Nord”. Not an audit of a live site, and not a sector benchmark.

61Clarity index

Atelier Nord — product page (fictional)

The visitor can tell this is apparel, but buying is not obvious at first glance: the button sits low, the price drowns in variants, and reassurance only appears after a long scroll. The page asks for too much effort for a simple decision.

Why visitors leave without buying

Do not rebuild the site. Lift the purchase action, reduce choices visible up front, and place a trust line next to the price — where the thumb hesitates.

Illustration of the first mobile screen, not a capture of a real store.

Atelier NordPanier (0)
Manteau laine — photo

Manteau laine courte

-20%Livraison3 couleursPack

S · M · L · XL · XXL · Sur-mesure

Prix

1Photo is fine — the product reads
2Price drowned under chips
3Buy button too low
Fixation pins (illustration) — the same idea as pins on real screenshots in a paid report.

The 4 pillars

Visual hierarchy & F-pattern

54

Eye drops off

Current state

The title is clear, but the buy button sits under a stack of promo chips. The eye ends on variants, not on the action.

Corrected mock

One visual offer above the fold: photo, name, price, button. Push badges and secondary variants below the primary action.

Mental load & Hick’s law

48

Too many choices too soon

Current state

Size, color, bundling and express shipping are all visible before the button. The visitor compares instead of acting.

Corrected mock

A default path (guided size, color already selected). Advanced options expand after the buy tap, not before.

Trust signals

57

Proof too low

Current state

Reviews and returns sit at the bottom. At the moment of doubt (price + button), nothing sits beside them.

Corrected mock

One proof line next to the price: rating, delivery time, returns. Full reviews can stay lower.

Mobile readability

72

Fine, can be tighter

Current state

Body text reads. The secondary “wishlist” button visually competes with buy.

Corrected mock

One solid buy button. Secondary action as a text link, not an equally heavy pill.

CRO plan — order, impact, effort

1. Lift the buy button above the fold

Impact High · Effort Low · First screen

In the product theme, pin price + CTA under the title, before the variant grid. Check an iPhone SE: the CTA must be visible without scrolling.

2. Cut choices visible before the tap

Impact High · Effort Medium · Variants

Pre-select a variant. Hide bundling and secondary options behind “Customize”.

3. Place proof next to the price

Impact Medium · Effort Low · Price / CTA

One line: review count + delivery time. Not a review carousel in that spot.

Run an audit on my real store