Testimonials Slider
Let your customers do the selling
A carousel of quotations with photographs and star ratings — three across on a desktop, one on a phone, with the arrows, dots or neither that you choose.

Card, three slides, dots.
Use cases
Where shops put it
The trust band on the home page
Three quotations under the hero, each with a name, a photograph and five stars — the block a first time visitor reads before they read your product copy.
"What buyers say" on a product landing page
A carousel scoped to one product or one range, quoting the thing your own description is not allowed to promise.
Reference customers on a B2B page
The Quote appearance, with the role and the company under each name, and autoplay off so a reader can take their time.
- Visible slides per screen
- 1 To 4 on desktop, 1 to 3 on tablet, 1 or 2 on a phone.
- Navigation
- Arrows, dots, both or none.
- Loop
- On or off; without it the carousel stops at the last testimonial instead of wrapping.
- Autoplay
- Its interval, and pause on hover so a quotation being read does not slide away.
- Per testimonial
- The quotation in rich text, a name, a role or company, a photograph with alt text (cropped to a circle) and a rating of 1 to 5 — or none at all.
- Appearance
- Card, Quote or Centered, set once on the carousel and inherited by every testimonial in it.
Shown in the demo store

The Quote carousel moving on once by autoplay and once by a click on the next arrow.

Quote, with arrows and autoplay.

Centered, two slides, no navigation.

Four slides, arrows and dots, loop off.
Native and honest
Your content is written in Magento's own format
Each testimonial is stored as a <figure> with a <blockquote> and a caption — the markup the web already has for a quotation and its source.
Every element saves itself the way native Page Builder saves its own: a plain <div data-content-type="wrizu_…"> with its settings in data-* attributes, stored with the page. There is no proprietary database table, no shortcode, no second editor and nothing that has to be converted later.
That has a practical consequence. Disable the module and the storefront keeps serving those pages: headings, copy, images, links and buttons stay visible and clickable, and the styling you set per element — alignment, colours, spacing — stays with them, because it lives in a <style> block stored with the page rather than in our stylesheets. What you lose is what our CSS draws: the layouts, the borders and shadows, the button variants and the bundled icons.
One honest warning
With the module switched off, do not open and save a page that contains Wrizu elements — Page Builder flattens any page holding a content type it does not know into a single HTML Code block, and that save cannot be undone. It behaves that way with every unknown content type, not only with ours, and the storefront is unaffected either way; the rule is simply to leave those pages alone until the module is back on.
Works with any Luma-based theme
The elements are built on the same front-end stack the native Page Builder uses: jQuery and the libraries Page Builder already loads. They target Luma-based themes — Magento Blank, Luma, and the custom themes shops build on either of them.
Buttons use Luma's own button mixins, so a Wrizu button looks like a button from your theme rather than like a button from a plug-in. All of the module's CSS is scoped to [data-content-type^="wrizu_"], so it styles our elements and nothing else in your theme.
Requirements
- Magento Open Source or Adobe Commerce 2.4.6 or newer, with the
Magento_PageBuildermodule enabled - PHP 8.1 to 8.5 — whichever your Magento version supports
- No other extension, no external icon font, no CDN dependency
Questions about this element
Conversion & trust
More in Conversion & trust
Thirty-five conversion elements for the Page Builder you already have
Wrizu Page Builder Extensions adds them to the native Magento 2 Page Builder — no second editor, no proprietary format, no content held hostage.