We've rebuilt a lot of product pages. And almost every time a merchant comes to us frustrated with their store's performance, or asking for a feature they can't get built, a page builder is somewhere in the conversation.
That's not a coincidence. Page builders make starting easy. They make growing past them harder than it should be. This is what we've consistently seen across client work — and why the stores we build from the ground up outperform their page-builder predecessors on the metrics that actually matter: speed, conversion, and control.
What Page Builders Actually Add to Your Page
When you drop a block into a page builder, you're not just adding a visual element. You're adding its rendering layer, its JavaScript, its stylesheet, and its network requests — stacked on top of every other block already on the page.
On a typical page-builder PDP we audit, we find the builder's core JS bundle loading before any content renders, 3–6 independent block scripts each fetching separately, multiple competing stylesheets creating render-blocking requests, and deeply nested DOM structures slowing the browser's layout calculation. None of this is visible in the editor. It only shows in your Core Web Vitals scores, your mobile bounce rate, and — quietly — your revenue.
We break down exactly what's happening and why in: What Your Page Builder Is Really Doing to Your Shopify Page Speed.
The Customisation Wall — and Why It Always Comes
The second issue we hear from almost every store that's been on a builder for more than a year: “We need X and the builder can't do it.”
Pack selectors that drive AOV. Swatch systems that show product images. Sticky bars that display the selected variant name. Conditional content that changes based on what's in the cart. None of these are unusual — they're the features that separate a converting product page from an average one. But they live outside what any block catalogue can offer.
The workaround is always injected JavaScript. Which works temporarily — until the builder updates and breaks it. We've taken over stores where a developer had been patching the same workaround for 18 months. The maintenance cost alone had exceeded what a proper rebuild would have cost. We cover this pattern in full at: When a Page Builder Stops Being Enough.
What We See When We Rebuild in Native Liquid
When we rebuild a product page as a native Shopify section, two things change immediately.
The page gets significantly lighter. No builder initialisation layer. No competing scripts. No framework overhead. Clean Liquid rendering exactly what the page needs and nothing else. The browser works on actual content from the first response instead of waiting for an app bundle to execute first.
There's no ceiling on what can be built. Pack selectors, variant-driven pricing displays, conditional content blocks, custom swatch logic, bundle builders — all possible because we're writing the code directly, not configuring a block. It stays in the theme permanently. No app dependency, no update risk, no monthly subscription. Merchants still update content in the theme editor. The flexibility is still there. What's gone is the overhead.
What This Looked Like for Flewd
Flewd — a DTC brand on Shopify Plus — came to us with a product page built on a page builder. It looked fine visually, but their mobile performance scores were significantly below where they needed to be, and there were features they'd wanted to build for months that kept hitting walls inside the builder.
We rebuilt their PDP as native Liquid sections. Core Web Vitals scores improved meaningfully, the features they'd been waiting on were built properly, and the cost of maintaining workarounds dropped to zero. That outcome — better performance, real features, lower ongoing cost — is consistent across the PDP rebuilds we've done. See our case studies for more.
The Performance Gap
| Metric | Page Builder PDP | Native Liquid PDP |
|---|---|---|
| LCP (mobile) | 3.5s – 5s+ | 1.2s – 2.5s |
| Total Blocking Time | 300ms – 800ms | Under 100ms |
| JS Page Weight | 400KB – 1MB+ | 50KB – 150KB |
| Network requests | 15 – 40+ | 3 – 10 |
These are directional ranges from real audits — every store is different, but the direction is consistent. On mobile, where most ecommerce traffic comes from, the gap compounds with every extra request.
When a Page Builder Is Still the Right Call
We're not against page builders. For the right situation, they're the practical choice: early-stage stores testing positioning, short-lived campaign pages, content pages like blogs or FAQs, stores with genuinely standard requirements. The calculus changes when a store has meaningful traffic, a revenue-driving PDP, and requirements the builder can't deliver. That's when staying on the builder starts costing more than moving off it.
Signs Your Store Has Outgrown It
- ✅ Mobile Lighthouse score below 50 on your main product page
- ✅ Core Web Vitals flagged in Google Search Console on product URLs
- ✅ Features the builder “doesn't support” — more than once
- ✅ A developer patching injected JS after builder updates
- ✅ 3+ app blocks loading on the same PDP
- ✅ Mobile conversion rate significantly lower than desktop
Three or more of those, and the builder is the constraint — not your product, copy, or pricing.
In This Series
- What Your Page Builder Is Really Doing to Your Shopify Page Speed
- How Page Builders Affect Your Shopify SEO — And What to Do About It
- When a Page Builder Stops Being Enough: The Customisation Wall
- The Real Cost of Using a Page Builder on Shopify
- Page Builder or Native Shopify Sections? An Honest Side-by-Side
🔥 Your Product Page Is Where Every Ad, Email, and Visit Lands
If it's slow, or if it's been stuck for months because of what a builder can't do — that's a real cost, even if it doesn't show up on an invoice. We audit product pages, identify what's actually driving the problem, and rebuild the right way. Get in touch and we'll tell you honestly what we find.
Read More in This Series
- What Your Page Builder Is Really Doing to Your Shopify Page Speed
- How Page Builders Affect Your Shopify SEO (And What to Do About It)
- When a Page Builder Stops Being Enough: The Customisation Wall
- The Real Cost of Using a Page Builder on Shopify
- Page Builder or Native Shopify Sections: An Honest Side-by-Side
