Tested with every major page builder

A feature

Trustie shortcodes are pure WordPress. Drop them in Bricks, Divi, Elementor, Oxygen, or Gutenberg, and they work.

You picked Bricks (or Divi, or Elementor, or Oxygen) because you wanted to control how your site looks. The last thing you need is a reviews plugin that brings its own design system and fights yours.

Trustie’s display surfaces are plain WordPress shortcodes. Bricks accepts shortcodes. Divi accepts shortcodes. Elementor accepts shortcodes. Oxygen accepts shortcodes. Gutenberg accepts shortcodes. Trustie works in all of them without addons.

Tested in

  • Gutenberg. Drop a Shortcode block, paste
    5.0
    Based on 3 reviews
    5
    3
    4
    0
    3
    0
    2
    0
    1
    0
    Loading reviews...
    , save. Works.
  • Bricks. Use the Shortcode element. Trustie Pro also ships dedicated Bricks elements for richer integration, but the shortcodes work standalone in Free.
  • Divi. Drop a Code module or Text module with the shortcode in it. Trustie renders inside the Divi layout.
  • Elementor. Use the Shortcode widget. Same shortcodes, same result.
  • Oxygen. Use the Shortcode element. Works the same as everywhere else.

On site speed

A review plugin can quietly slow your site down. Trustie tries not to:

  • No third-party JS bundles. Trustie doesn’t load scripts from external CDNs (no Trustpilot SDK, no Google JS widget, no third-party reviews host). Every script Trustie loads is bundled with the plugin and served from your own domain, which means your existing caching layer (page cache, edge cache) just works.
  • No external stylesheets. All styling is bundled. Your CDN, your CSS minifier, your build tool all see Trustie’s CSS as part of your own site, not as a third-party resource.
  • CSS variables, not hard-coded hex. Trustie’s CSS doesn’t ship a design system that overrides your theme. It uses CSS variables that pick up your theme’s colours where it can, and falls back to Brand Hub defaults you configure.
  • Cacheable everywhere. Reviews from Google are fetched server-side (not via the customer’s browser hitting Google directly), cached, then rendered into static HTML. The result is a cached page, not a live API call on every visit.

The net effect: a shop running on Bricks with Trustie installed should benchmark the same as one without, for any sensible cache configuration.

Why this matters

Most review plugins were built when “drop a JavaScript widget on the page and let it phone home” was the only way to do reviews. Trustie was built later, on the assumption that your site is a real site, not a wrapper for someone else’s app. Shortcodes, CSS variables, cacheable HTML, no third-party JS. The plugin is supposed to fit your site, not the other way around.

Why shops turn it on with Pro

Free covers the shortcode story. Trustie Pro adds dedicated Bricks elements (so you get the same integration shortcodes give you, but with the Bricks element panel and design controls), photo lightbox JS for the photo reviews feature, and review-card interactions that benefit from a bit more state than a pure shortcode can carry. Both Free and Pro respect the same speed principles: bundled scripts, no third-party hosts, no external CDNs.