An online shop differs from a company website in one structural way: the number of pages. A corporate site has ten pages written once. A shop with a thousand products has a thousand pages, each of which has to load quickly, get indexed, and show the right stock.
Most projects that go wrong go wrong on that number rather than on the design.
Three things that separate a shop from a brochure site
Generated pages. Every product, category, filter and combination of filters can mint a URL. Left unchecked, a site with a thousand products can present Google with a hundred thousand addresses, ninety-nine percent of them duplicate content.
Content that moves. Price and stock change daily. Any caching layer that suited a corporate site now has to know which part of the page it must not hold on to.
The payment path. It is the only part of the site where a fault costs you money directly, and usually without telling you.
Weight, the number one problem
A product page is heavy by nature: several good images, a slider, related products, reviews and cart scripts. The total climbs past sensible limits quickly.
In the measurements we have taken on Persian pages, shop pages reach several megabytes without much effort while a well built content page stays under two hundred kilobytes. The gap has nothing to do with design quality. It has to do with nobody measuring again after launch.
To work out which part is costing you what, the explanation of the Core Web Vitals metrics shows which number points at which problem. On a shop, LCP and the large image at the top of the page are usually the knot.
The thing a shop builder will not tell you
A good share of the people who come asking for an online shop do not need a cart or a payment gateway.
If you have ten products and take twenty orders a month, and every one of those orders currently arrives by phone or messenger, a good catalogue with a proper product page and a contact button does the same job at a fraction of the cost and the maintenance. A cart earns its place once order volume passes the point where answering by hand stops being possible.
We say this while selling shop builds. The reasoning is simple: a shop that launches and gets abandoned six months later is bad for us too. A project sized to the real need is one that gets extended the following year.
The order of work that saves the project
On a shop build, the sequence matters more than the choice of tools.
Category structure and URLs come first, because changing them after indexing is expensive. Then the product page as a template that has to work correctly a thousand times. Then search and filtering, usually the weakest part of Persian shops. And last of all the look of the homepage, which is always requested first and has the least effect on sales.
The homepage is not the landing page
A shop's homepage is not where most buyers land. The buyer arrives from search results directly onto a product page, and that page is the one that has to sell.
Where this advice does not hold
If you sell one or two items and your sales come from advertising rather than search, everything above about page counts stops being relevant. Your problem is one good landing page, not shop architecture.
And if you sell digital products, stock and shipping disappear while automatic delivery and account access become the main problem, which is a different project.
Questions people ask
What does an online shop cost to build? It depends on product count and how much is custom, and the range is genuinely wide. The figures and the factors that move them are in our guide to website design costs.
What makes an online shop successful? In practice three things: a product page that answers the buyer's question, a search that finds the right item, and a short payment path. Every other feature comes after those three.
How long does it take? Most of the project time does not go on design. It goes on preparing product data. If photos, specifications and prices for a thousand products are not ready, the project waits for you rather than the other way round.
If you are still deciding, reading what the stages of a real web design project look like helps you see where the weight sits. For the build itself, an online shop designed around your actual product count is what we do, and it starts at the category structure rather than the theme. And because a shop puts a different kind of load on a server, hosting suited to a WooCommerce shop is part of that same decision rather than a separate purchase at the end.
Comments & Questions
Have a question about this article? Ask, we'll answer.
No comments yet; be the first.