How fast is your review widget really? We benchmarked the major review-widget platforms against Rated Stores on the metrics that matter for Core Web Vitals and SEO: bundle size, LCP, CLS, and total blocking time.
This page documents the methodology, results, and why the numbers matter.
Why Widget Speed Matters
Review widgets sit on high-traffic pages — product pages, homepages, checkout flows. A slow widget hurts everything else:
- Core Web Vitals — Google ranks pages partly on LCP, CLS, and INP. A slow widget drags every page using it down in search results.
- Conversion — every 100ms of added load time costs ecommerce stores 1-2% conversion on average.
- Mobile experience — widget overhead hits hardest on low-end mobile devices.
If your review widget adds 200KB of JavaScript and shifts layout while loading, you're paying for it in SEO and revenue.
Methodology
- Tested on a clean Lighthouse run (mobile, simulated 4G, Pixel 5 emulation)
- Host page: blank HTML with widget embedded mid-page
- Measured: bundle size (gzipped), LCP (largest contentful paint), CLS (cumulative layout shift), TBT (total blocking time)
- Each widget configured to display 5 reviews in a list layout
- Tests run in May 2026 — competitor bundles may have changed since
Results
| Widget | Bundle (gzip) | LCP | CLS | TBT | Rich Snippets |
|---|---|---|---|---|---|
| Rated Stores | <30KB | <1.2s | 0 | <50ms | JSON-LD |
| Elfsight | ~150KB+ (iframe) | 2.5-3.5s | 0.05-0.15 | 200-400ms | Iframe |
| Common Ninja | ~120KB (iframe) | 2.2-3.0s | 0.05-0.12 | 180-350ms | Iframe |
| EmbedSocial | ~180KB | 2.8-3.8s | 0.08-0.18 | 250-500ms | Mixed |
| Taggbox | ~200KB+ | 3.0-4.0s | 0.10-0.20 | 300-600ms | Iframe |
Numbers approximate, measured on representative widget configs in May 2026. Re-tested quarterly.
Why Rated Stores Is Faster
1. Shadow DOM instead of iframes. Most competitors render inside <iframe> tags — each iframe is a separate document with its own HTTP requests, CSS pipeline, and JavaScript context. Shadow DOM is browser-native style isolation without the overhead.
2. Sub-30KB gzipped bundle. We measure bundle size every build. Adding features doesn't bloat the runtime — code-splitting per widget type means you only ship what you embed.
3. Async-deferred script loading. The <script> tag uses defer — doesn't block initial render. Widget hydrates after document is interactive.
4. Zero layout shift. The widget container reserves space immediately, so when reviews load there's no jump. CLS = 0.
5. CDN-cached globally. Widget bundle served from Cloudflare's edge network, cached close to your visitors.
6. JSON-LD instead of iframe content. Iframe widgets are invisible to Google. JSON-LD review schema is injected directly into your page HTML — Google indexes the reviews as part of your page.
What This Means for SEO
LCP and CLS feed directly into Google's Page Experience ranking signal. A widget that pushes LCP from 1.5s to 3s on every page using it is dragging your entire site's ranking down.
Combined with the rich-snippet difference (JSON-LD vs iframe), the SEO gap between Rated Stores and iframe-based competitors compounds: faster pages + indexable reviews + star ratings in search results.
What This Means for Conversion
For a Shopify store doing £100k/month, a 200ms slowdown across product pages (typical of switching to an iframe-based widget) costs roughly £2-4k/month in lost conversion. That's not theoretical — it's measured industry-wide in ecommerce performance studies.
Test It Yourself
We publish the bundle size on every release. You can verify:
curl -s https://widgets.ratedstores.com/latest.js | gzip | wc -c
Compare against any competitor's bundle URL. Numbers don't lie.
FAQ
Will Rated Stores stay fast as you add features? Yes — code-splitting per widget means new widget types don't grow the base bundle. The list widget stays small even when we add 10 more block types.
Why are competitors so much slower? Most chose iframes years ago for cross-domain isolation simplicity. Iframes are slow by design, and the choice is architectural — they can't easily switch to Shadow DOM without rebuilding.
Does the widget block first paint? No — defer attribute prevents render-blocking. Widget hydrates after the page is interactive.
Will the speed gap stay as wide? We re-measure quarterly. The Shadow DOM vs iframe gap is structural; competitors would have to rebuild their entire embed architecture to close it.
Get Started
Try Rated Stores free → — measure the impact on your own site with Lighthouse.
Related
- Reviews Widget HTML Embed
- Best Elfsight Alternative
- Rated Stores vs Elfsight
- All-in-One Reviews Widget