Reviews on your store: apps, speed and honesty
Reviews build trust and review apps slow stores. How to collect and show reviews that help, without the weight or the temptation to fake them.
The short answer
Reviews from real customers, including the imperfect ones, are among the strongest trust signals a store has, and they feed search results through structured data. Two things go wrong with them. Review apps commonly inject heavy scripts on every page and slow the store more than the reviews help it. And the temptation to fabricate, filter or hide reviews turns a trust signal into a legal and reputational risk. Collect reviews by asking once at the right time with one tap. Show them where decisions are made. Reply to the negative ones publicly and well. And choose a review system that renders into the page rather than loading a widget for every visitor.
What good review handling looks like
| Aspect | Good | Bad |
|---|---|---|
| Collection | One email after the product has been used; one tap to rate; optional comment | A sequence of reminders; incentives that bias |
| Honesty | All genuine reviews shown, negative ones answered | Filtered, hidden, purchased or written in-house |
| Display | Summary near the price; details lower; photos where customers add them | A slow widget in the middle of the page |
| Speed | Rendered into the page; interactive parts on demand | A large script on every page fetching from a third party |
| Search | Rating and count in the product’s structured data, once, consistent | A second conflicting structured data block from the app |
| Replies | Public, specific, calm, fixing what is fixable | Silence, or arguing |
Setting it up
- Choose the system for speed first: server-rendered reviews, no page-load script, structured data generated once without duplicating the theme’s.
- Set the request timing per product type: after the product has been used, not after delivery.
- Make rating one tap from the email; comment optional; photos welcome.
- Show a summary near the price and full reviews further down, with the most useful first.
- Reply to negative reviews within days, publicly and specifically.
- Never filter, edit or incentivise in ways that bias the result; check your market’s consumer rules.
- Measure the page with the review system on and off, on a phone, and revisit after every app update.
Reviews and speed, together
The review widget that fetches from a third party on every page load, on every page, including the homepage where no reviews are shown, is one of the apps we remove when speeding up a store. The alternative exists: reviews stored with the product, rendered into the page, with the interactive parts loaded only when a visitor scrolls to them. The visitor sees the same stars; the page arrives seconds sooner.
What this means for you
Collect reviews by asking once at the right time, show every genuine one, reply to the critical ones well, and choose a review system that renders into the page instead of slowing every visit. Reviews handled this way build trust with customers and search engines alike, and they never become the reason a regulator or a customer stops trusting you.
Frequently asked questions
Should we remove or hide negative reviews?
No. In the EU a trader who provides access to consumer reviews must say whether and how it makes sure the published reviews come from people who actually bought or used the product, and that information counts as material. Shoppers also trust a rating with some criticism more than a perfect one. Reply to negative reviews publicly, fix what they reveal, and let them stand. A store with honest reviews and thoughtful replies looks far more trustworthy than one with five stars everywhere.
Why do review apps slow the store?
Many load a large script on every page, fetch reviews from their servers at page load, inject widgets that shift the layout and add tracking. A well-chosen app renders reviews into the page at build or server time and loads any interactive part on demand. Measure the page with the app disabled and enabled; the difference is what you are paying.
When should we ask for a review?
After the customer has used the product: a week or two after delivery for most goods, longer for things that take time to judge. One email, one tap to rate, a short optional comment, and no incentive that could bias the result or breach rules. A reminder at most; never a sequence.
Sources
- EUR-Lex: Directive (EU) 2019/2161, which added the review information duty to Directive 2005/29/EC (accessed 2026-09-14)
- Shopify Help Center: Shopify Product Reviews (accessed 2026-09-12)