Your store gets traffic but no sales

Before blaming the store, check whether these visitors ever intended to purchase. Intent mismatch is the most common cause and the cheapest to rule out. Informational search traffic — people reading a guide, comparing definitions, hunting for a manual — will not buy today no matter how good the product page is. Paid traffic fails the same way in a different costume: broad match keywords, automated placements you never picked, an audience the algorithm found because it was cheap rather than because it converted. Open analytics, segment sessions by source and by landing page, and compare where the volume arrives against where the few orders came from. If the volume lands on blog posts while orders trickle in from two category pages, you do not have a conversion problem yet. You have an acquisition problem, and no frontend work will fix it.

• Segment sessions by source and landing page, never by site total
• Read the actual search terms that triggered your paid clicks
• Compare add-to-cart rate per channel before you judge the site
• Flag volume landing on informational pages that never sell

Most storefront traffic is mobile, on mid-range Android hardware and an ordinary connection — precisely the audience your desktop test never sees. Google's Core Web Vitals thresholds are a fair bar: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, Cumulative Layout Shift under 0.1. Check the field data in Search Console rather than a lab score from your office laptop, and check it per template, because category and product pages carry the catalogue and are usually the heaviest. The one-hour verification is physical: load your busiest category on a real phone over mobile data and count the seconds until you can tap a product without the layout jumping under your thumb. Past four seconds, speed is costing you orders. Fixes range from a plugin audit to a rebuilt storefront — WooCommerce speed optimization and Core Web Vitals cover what each level involves.

A shopper arrives with a short list of questions and leaves when the page will not answer them: does this fit me, what exactly is in the box, what material is it, how does it compare to the cheaper one next to it, and what happens if it is wrong. Many WooCommerce product templates bury those answers under tabs, accordions and upsell carousels, or ship a specification table copied straight from a supplier feed. Verify it by handing your phone to somebody who has never seen the store and asking them to decide between two of your products without asking you anything. Watch where they scroll back, where they pinch to zoom an image that has no detail, and where they give up. That is your rewrite list, and it usually costs copy and photography rather than engineering.

Trust is not a badge graphic. A first-time visitor from an ad has no reason to assume you will ship anything, and they scan for evidence in a few predictable places: a returns policy written in plain language, a physical address and a working contact route, delivery expectations stated before checkout, and payment methods they recognise. Missing or vague versions of these read as risk, and risk is why a fully considered cart is abandoned. To check, open your store in a private window and try to answer three questions in ninety seconds: who am I buying from, what happens if this does not fit, and when does it arrive. If you cannot, neither can they. Resist the temptation to invent proof — fake reviews and borrowed logos are worse than an honest, specific policy page.

Baymard Institute's long-running checkout research consistently finds unexpected extra costs — shipping, taxes and fees revealed at the last step — to be the most cited reason people abandon a cart they had already filled. The mechanism is simple: the shopper mentally committed to a number on the product page, and you changed it after they invested effort. Delivery timing behaves the same way when a date only appears after an address form. Verify by buying from yourself: pick a mid-priced item, go to the final step, and note the first screen where the true total and the arrival window became visible. Anything discovered late is a candidate to move earlier, even when the honest answer is unflattering.

• State shipping cost or a clear threshold on the product page
• Show a delivery window before the address form, not after
• Put taxes and fees in the cart total, not the final step
• Make the returns window visible next to the buy button

This is the point where diagnosis gets expensive, so verify before you spend. Complete a real purchase on your own phone, in a browser you never use, with a card you actually own, and log every place you hesitated: a forced account, a coupon field that swallows the layout, a mandatory company field, an error that clears the form, a payment method that opens a broken redirect. Also check server-side — declined transactions and gateway errors sit in your logs, and a payment plugin that quietly fails for one card type looks exactly like weak demand. It is worth being concrete about what changes here. When we rebuild a storefront, WordPress keeps products, stock, prices, coupons, tax and shipping rules, payment gateways and the orders your team works in daily; only the customer-facing layer is replaced, and checkout by default stays native through a hybrid handoff.

Before accepting any of the conclusions above, confirm the data deserves your trust. Consent banners that block tags until acceptance, a purchase event that never fires on the thank-you page, duplicate tags counting one order twice, ad blockers, and traffic from bots and your own team all distort the picture in different directions. A store that appears to convert at zero sometimes converts fine and simply cannot see it. Reconcile the one number that cannot lie: count actual orders in WooCommerce admin for the last thirty days and compare them against the conversions your analytics and ad platforms report. If those disagree by more than a rounding error, fix measurement first — every other decision on this page depends on it. Analytics setup explains how the tracking layer is wired when a storefront is rebuilt.

• Compare WooCommerce order count against reported conversions monthly
• Confirm the purchase event fires once, with the right value
• Exclude internal and bot traffic before reading any rate
• Check what the consent banner blocks and for how long

Sometimes the honest answer is that the storefront is fine. If your price sits well above the same item on a marketplace that delivers tomorrow, if the assortment is too thin to justify the trip, or if lead times are measured in weeks in a category where they are measured in days, then a faster site simply delivers that message more efficiently. Check it in an afternoon: take your five best-selling items, search each one as a stranger would, and place yourself honestly in the results. There is a second case for waiting. With a few hundred sessions a week you have anecdotes rather than data, and the cheaper move is to fix measurement, run traffic for a month, and change one thing at a time. Hire someone when the diagnosis points at the frontend and the numbers justify it — what an engagement costs is deliberately public so you can make that call before talking to anyone.