Industry
Websites for online retail
An online store is the only kind of site where the design is measured in money the same day you change it.
The catalogue is the website
On most sites the pages are written once. A store's pages are generated from product data, which means the data is the design: a thin description, a missing size, an inconsistent photograph or an uncategorised item is a page that cannot rank and a product that cannot be found.
So the build starts with how products are structured rather than how the homepage looks. Filters, categories and search only work if the data underneath them was modelled to support them — retrofitting that later means re-entering the catalogue.
Speed is not a technical concern here, it is a commercial one
Heavy themes, unoptimized imagery and a stack of third-party scripts are the usual causes, and they accumulate quietly as apps get added over a couple of years.
Building custom rather than from a purchased theme means the store ships the code it uses and nothing else. Keeping it that way is ongoing work, not a launch-day setting — which is exactly what the monthly arrangement is for.
Every other kind of site can absorb a slow page. A store cannot — the alternative is one tab away.
Concept — not a client
What a storefront is asked to do
A store's first screen has a different job from a service business's: get someone into the catalogue quickly, then remove reasons to stop.
- Product data first
- Categories, attributes and search modelled before layout — filters are only as good as the data beneath them.
- Merchandise above argument
- One headline line, then the catalogue. A storefront persuades by showing stock, not by explaining itself.
- Costs shown early
- Delivery, returns and payment methods surfaced where the doubt occurs, not discovered on the last screen.
- A checkout that fits a thumb
- Guest checkout, correct keyboards, the fewest fields the payment processor will accept.
Point at a line to locate it in the frame
The checkout is where it leaks
Traffic and browsing are the visible metrics, but the money is decided in the last three screens. Shipping, returns and payment options are conversion content, not legal boilerplate to be buried in the footer — they belong where the doubt actually occurs.
Reasons a full basket gets abandoned
- Shipping cost revealed on the final screen
- Account creation forced before payment
- A form that fights a phone keyboard
- No visible return policy at the moment of doubt
- One payment method, and it is not theirs
What the checkout should do instead
- Show delivery cost and date before the basket
- Guest checkout as the default path
- Correct input types, so the right keyboard appears
- Returns and support stated beside the pay button
- The wallets and methods the audience actually uses