Shopify theme quality: what separates a theme that ranks and converts from one that only looks good

Buying a Shopify theme feels like buying a shop front: you look at the demo, you imagine your products in it, and you pay. The trouble is that a demo is a stage set. The photos are perfect and the catalogue is tidy, there are no extra apps running, and nobody is on a slow phone in a train tunnel. The question that matters is not "does the demo look good?" but "how will this behave in my store, with my products, on my customers' phones, in Google?"

After building and customising many storefronts, here is how I judge theme quality, and how we try to hold our own themes to a higher standard. If you want the wider picture of what makes a store good, read what a high-quality Shopify store looks like first.

Why demos mislead

Demo stores are built to impress in a screenshot. They use a handful of beautiful, carefully compressed images, short product names, a fixed number of products, and no third-party apps. Shopify itself acknowledges this in its own review process: when it checks a theme's performance and accessibility scores, sections must contain real images and content, because empty sections would score unrealistically well.

So treat every demo score with suspicion, and test the theme in conditions closer to real life, as the checklist below shows.

What Shopify itself checks

Themes sold in the official Shopify Theme Store pass a staged review. Two parts are useful to know about:

• Accessibility. Shopify's partner guidance says a theme must reach an average Lighthouse accessibility score of at least 90, averaged across the home, product, collection and cart pages, and it also runs manual checks, because automated tools only catch part of the problem.
• Performance and code quality. Shopify's review includes Lighthouse performance testing, and its developer guidance recommends running Theme Check, a linter that flags problems in Liquid, the theme language, and the Lighthouse CI action to track scores over time. Shopify publishes its threshold values in its partner documentation, and they change, so always check the current figures before relying on any number you read elsewhere, including here.

A theme that comes from outside the Theme Store, for instance from a marketplace or a freelancer, has not necessarily been through any of this. That is not a reason to avoid it, only a reason to test it yourself.

Core Web Vitals: what a theme can and cannot change

Google measures the experience of real visitors with three metrics, and a "good" result means 75% of visits meet each target:

A theme controls a good share of this, but not all. The biggest outside factor is the apps you install. Shopify's own documentation says auditing and removing third-party scripts is among the highest-impact performance fixes, since they run on the main thread and slow both loading and responsiveness. So a theme that scores well in a demo can score poorly in your store after you add four apps, which is why we ask clients about their app list before we promise anything.

What to inspect in the theme itself

You do not need to be a developer to ask these questions. Any good theme author should be able to answer them:

1. Is it built on Online Store 2.0 architecture? Sections everywhere, blocks you can reorder, and JSON templates mean you can change layouts without code.
2. How heavy is its JavaScript? Open the demo, run a speed test and look at the scripts. Does a simple page ship hundreds of kilobytes of code? Are carousels and mega menus essential or decorative?
3. Are images responsive? A good theme asks Shopify's image service for the right width for each screen, with explicit width and height attributes and lazy loading below the fold. The hero image, though, should load with priority, not lazily.
4. Does it need apps to function? Some themes quietly depend on a paid app for features shown in the demo. Ask what is built in and what is extra.
5. Is the HTML clean? One main heading per page, a sensible heading order, real buttons and links, landmarks, and no empty headings used for spacing.
6. Does it output correct structured data? Products, breadcrumbs and organisation details should be present and valid, without duplication from apps.
7. Are fonts and animation restrained? A few font files, no layout jumping, and respect for the visitor's reduced-motion setting.
8. Is it accessible by keyboard? Tab through the demo. Can you open the menu, the cart and the filters? Can you see where you are?
9. Does it support your markets? Multiple currencies, translation, right-to-left languages if you need them, and clean handling of long product names.
10. What are the documentation and support like? A theme with a help center, step-by-step guides and a named response time will save you more money than a prettier theme without them.

The SEO basics a theme should get right

A theme cannot rank your store for you, but it can make it easy or hard for Google to understand it. The foundations to look for:

• Editable titles and descriptions for every page type, and sensible defaults.
• Clean addresses and canonical tags so variants and filters do not create duplicate pages.
• Breadcrumbs that match the page's place in the store.
• Correct handling of pagination and filters, so thousands of near-duplicate pages are not indexed.
• Markets and language tags if you sell in more than one country or language.
• Social sharing images that you can set per page.

It also helps to be honest about ranking. Google says a good page experience can contribute to success in Search, but relevance and helpfulness of content come first. A fast theme will not rescue thin pages, and a brilliant article will not save a store that does not load. You need both, which is why we write the product and category content with the same care as the code.

How to test a theme before you buy it

1. Run the demo's product and collection pages through Google's PageSpeed Insights on mobile, and note the three Core Web Vitals.
2. Look at the page source. Count the scripts, and look for ones that come from outside the theme.
3. Tab through it with the keyboard.
4. Switch to a slow connection in your browser's developer tools and watch what appears first.
5. Install the theme on a development store, fill it with your real products and real photographs, then test again. This single step reveals more than any demo.
6. Read the documentation and message support with one genuine question, to see how and when they reply.

How we build our own themes

We build themes the same way we build everything else, with checks written into the process. Our first theme, Acanthus, is for skincare and make-up brands. Instead of asking merchants to install separate apps for a shade finder, a skin quiz, a bundle builder or an honest countdown, those tools are part of the theme, so they load with the page and cost nothing extra each month. Every feature is documented in a help center, with step-by-step guides, short films and fixes for the problems merchants meet most, and support replies within two business days. You can read more in Acanthus: a Shopify theme made for beauty brands.

Our standards for every theme are the ones in this article: clean markup, responsive images with dimensions, restrained JavaScript, accessibility checked by hand as well as by tools, structured data that is correct, no hidden app dependencies, and documentation that a first-time merchant can follow.

Red flags when you are shopping for a theme

• The demo only looks good with the exact images the theme author chose, and falls apart with ordinary photographs.
• The sales page lists features but never mentions speed, accessibility or support.
• There is no changelog, so you cannot tell whether the theme is maintained.
• Key features require a separate paid app that is not mentioned until checkout.
• Support is an email address with no stated response time, and no documentation to read first.
• Reviews are vague or all appear within the same few days.

The opposite signs are just as telling. A good theme author publishes a changelog, shows how the theme scores with real content, explains which features are built in and which are not, and documents everything a merchant is likely to try.

Built in or bolted on?

Every feature a store needs can arrive in one of two ways: built into the theme, or added through an app. Neither is wrong, but they have different costs. An app brings its own scripts, a monthly fee and another company with access to your store, while a built-in feature loads with the page and is covered by the theme's support. Common examples are size guides, bundles, quizzes, countdowns and shade finders. Before you buy, list the features you actually need and ask, for each one, whether it is built in. That single question often changes which theme is the best value.

When a theme is not enough

Sometimes a brand needs something a theme cannot give: an unusual product configurator, a big storytelling experience, a strict performance budget. Then a customised or fully custom storefront is the honest answer, and we will say so. You can see how far design can go in our concept studies, such as Plumaire, a pre-launch store built around a scroll-to-assemble product story.

Written by Vish Jay

I design and build websites, online stores and business systems for clients in the US, UK, Europe, Australia and Canada, from Colombo, Sri Lanka. When you work with iVishwa, you talk to me directly, from the first call to launch and after.