A Shopify theme can look fine while performing badly. Conversely, a theme can look dated while working perfectly well underneath. The decision to rebuild should be driven by what the theme is actually doing — or failing to do — not by how it looks.
Here are seven signs that your theme has problems a redesign won't fix.
1. Your Lighthouse Performance score is below 60 and the theme is the cause
Shopify stores are expected to be fast. A Lighthouse Performance score below 60 on mobile affects search rankings and directly reduces conversion rate — every additional second of load time reduces conversions by approximately 1%.
The question is whether the theme is responsible. Performance issues often come from third-party apps — review widgets, chat tools, loyalty programmes — rather than the theme itself. Before assuming a rebuild is necessary, run a Speed Audit to identify the actual cause. If the theme's Liquid renders slowly, loads large unoptimised assets, or includes blocking JavaScript, a rebuild is likely warranted. If the problem is one bad app, removing or replacing the app is a fraction of the cost.
2. The theme has been customised by multiple developers over several years
A Shopify theme starts as a coherent codebase. After three developers over four years, each adding sections, overriding styles, and working around each other's changes, it stops being coherent. The symptoms are specific:
- Adding a new section breaks an unrelated part of the theme
- The CSS has conflicting rules that can only be managed with
!important - Sections aren't editable in the theme editor because they were hardcoded
- A "quick change" takes a full day because nothing is predictable
At this point, maintenance costs more than a rebuild. Every future change carries risk.
3. You're on a pre-Online Store 2.0 theme
Shopify launched Online Store 2.0 in 2021. Themes built before this don't support app blocks, section groups, native metafield integration, or the full range of theme editor functionality. Adding these features to an old theme is possible but increasingly expensive as the gap widens.
If your theme predates 2021, it's worth evaluating whether the features you're trying to add would be cleaner on a fresh OS 2.0 build. For most stores they will be.
4. Your product page can't display custom data without workarounds
Modern Shopify product pages are data-rich. Specifications, materials, size guides, videos, downloadable PDFs, customer Q&As, warranty information — all of this can be stored in metafields and rendered dynamically in Liquid.
If your current theme hardcodes all of this as static sections or requires the content team to format it manually per product, you're missing the metafield layer entirely. Adding it to an old theme is usually messier than building it into a new one from the start.
5. Mobile performance is systematically worse than desktop
More than half of ecommerce traffic is mobile, and mobile conversion rates are lower than desktop on most stores. Some of that gap is structural — mobile shopping has genuine UX constraints. But some of it is theme-specific: desktop-first designs that were adapted for mobile rather than built for it.
If your mobile Lighthouse score is significantly worse than desktop, if your product page requires horizontal scrolling on some devices, or if your checkout drop-off on mobile is materially higher than desktop, the theme architecture is likely a contributor.
6. The theme vendor no longer maintains or updates it
Shopify releases platform updates regularly. Themes that aren't actively maintained fall out of compatibility with new features, app blocks, and Shopify admin functionality. If your theme vendor has stopped publishing updates, you're accumulating technical debt with every Shopify release.
Check when the theme was last updated in the Shopify Theme Store. If it's been more than 12 months with no updates, the theme is either abandoned or operating on minimal maintenance.
7. You're planning a significant rebrand
A rebrand that changes typography, colour palette, component design, and layout patterns doesn't leave much of the original theme intact. At that point, the cost of adapting the old theme to a completely new visual system is often comparable to building a new theme from the Figma files. The rebuild option also produces cleaner code.
If you're rebranding and the new brand direction is substantially different from the current store, factor in a rebuild as part of the project.
Before you decide: get a diagnosis
Not every store with these symptoms needs an immediate rebuild. Some can be extended, optimised, or selectively replaced. The right starting point is understanding specifically what's causing the problem before committing to a solution.
A Speed Audit diagnoses performance issues with a specific fix list. A CRO Audit identifies conversion blockers across the full store. Both are faster and cheaper than a rebuild — and sometimes they're all you need.
If after an audit the diagnosis points to the theme itself, a rebuild is justified. If the problem is more targeted, fix the target. The rebuild vs redesign guide goes deeper on how to make that decision.
