Is Your Google Reviews Widget Slowing Down Your Site? How to Tell

You added a Google reviews widget to your site, and now the page feels slower. Or you ran a speed test, saw a wall of warnings about "third-party code," and wondered if the reviews are to blame.

They might be. They might not. A reviews widget is one of the easiest things on a page to test, because you can switch it off, measure, and switch it back on. This guide shows you how, and then shows you what we found when we ran the same test on our own widget.

What a Reviews Widget Actually Adds to Your Page

Your website lives on your server. A reviews widget lives on someone else's. When a visitor opens your page, their browser has to go and collect the widget from that other server, run its code, and fit the result into your layout.

Developers call this a third-party script, and Google's web performance team is blunt about it. Their guide to third-party JavaScript opens with this:

"If you've optimized your code, but your site still loads too slowly, it's probably the fault of third-party scripts."

You are not alone in having them. The HTTP Archive's 2025 Web Almanac found that the share of pages with one or more third parties "remains greater or equal to 90%." The question is never whether you have third-party code. It is what each piece costs.

A reviews widget can cost you in three ways.

1. Requests and weight. First on the same Google guide's list of problems: "Firing too many network requests to multiple servers. The more requests a site has to make, the longer it can take to load." A widget is never just one file. There is the script, the review data, and usually a photo for each reviewer. Some widgets add an iframe (a separate page loaded inside yours), a stylesheet, and a font on top.

2. Busy time. Once the code arrives, the browser has to run it. While it does, the page cannot respond to taps and scrolls. Google's guide describes it as "Sending too much JavaScript that keeps the main thread busy."

3. The jump. The reviews arrive after the rest of the page is already on screen. If nothing held their place, everything below gets pushed down, sometimes just as a visitor reaches for a button.

If you have not picked a widget yet, the complete guide to Google reviews on your website covers the options. This post is about checking the one you have.

What Google Counts as Slow

Google measures page experience with three numbers it calls Core Web Vitals. Each one maps neatly onto one of the costs above.

Google judges these at the 75th percentile of real visits, split between phones and desktops. In plain terms, three out of four visits need to hit the mark.

Does it matter for rankings? Google's page experience documentation answers directly: "Core Web Vitals are used by our ranking systems." Then it adds a caution worth reading twice:

"These scores are meant to help you to improve your site for your users overall, and trying to get a perfect score just for SEO reasons may not be the best use of your time."

So the honest framing is this. A widget that drags a page past those thresholds is a real problem. A widget that costs you two points on a speed score is not. Whether reviews on your site help SEO at all is a separate question, and the answer is more modest than most widget vendors suggest.

The 10-Minute Test for Any Widget

You do not need a developer for this. You need Chrome and the page your widget is on.

Step 1: Get a baseline. Open PageSpeed Insights, paste your page's address, and run it. Scroll to the diagnostics and look for an item about third-party code. Google's Lighthouse tool, which powers that report, flags pages "that have third-party code that blocks the main thread for 250 ms or longer." If your widget's domain is on that list with a big number next to it, you have your first answer.

Step 2: Count what the widget loads. Open your page in Chrome. Press F12 (or right-click and choose Inspect), click the Network tab, and reload. Type the widget company's name into the filter box. You will see every file the widget asked for, and the size of each. Write down two numbers: how many requests, and how many kilobytes in total.

Step 3: Switch it off. This is the part most people do not know exists. In that same Network list, Google's guide says you can "right-click any request in the Network panel and select Block Request URL." Block the widget's script and reload. Your page now loads as if the widget was never installed.

Step 4: Compare. Load the page three times with the widget blocked and three times with it unblocked. Google recommends at least three runs because some scripts fetch different things each time. If you cannot tell the difference, the widget is not your problem.

Step 5: Watch for the jump. Unblock the widget, reload, and keep your eyes on the content below the reviews. Does it lurch downward when the reviews appear? That is layout shift, and it is the cost visitors notice most.

One caveat about the scores. PageSpeed Insights shows two kinds of data. The lab result is a single simulated load, and Google says it "may not capture real-world bottlenecks." The field result comes from real Chrome users over the previous 28 days, so it will not reflect a change you made this morning. Use the lab result to compare before and after. Use the field result to see how the page is really doing.

We Ran the Test on Our Own Widget

It would be easy to tell you our widget is fast. Here are the numbers instead, so you can hold yours up against them.

On November 14, 2026, we put the free ReplyOnTheFly reviews widget on a plain test page for a real business with five Google reviews. We loaded it in Chrome at a phone-sized screen, with the processor slowed to a quarter of its speed, the connection throttled to 1.6 Mbps, and an empty cache. Think of an older phone on an average mobile signal. Each version was loaded five times.

A few things stood out.

The script is not the heavy part. The widget is one script, 20.6 KB as delivered, with no iframe and no fonts. The review data is another 1.5 KB. In the carousel, the three reviewer photos weighed about 41 KB, twice as much as the code. If you want a lighter widget, showing fewer reviewers at once does more than anything else.

It barely kept the browser busy. Even with the processor slowed four times over, the typical time the widget's code blocked the page was under 10 milliseconds in every layout. The worst single load out of 50 was 155 milliseconds, still under the 250 that Lighthouse flags.

