Skip to content
Academy
Marketing Academy · Field Work●Human Psychology
MiniAudit· 20 minutes

Volume and Recency: Auditing a Real Product Page's Review Widget

Warby Parker

Objective: Given any live product page with a review widget, score it against the lesson's volume and recency rules, and write a one-paragraph recommendation for what to fix first.

You're a CRO analyst supporting Warby Parker's product team, benchmarking how competitors display reviews before recommending changes to your own product pages.

Pick a live product page (any retailer, not Warby Parker) with a star rating and review count. Score it on volume, recency, and specificity.

Before you start

What you'll need

Free path (everything below is enough to finish)

FreeScore volume, recency, and specificity for each page you audit

Free, sufficient for a single-page scoring exercise

The process

2 steps

Step 01 of 02

Showing volume, not just stars

The lesson notes '4.8 stars (12,431 reviews)' beats a bare '4.8 stars' because volume is the credibility signal, and a 5.0 with 3 reviews reads as insider-written.

Does the page show a review count next to the star rating, and is that count high enough to read as credible rather than suspicious?

Google Sheets— A blank sheet to score each product page you check.

Procedure

  1. Find a live product page showing a star rating
  2. Check whether a review count is displayed next to the stars, not just on a separate page
  3. Note the exact count and the star average
  4. Flag it: 0-10 reviews (suspicious), 11-199 (moderate), 200+ (strong, matches the lesson's 2x-revenue threshold)
Sample output
Product: [wireless earbuds listing]
Stars shown: 4.9
Review count shown next to stars: none, count is only visible after clicking through
Flag: WEAK, high star average with no visible count reads as suspicious per the lesson's framework

Healthy

The count sits directly next to the stars, is 200+, and is genuinely visible without a click-through.

Unhealthy

Only a bare star average shows, with the count hidden behind a click, or a suspiciously low count (under 10) paired with a perfect 5.0.

What this means

Volume next to the stars is what turns a rating into evidence; hiding the count (or having too little of it) undercuts the exact signal the rating is supposed to send.

So what do I do about it?

SymptomActionEffort
Star rating shows with no visible review countRecommend surfacing the count directly next to the stars, not behind a click5 min
YouYou can do this yourself, no engineering access required.

Step 02 of 02

Using specific, recent proof

The lesson cites Trustmary's 2025 finding that 83% of consumers distrust reviews older than one month, and that specific numbers ('2,847 marketers this month') beat round ones ('thousands').

Are the top-displayed reviews dated, and if so, how recent are they? Does any surrounding copy use a specific number or a vague round one?

Google Sheets— The same sheet, a second column for recency and specificity.

Procedure

  1. Check the dates on the first 3 reviews shown by default
  2. Note whether any are older than 30 days
  3. Scan nearby marketing copy for a customer-count claim (e.g. 'trusted by thousands' vs. 'trusted by 12,847 customers')
  4. Write your recommendation: what would you fix first, volume display or recency/specificity
Sample output
Top 3 review dates: 4 months ago, 7 months ago, 11 months ago
Nearby copy: 'Loved by thousands of customers'
Recommendation: fix recency first, no review in the default view is under 30 days old, and 'thousands' should become a real number.

Healthy

Most default-shown reviews are under 30 days old, and nearby claims use specific real numbers.

Unhealthy

Default reviews are all months old, and copy uses round, unverifiable numbers like 'thousands' or 'millions.'

What this means

Staleness and vagueness both quietly signal 'this claim isn't being maintained,' which is the opposite of the trust proof is supposed to build.

So what do I do about it?

SymptomActionEffort
Default-shown reviews are all older than 30 daysRecommend sorting by recency by default, or actively soliciting new reviews on a schedule30 min
YouYou can do this yourself, no engineering access required.

Final deliverable

A completed 2-row scoring sheet (volume, recency/specificity) for one live product page, plus a one-paragraph fix recommendation.

See a reference example
Sample output
Audit: Nykaa, moisturizer listing

Volume: 4.6 stars, 1,204 reviews shown directly under the rating. STRONG.
Recency: top 3 reviews dated 6 days, 11 days, and 19 days ago. STRONG.
Specificity: page copy reads 'Chosen by 40,000+ customers this year'. STRONG.

Recommendation: no urgent fix needed, this page already follows all three rules from the lesson.

Success criteria

You're done when you can:

  • Scores a real live page on both volume and recency/specificity
  • Cites the specific numbers observed, not a vague impression
  • Names one concrete fix, or confirms none is needed, with reasoning