
Why your Shopify investment isn’t delivering the growth you expected
A new Shopify theme or a move to Shopify Plus is usually a large project, with months of design, build and migration work behind it. When it goes live, the expectation is that the new store will sell more because it’s faster, looks better and runs on a stronger platform.
However, launch day is where most of the growth work begins. The stores that keep growing are the ones that can test an idea, learn from the result and change the site again within weeks. How quickly a team can do that depends far more on how the store was built than on which Shopify plan it runs on.
This article explains how a build can slow down both the team and the store, what Shopify itself now offers for testing, and how to check whether your build helps or blocks growth. It draws on how our Shopify development team builds stores that our own research and testing teams then work on.
Shopify can now test changes, if your theme lets it
Shopify has added testing directly to the store admin through a feature called Rollouts, which sits under Markets. According to Shopify’s help centre, a rollout can schedule changes to a store’s theme, checkout, discounts or catalogs, and an Experiment compares a changed version against the current one so a team can measure the effect before a full launch.
That removes one reason not to test, because there’s no extra tool to buy or install. But Shopify’s requirements for rollouts set out some limits that matter for any store.
- Experiments, the part of Rollouts that compares two versions, are available only on the Grow plan or higher.
- Rollouts can’t be applied to vintage themes, which are themes that don’t use Shopify’s Online Store 2.0 architecture.
- You can’t change Liquid templates, the code files behind each page, as part of a rollout.
- Headless and custom storefront checkouts, which use their own front-end code, can’t be tested with rollouts.
So the changes you can test without a developer are the ones that your theme already lets your team make in the theme editor. Anything that needs new code still needs a developer to build it, and often a separate testing tool as well.
That makes Rollouts a good starting point for theme-level tests. For tests that need code changes, run across several pages, target specific audiences or run on a headless storefront, teams use a dedicated experimentation tool instead.
How a build slows growth down
A build can hold back growth in two ways. It can make every change need a developer, so the team tests less often. It can also make the store slower to load and harder to keep up to date, and apps are the usual cause. Both build up over time.
Two shortcuts make every change need a developer.
- An older theme architecture: Shopify’s Online Store 2.0 guide explains that its template format lets teams add and remove sections on most pages in the theme editor, without relying on a developer. A vintage theme can’t do this, and it can’t use Rollouts either.
- Custom code with no settings: a section that a developer hard-codes for one campaign can’t be changed in the theme editor. Every later change to that section, and every test of it, has to go back to the developer who wrote it.
Apps can slow the store itself. According to Shopify’s developer documentation, apps that change theme files often leave “ghost code” behind when they’re removed. That code can cause quality and performance issues and take the theme off its upgrade path.
There’s also a change that could break parts of any store using older apps. Shopify’s storefront script tags guide sets a date after which Shopify stops loading script tags, an older way for apps to add code to a store, so any feature that still depends on one stops working. It’s worth checking which of your apps still use them.
What a build made for testing looks like
A build made for testing treats launch as the first release, not the last one. In practice, that means the people who build the store and the people who test it plan the theme together from the start.
That’s how our Shopify work runs, because our developers sit in the same team as research, CRO and personalisation, so a change can move from a hypothesis to a live test without passing between three suppliers. On each build, we work to the following standards.
- Themes and apps are built to support ongoing testing and personalisation.
- Apps and tracking are integrated cleanly with your existing stack, and tested against it before launch.
- Every release is checked against page speed and Core Web Vitals, Google’s measures of how fast and stable a page feels.
- Builds conform to WCAG accessibility standards from the start, rather than being fixed later.
- Custom apps are built where the Shopify App Store doesn’t fit your needs.
The result is a theme where the common changes can happen in the editor and the uncommon ones are quick for a developer to make, and that’s what keeps the test-and-learn cycle short.
How to check whether your build helps or blocks growth
You can check most of this in an hour with whoever manages the store and whoever plans changes to it. You can use this list as the agenda for that meeting.
- Check whether your live theme is an Online Store 2.0 theme or a vintage theme. Shopify’s help centre explains how to tell the theme types apart.
- List the last ten changes your team asked for, and mark which ones needed a developer. If most of them did, the theme itself is slowing your team down.
- Check that your plan includes Experiments in Rollouts, then run one small test, such as a change to a homepage section.
- List your apps and ask each provider whether it uses Shopify’s theme app extensions or edits your theme code.
- Ask each app provider whether their app still uses script tags, and get a date for their replacement.
- Remove any app you no longer use, and ask a developer to check that it left no code behind in the theme.
- Measure page speed before and after each release, so a slow app or section shows up early.
- Agree who owns the testing plan after launch, and how often the team reviews results.
Where does your store stand?
Most stores fit one of three stages, so find the one that matches yours and start with the step it points to.
- Most changes need a developer: start with steps 1 and 2 above, because testing will stay slow and expensive until the theme lets your team make common changes in the editor.
- You can make changes, but you rarely test them: work on steps 3 and 8. A first experiment in Rollouts needs no extra tool, and a clear owner keeps the testing going after the first result.
- You test regularly: look at steps 4 to 7. They keep the store fast and working as your team releases more changes.
Make launch day the start of the growth work
Shopify gives a strong base, and it now includes its own tools for testing changes. Whether you get the growth you paid for depends on how quickly your team can use them, and that comes down to how the store was built.
If your store makes every change slow, we can help you find out why and fix it. When you work with us, you get the following.
- A review of your theme, apps and code against how your team wants to test and change the store.
- Shopify Plus migrations planned to protect your search rankings and conversion.
- Every release checked against page speed and Core Web Vitals.
- Ongoing support and development after launch, from the same team that runs your tests.
- A team certified to ISO 27001, the international standard for information security management.
If any of your apps still rely on script tags, they’ll need replacing, and a review is a good time to find them. Book a Shopify Platform Review and we’ll show you what’s slowing your store down and what to fix first.
Frequently asked questions
What is a good conversion rate on Shopify?
It depends on what you sell, your prices and where your visitors come from, so a figure from another store tells you little. The most useful comparison is your own store over time, measured the same way and split by device and traffic source.
How do I increase my conversion rate on Shopify?
Start with research into where and why visitors drop out, then test changes that address those reasons. Testing each change before a full launch shows which ones work, and stops changes that hurt sales from staying live.
Can you A/B test on Shopify?
Yes, Shopify’s Rollouts feature includes Experiments on the Grow plan or higher, for stores with Online Store 2.0 themes. Tests that need new code, or stores with vintage or headless setups, need a developer and often a separate testing tool.
Is Shopify Plus worth it?
It’s worth it when your business needs features that only Shopify Plus offers. According to Shopify’s Plus plan page, the ones that matter most for growth and testing are the following.
- Checkout customisation, with the Checkout Branding API, checkout extensions and separate checkout flows for B2B and D2C customers.
- Custom apps built with Shopify Functions, and discount rules beyond the standard limits.
- Up to 100 themes and unlimited staging stores, so you can test changes on copies of your store.
- Launchpad, for scheduled promotions and product launches.
A plan upgrade alone doesn’t change how quickly your team can test and change the store, so check the build as well as the plan.
Do Shopify apps slow down my store?
They can, because an app that loads scripts on every page adds to page weight, and an app that edited theme code can leave that code behind after you remove it. Measure page speed before and after you add or remove an app, so you can see its real effect on your visitors.
Sources
- Shopify Help Center, Rollouts. Read 11th November 2026.
- Shopify Help Center, Requirements and considerations for using rollouts. Read 11th November 2026.
- Shopify Help Center, Theme architecture versions and sources. Read 11th November 2026.
- Shopify developer documentation, Online Store 2.0. Read 11th November 2026.
- Shopify developer documentation, Migrate to theme app extensions. Read 11th November 2026.
- Shopify developer documentation, Storefront script tags. Read 11th November 2026.
- Shopify Help Center, Shopify Plus plan. Read 11th November 2026.
- Our own service page, Shopify Development. Read 11th November 2026.