You needed a landing page by Friday, so you installed a drag-and-drop builder and shipped it. Nobody argues with that call. But a month later your speed report is red on exactly the pages you built, and the theme you picked for performance is getting the blame. Shopify page builder apps are the usual culprit, and almost nobody checks them, because the damage shows up on a delay.
Want the code side cleaned up while you sort out the builder question? Plug In Speed does theme-level CSS and JavaScript minification, so your own theme stops adding to the problem.
What Shopify page builder apps actually do to a page
The bottom line: a page builder does not just hand you a finished Liquid section. It ships its own JavaScript runtime, and that runtime loads on every page it renders.
Your theme builds a page with Liquid on Shopify’s servers. The shopper’s browser receives HTML that is already assembled. A builder app works differently. It stores your layout as its own data, then loads its own script to turn that data into the page you designed. So the browser now has two jobs instead of one: render the theme, then run somebody else’s code on top.
That is the whole mechanism. It is not a bug, and it is not a sign the app is badly made. It is what app-layer rendering costs. The practical consequence is simple: pages built with the app carry weight that your other pages do not, which is why the damage looks so patchy when you finally go looking for it.
Why the cost lands hardest on phones
The bottom line: extra JavaScript is not just extra download. It is extra work for a processor that is far weaker than your laptop’s.
The web-wide numbers make the scale obvious. At the median, a mobile page already ships 558 KB of JavaScript before anyone adds a builder. More telling is the split: 168 KB of that comes from the site’s own developers, and 375 KB comes from third parties. Most of the code running on a typical page was written by someone the site owner never met.
At the mobile median, pages ship 168 KB of first-party JavaScript against 375 KB of third-party JavaScript. Median main-thread processing time is 2,437 ms on mobile versus 849 ms on desktop.
Look at that second figure again. The same work takes roughly three times longer on a phone. So a script that feels instant while you preview the page on a desktop can cost a real shopper a visible wait. That gap is the reason a builder page can pass your eye test and still fail Google’s.
What “slow” means in Google’s terms
The bottom line: Google measures three things, and a heavy script layer can hurt all three at once.
Core Web Vitals give you the actual pass marks. Largest Contentful Paint should land within 2.5 seconds. Interaction to Next Paint should stay at 200 milliseconds or less. Cumulative Layout Shift should stay at 0.1 or below. Crucially, Google assesses these at the 75th percentile of your page loads, not the average, so your slowest quarter of visits is what counts.
Core Web Vitals “good” thresholds: LCP within 2.5 seconds, INP at 200 ms or less, CLS at 0.1 or less — assessed at the 75th percentile of page loads, segmented across mobile and desktop.
A builder layer can push on each one. Its script competes for the main thread, which hurts INP. It often paints the hero after the script runs, which hurts LCP. And content that appears once the script finishes can shove the rest of the page down, which is exactly what CLS punishes. Our guide to Core Web Vitals on Shopify covers what to fix first when more than one is failing.
The apps most merchants are choosing
The bottom line: the leading Shopify page builder apps are well-reviewed, widely used tools. The question is not whether they are good. It is whether you are paying their cost on pages that do not need them.
Here is what the three most-installed builders look like on the App Store today, verified on 24 September 2026:
- PageFly — 4.9 stars across 5,894 reviews. Free tier with one published slot, then Builder at $24/month, Accelerate at $99/month, Enterprise at $299/month.
- GemPages — 4.9 stars across 4,247 reviews. Free to install, then Build at $29/month, Optimize at $59/month, Enterprise at $199/month.
- Shogun — 4.8 stars across 1,965 reviews. Free draft mode, then Build at $39/month, Grow at $199/month, Advanced at $499/month, with a 10-day trial.
Those ratings are not an accident. These tools genuinely solve a real problem for merchants without a developer. But notice what none of those listings can tell you: what the app costs your store, on your theme, with your sections enabled. That number is specific to your build, so you have to measure it yourself.
How to measure the damage on your own store
This takes about twenty minutes and needs no code. Work through it in order.
- Pick a matched pair of URLs. Choose one page built with the app and one comparable page built by your theme alone. A builder landing page against a normal collection page works well. Comparing a builder page against your homepage does not, because the homepage carries its own extra weight.
- Run both through PageSpeed Insights, on mobile. Use the mobile tab deliberately, since that is where the processing gap shows up. Write down LCP, INP and CLS for each, not just the headline score.
- Read the “Reduce unused JavaScript” and “Reduce the impact of third-party code” items. These name the actual offending scripts by domain. If the builder’s own domain appears near the top of that list, you have your answer in black and white.
- Check whether the script loads on pages it has no business loading on. Open a product page you never touched with the builder and look for the same domain in the network panel. Some setups inject the runtime store-wide rather than only where it is needed.
- Repeat after any change. Field data in Search Console lags by weeks, so treat lab numbers as your fast signal and Search Console as confirmation. Our Shopify speed optimization guide walks through the rest of the diagnostic order.
One caveat worth stating plainly. A single PageSpeed run varies between attempts, sometimes by several points. So run each URL three times and use the middle result, rather than reacting to one bad score.
When paying the speed cost is the right call
The bottom line: a builder that earns its weight is a good trade. A builder still installed for a campaign that ended in March is not.
Keep it where it converts. A seasonal landing page, a paid-traffic destination, a product story your theme genuinely cannot lay out — all of these justify the load, because the page exists to convert rather than to rank. Search traffic is not really the point of a paid landing page.
Cut it where it does not. Pages you built once and never revisited, layouts your theme could now reproduce with native sections, and anything the builder still loads on but no longer renders are pure cost. Rebuilding two or three of those in your theme is usually a smaller job than merchants expect, and it removes the script from those URLs entirely.
There is a second reason to care. Content that only appears after a script runs has to survive Google’s rendering queue before it can be indexed, and that queue has no fixed ceiling. Our guide to what Google actually sees on a JavaScript-rendered page explains how to check your own pages with URL Inspection.
Where Plug In Speed fits
Plug In Speed handles theme-level CSS and JavaScript minification, plus image compression, and tracks your average load time over time so you can see whether a change helped. Be clear about the boundary, though: minifying your theme’s code does not remove a third-party app’s runtime. No app can do that, because only uninstalling the builder or rebuilding the page removes it. What Plug In Speed does is make sure your own theme is not adding to a problem you are already trying to diagnose. If you are still choosing a theme, our comparison of the fastest Shopify themes is the better starting point.
Frequently asked questions
Do Shopify page builder apps slow down your store?
They add weight to the pages they render, because they load their own JavaScript to build the layout in the browser. Whether that is enough to matter depends on your theme, the sections you use, and how many pages the script loads on. Measure a builder page against a theme-built page on mobile rather than assuming either way.
Does a page builder affect the rest of my store, or only the pages I built?
Usually only the pages it renders, but not always. Some configurations inject the app’s script store-wide. Open a product page you never edited with the builder and look for the app’s domain in your browser’s network panel. If it is there, the cost is running everywhere.
Which Shopify page builder apps are fastest?
There is no honest universal answer, and the published benchmarks you will find are nearly all run by companies selling a competing product. The weight depends on which features and sections you actually enable. Test the specific builder against your own theme with PageSpeed Insights instead of trusting a league table.
Will uninstalling the builder fix my speed score?
It removes the runtime, but it also removes the pages. Builder apps store your layouts in their own system, so those pages typically stop rendering once the app is gone. Rebuild the pages you still need in your theme first, then uninstall.
Can Plug In Speed remove a page builder’s JavaScript?
No, and neither can any other app. Plug In Speed minifies your theme’s own CSS and JavaScript and compresses images. A third-party app’s runtime belongs to that app, so only rebuilding the page or removing the app clears it.
How long before a speed fix shows up in Search Console?
Search Console’s Core Web Vitals report draws on field data from actual users via the CrUX report, over a 28-day lookback, so changes take weeks to settle. Use PageSpeed Insights lab results for fast feedback, then check Search Console later to confirm real users saw the improvement.
Stop your theme adding to the problem
Plug In Speed minifies your theme’s CSS and JavaScript and compresses your images, so the weight you are left diagnosing is the app’s, not your own.