Placement decided the jump. This was the finding that surprised us. With the carousel placed directly under the headline, the page shifted when the reviews arrived, and Cumulative Layout Shift came in at 0.05 to 0.06. That is inside Google's 0.1 limit, but it uses up about half of it before anything else on your page has moved. With the same carousel one screen further down, the shift was zero. With the carousel back at the top but its height reserved in advance, the shift was also zero.

The headline stayed the largest element on the page throughout, so Largest Contentful Paint did not move.

These are lab numbers from one test page and one business. Your page has its own images, fonts, and scripts, and a business with long reviews will render a taller widget. That is exactly why the test above matters more than anyone's published figures, including ours.

Five Fixes, in Order of Payoff

If your test found a problem, work down this list. The first two cost nothing and take minutes.

1. Move the Widget Below the First Screen

Google's guide to layout shift says content injected near the top of the page "usually causes greater layout shifts than content injected lower," and gives this advice:

"If you can't reserve space for injected content, we recommend placing it later on the page to reduce the impact on its CLS."

It matches what we measured. It also happens to be good for conversions: reviews tend to work hardest next to the decision, not above the headline. Our guide on where to put reviews on your website covers the spots that earn their place.

2. Reserve the Widget's Height

Google explains why widgets cause shifts in the first place: they "often aren't aware of how large their contents are before they load," so "platforms offering embeds don't always reserve space for their widgets." Its suggested fix is "a min-height CSS rule to reserve space."

You can do that yourself. Wrap your embed code in a container with a minimum height close to the widget's real height:

Template

<div style="min-height: 390px"> <!-- paste your widget's embed code here --> </div>

To find the right number, right-click the loaded widget in Chrome, choose Inspect, and read its height. Check it on a phone-sized screen too, since a widget is often taller there. In our test, 390 pixels fit the carousel on a phone and took the shift from 0.05 to zero.

3. Show Less, Once

Every reviewer photo is a request. Every extra widget on the same page repeats the whole cost. Use one widget per page, pick a compact layout, and cap the number of reviews it shows at once. On pages where reviews are a supporting detail, a rating badge gives you the proof for a fraction of the weight.

4. Check the Embed Code Says Async

Look at the embed code you pasted. The script tag should include the word async or defer. Google's guidance: "Always use async or defer for third-party scripts, unless the script is necessary for the critical rendering path." Without one of them, the browser stops building your page until the widget's script has downloaded and run.

If your widget's code has neither, ask the vendor before adding it yourself. Some older scripts break when loaded that way.

5. Replace a Widget That Fails the Test

Google's list of fixes for a slow third-party script includes a short one: "If the script doesn't add clear value to your site, remove it." Reviews do add value, so the better move is a lighter widget. When you compare options, use the same three checks: requests, busy time, and the jump. Our comparison of Google reviews widgets covers what each free plan really includes, so you can shortlist a few and run the test on each.

On WordPress, pay attention to where a plugin gets its reviews. A plugin that calls Google while it builds the page makes every visitor wait on that call. The free ReplyOnTheFly plugin keeps reviews in your own WordPress database, refreshes them hourly in the background, and never fetches them during a page load. The full setup is in our guide to adding Google reviews to WordPress.

When the Widget Isn't the Problem

Sometimes you block the widget, reload, and the page is just as slow. That is useful news. It means the cause is somewhere else, and the usual suspects on a small business site are:

• A huge hero image. A photo straight off a phone is often several megabytes, many times the weight of a reviews widget.
• A slider or video at the top of the page. These are often the largest thing the browser has to paint.
• Other third parties. Chat bubbles, booking widgets, maps, analytics tags, and social feeds all work the same way a reviews widget does. Use the same block-and-reload test on each.
• Too many plugins or apps. Each one tends to add its own script and stylesheet to every page.

The block-and-reload test works for all of them. Go down the Network list, block one thing at a time, and see which one gives you the page back.

And if the opposite happens, where the widget loads fine but shows nothing, that is a different problem with its own checklist: why your Google reviews aren't showing on your website.

The Bottom Line

Is your Google reviews widget slowing down your site? You can stop guessing. Block it, reload, and compare. If it adds a handful of requests, stays off Lighthouse's third-party list, and holds still when it loads, keep it and move on. If it fails, the fix is usually where it sits or how much it shows, not giving up on reviews.

Key Takeaways:

• A reviews widget costs you in three ways: extra requests, time the browser spends running its code, and a jump when the reviews appear.
• Google's "good" thresholds are 2.5 seconds for Largest Contentful Paint, 200 milliseconds for Interaction to Next Paint, and 0.1 for Cumulative Layout Shift. Google says these are used by its ranking systems, and also that chasing a perfect score just for SEO may not be worth your time.
• You can test any widget in ten minutes with Chrome's Network tab: count its requests, block it, reload, and compare.
• In our own test, the widget added 2 to 7 requests and 22 to 127 KB depending on layout, and reviewer photos outweighed the code.
• Placed directly under the headline, our carousel caused a layout shift of 0.05 to 0.06. One screen lower, or with its height reserved, the shift was zero.
• Fix placement and reserved height first. Replace the widget only if it still fails.

Once your reviews are on the page and loading fast, the replies under them matter too. Create a free account and every new review arrives in your inbox with a ready-to-send draft reply, one tap to approve, no login needed.

---