I pick a store theme in one afternoon and then let it run the business for three years. That gap is why I stopped judging themes by their demo pages. A demo holds twelve products, flawless photos, and no shipping rules at all. My stores hold hundreds of SKUs and exactly three of them sell. Those are different jobs.
A theme is a stack of decisions someone made before you arrived. Where the price sits relative to the photo. How many taps separate the home page from a completed order. Whether the cart shows shipping before or after the coupon field. Whether the mobile layout keeps the add-to-cart button pinned while a buyer scrolls a long description. You inherit all of it. Buyers feel those choices even when they never name them.
Colors and fonts get the conversation time, and they are the cheapest part of the theme to change later. I can repaint a store in an afternoon. I cannot repaint its information architecture without surgery, so I spend my inspection time on structure: how categories nest, how filters behave, where the search box lives on a phone, what a buyer sees when a product is out of stock. Structure is what the theme author decided for me, and structure is what I have to live inside.
The theme is part of the sales team
I count a theme as equipment, same as the card terminal in a physical shop. It either helps the sale or gets in the way. Three things decide which: how fast pages load on a phone, how much thinking a product page demands, and how short the road to payment runs. Everything else is trim.
The clearest example I have is a clothing store I rebuilt with a different theme and nothing else. Same photos, same prices, same products, same suppliers. Add-to-cart rate went from 2.1% to 2.9% over six weeks. The new theme did three things the old one refused to do: it kept the buy button visible on mobile, it put size and stock status above the fold, and it cut the home page from 3.4MB to 890KB. A few tenths of a percent sounds polite until you multiply it across a year of sessions. On that store it paid for the rebuild in under two months.
Speed is a layout decision
Performance gets handled like a hosting problem, and I have fixed it with layout choices instead. A theme that loads a slider library, three icon fonts, and a background video before the product photo is making a bet on the buyer’s patience. On hotel wifi that bet loses. My floor is largest contentful paint under 2.5 seconds on a mid-range Android. Past 4 seconds, mobile revenue dips on every store I have measured, and the dip is always bigger than the page-weight savings that caused it.
One store carried a home page video because it looked sharp in the demo. Cutting it halved the page weight. Session depth went up, and the store looked slightly less impressive in screenshots. I took that trade again twice since, and I will take it again.
Selling online has a long settled history, and the general shape of the job is old ground. The Wikipedia article on e-commerce is a fair map of it if you want the long version. What keeps changing is what buyers expect at the end of the checkout: which payment wallets, how fast a parcel should land, how much of the order runs on a phone. A theme picked in 2019 is now serving 2026 expectations, and the mismatch shows up in the numbers before it shows up in complaint emails.
What I check before I install anything
My pre-install list is short and unglamorous. Load the demo on a phone with the connection throttled, and count taps from home page to paid order. Find a product with a long description and check that the buy button stays on screen while scrolling. Add twenty products to the cart and see whether shipping appears before the payment step. Read the changelog and check the last release date. A theme updated monthly is a theme someone is still making decisions for.
I also load a category page with a hundred products on it and sort it three ways. Sorting is where weak themes crack: broken pagination, filters that reset, images that reload from scratch. And I open the store on a laptop at 1280 pixels wide, the width of a cheap office machine, because that is where a lot of real buying happens and where themes designed for designer monitors fall apart.
Then I ask the seller the rude question: what happens to this theme in two years? If the answer involves a page builder I can drive myself, nested blocks I understand, and a changelog with real dates, good. If the answer is a portfolio of screenshots, I keep shopping. The theme is the shop floor. I want to know who maintains the floor.