How to fix low performance score on Yotpo

Steps for Yotpo

1. Audit which Yotpo widgets are actively loaded on each page type: in your Yotpo Admin go to Settings → Widgets and disable any widget (e.g. Q&A, Visual UGC carousel, Loyalty panel) that is not displayed on that page — unused widget scripts still load by default and add unnecessary JavaScript payload.
2. Enable Yotpo's asynchronous / deferred loading: in your theme's Yotpo snippet (usually snippets/yotpo.liquid or the Yotpo app embed block in the theme editor), confirm the <script> tag includes 'async' or 'defer' so it does not block first render. If using the legacy inline snippet, replace it with the async loader script found in Yotpo Admin → Account Settings → Store → Installation.
3. Lazy-load the Reviews widget below the fold: in the Yotpo Admin go to Settings → Widgets → Reviews Widget → Widget Settings and enable 'Lazy Load' (or 'Load on scroll') so the reviews iframe/JS bundle is only fetched after the main content has rendered, improving LCP and TBT.
4. Optimise Yotpo UGC / Star-rating images: in Yotpo Admin → Visual Marketing → Gallery, reduce the number of images shown in the initial load (set 'Initial items to display' to 4–6) and ensure 'Image quality' is set to 'Optimised' rather than 'Original' so Yotpo's CDN serves compressed, correctly-sized images instead of full-resolution uploads.
5. Remove duplicate Yotpo script tags: search your theme code (Layout/theme.liquid, product.liquid, collection.liquid) for multiple yotpo.com/widget.js or staticw2.yotpo.com references — each extra copy doubles the network request. Keep exactly one initialisation call per page, ideally in theme.liquid just before </body>.
6. Verify Yotpo is served via its CDN and HTTP/2: in Chrome DevTools → Network, filter by 'yotpo' and confirm all assets are served from staticw2.yotpo.com (their global CDN) with status 200 and protocol h2. If you see redirects (301/302) or assets served from your own domain, re-install the widget using the canonical snippet from Yotpo Admin → Account Settings → Store → Installation to restore CDN delivery.

What is low performance score?

The Lighthouse Performance Score (shown in Google's PageSpeed Insights tool) is a single number from 0–100 that summarises how fast your web page loads and responds for real users — especially on mobile. It is calculated from five timing metrics, with the three Core Web Vitals (Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift) carrying the most weight. A score below 50 is considered "Poor" by Google; a score above 90 is "Good." Think of it as a health-check report card for your page's speed: every point you gain means real customers are waiting less and leaving less.

Google officially uses page experience signals — including Core Web Vitals — as a ranking factor, meaning a very low score can directly suppress your position in search results and reduce organic traffic. Beyond rankings, a slow page destroys conversions: industry data consistently shows that each additional second of load time drops conversion rates by 10–20 %, and mobile shoppers are the most sensitive. A score of 8/100 on mobile means the vast majority of your mobile visitors are likely bouncing before they even see your products, costing you both ad spend and organic sales. Closing this gap is one of the highest-ROI technical improvements an ecommerce store can make.

See the complete Low performance score guide for every platform and the full background.