How I test a Shopify theme before recommending it
The demo looks gorgeous. Then you load your own products and the variant picker is a mess, the filters break on a phone, and the editor needs a developer to move a banner.
That’s why I test a theme against the store’s needs instead of picking the one with the flashiest preview. When I manage client sites, I check practical fit before I recommend anything.
A theme isn’t just a visual layer. It shapes navigation, product information, performance and accessibility, and it decides what the store team can change without calling a developer.
Start with the store, not the theme gallery
Before opening the theme store, I write down what the site needs. What product types are sold? How many variants does a typical item have? Any subscriptions, bundles or customisation? Which filters matter? Does the business publish articles or sell internationally?
Separate must-haves from nice-to-haves. A particular product gallery or quick-add interaction might be essential; a decorative animation may not be. Include the team’s editing skills and available support. A theme that needs custom code for routine updates could be a poor operational fit even if it looks impressive.
Review the existing store’s problems. If customers cannot find size information, test how the theme displays variants and descriptions. If mobile navigation is confusing, evaluate the menu and search behaviour. A new theme is not automatically the answer to weak product data, but it can reveal whether the current layout is making information hard to use.
Build a representative test catalogue
Don’t test with one simple sample product. Use a representative set: a product with several variants, one with a long description, one with an odd image ratio, and a collection big enough to exercise filters and pagination. Include a blog article and any important policy page.
Add realistic content. Placeholder copy can make a layout seem cleaner than it will be. Product titles, price, availability, delivery information and images should resemble the actual catalogue, without exposing private business data in a public preview. If the theme has sample content, remove it before evaluating the final design.
Test the complete customer journey. Can someone move from navigation to a collection, filter products, select a variant, add it to the basket and find shipping information? Check mobile and desktop. Use keyboard navigation for menus and forms, and inspect whether focus indicators remain visible.
Review SEO controls and page output
Check the page title, meta description, canonical URL, headings and structured data on representative pages. Themes may add schema, while apps or SEO plugins may add more. Inspect the rendered output for duplicate or contradictory Product, Breadcrumb or Article data. A demo does not prove how the theme behaves with the store’s existing apps.
Look at collection structure and internal links. Can customers browse the hierarchy? Does the theme link to collection pages and paginate in a way that products remain discoverable? Check the blog index, article URLs and breadcrumb labels. Keep URL decisions separate from design changes where possible; changing a theme should not casually change a site’s established paths.
I don’t trust a theme just because its sales page says “SEO optimised”. Ask what that means. It might be responsive layouts, metadata support or structured data. None of it guarantees visibility. Search performance depends on content, site structure, technical configuration and competition as well.
Measure performance and accessibility
Test the demo or preview with representative pages, but treat the result as directional. A theme preview may use different apps, images and content from the real store. On your test store, inspect large images, fonts, sliders, product recommendations and scripts. Third-party apps can contribute as much to the experience as the theme itself.
Core Web Vitals are LCP, INP and CLS. Check field data on the live store when available and use lab diagnostics to find likely issues in the preview. A fast score on an empty demo says nothing about a real catalogue. Evaluate the first product image, the main interaction and whether content jumps as the page finishes loading.
Check contrast, readable text size, image descriptions and keyboard operation. A theme can support an accessible design, but the merchant still needs to use headings, labels and alt text appropriately. Test the actual content, not only the theme’s accessibility claim.
Test app compatibility and editing
List the apps that are essential to the store. Check whether they support the theme’s architecture and whether the integration is installed through an app block, extension or custom code. Review what each app adds to the page and whether the feature can be tested before publication.
Ask a staff member to do ordinary editing jobs: update a banner, change a product detail, add a section, adjust a menu. Is the structure clear in the editor? Can they undo a mistake? Is it obvious which settings apply to mobile versus desktop? A theme needs to work for both shoppers and the people maintaining it.
Plan the launch and fallback
Duplicate the current theme and build in the unpublished copy. Keep a record of custom code and app settings. Before launch, compare important URLs and test redirects if any paths change. Schedule the release when the owner and technical support are available, then verify products, basket, checkout, forms, tracking and mobile navigation.
Keep the previous theme available for rollback, but understand what rollback restores and what it does not. Orders and content created after the new theme goes live may not be part of a theme revert. Document the launch and the issues found so the next update does not repeat them.
Related reading
- Shopify theme updates without losing your SEO edits
- Shopify page speed: fonts, sliders and the hero image
- Shopify navigation menus and SEO: what goes where
Take one theme candidate and test it with your most complicated product and a real mobile checkout. What did the demo fail to show you?