Public website evidence
The scan can inspect visible content, structure, interactions and technical signals on the public storefront.
Check your Shopify or WooCommerce store for issues that may make it harder to shop. We review what visitors can see and explain what we found, why it may matter, and what needs a closer look.
Example: yourstore.com, www.yourstore.com, or https://yourstore.com
Built on a 150-check framework · Evidence-backed · No website access required
Public scans are non-destructive. We never place orders, enter payment information or bypass website protections.
The free scan checks more than speed or search rankings. It looks at the main steps shoppers take, from finding a product to checking out. Some checks need store access or private business data, so they are not included in a public scan.
Can a new visitor tell what the store sells, who it is for, and why it matters?
Can check on your website
Can shoppers reach categories and products without losing their place?
Can check on your website
Does search help people find products — including when queries are imperfect?
Can check on your website
Can shoppers compare, filter and sort products without friction?
Can check on your website
Do product pages make price, variants, availability, shipping and risk clear?
Can check on your website
Does the interface make the next shopping step obvious and usable?
Can check on your website
Does the store explain offers and products in plain, useful language?
Can check on your website
Are important buying decisions structured so shoppers can commit confidently?
Can check on your website
Does the storefront give shoppers enough reason to trust the purchase?
Can check on your website
Are prices, discounts and offers easy to understand and act on?
Can check on your website
Is the path from cart to purchase clear? Some transaction checks need merchant authorization.
Needs store access
Does the store work on phones — and can more people use it?
Can check on your website
Do pages load, render and index as a commerce site should?
Can check on your website
What would real customer behaviour reveal? This needs private business data and is not inferred from a public website.
Needs private business data
Some checkout checks require merchant authorization. Analytics and experimentation checks require private business data and are not inferred from the public website.
We don't just point out what looks wrong. We show what we saw, why it may matter to shoppers, and what we still need to check. A reason behind every decision.
What can actually be seen or measured?
We start with what the public website shows: content, structure, interactions and technical signals.
Can the evidence be repeated or independently checked?
Findings are tied to pages, states and observations someone else could look at again — not vague impressions.
What is the most defensible diagnosis from that evidence?
We explain why an observation matters for a shopper, then suggest what may be worth changing.
What still requires analytics, research, authorization or experimentation?
Private funnel data, checkout behaviour and conversion claims stay out of scope until the right evidence exists.
Clear findings for store owners, without the audit jargon.
Each finding shows what we saw, why it could matter, and what you could do next. You can see the reason behind every suggestion.
On the sampled product page, the active variant does not use weight, colour contrast, a checkmark or a clearer selected treatment.
Variant ambiguity is a common source of hesitation and wrong-configuration risk, especially on smaller mobile controls.
Pair border contrast with weight, fill or a check indicator so the selected option is obvious at a glance.
Needs further validation
The free public scan flags the visible interface pattern. Whether shoppers are actually confused by it should be confirmed with behavioural evidence in a deeper engagement.
Evidence
This example is a made-up store page, created to show how a finding is explained. It is not from a real business.
The scan checks a sample of common page types, such as your homepage, category pages and product pages. This keeps the review focused on the parts of the store that shape shopping decisions.
If something is missing from the sample, we say it was not found in the pages we checked. We do not claim a sitewide failure from a partial sample.
Representative sample
Desktop and mobile states are reviewed where they change how shoppers understand products, offers and purchase controls.
A public scan can only tell us what is visible on your website. We will be clear about what we could check and what needs more access or information.
The scan can inspect visible content, structure, interactions and technical signals on the public storefront.
Some transaction testing requires merchant authorization. The free public scan does not place orders or enter payment details.
A public website cannot show where customers leave, how much sales are affected, or why people behave a certain way.
A recommendation does not prove that sales will increase. Check important changes with real customer data or testing.
The free scan gives you a quick first look. For bigger decisions, we take time to understand your store before recommending design or development changes.
A quick check of 150 common store issues
A closer look at your store, business goals and customer data where available
We learn about your store, plan the right changes, then check how they work
Enter your store address to get a free first look. No account or store access needed.
Example: yourstore.com, www.yourstore.com, or https://yourstore.com
Public scans are non-destructive. We never place orders, enter payment information or bypass website protections.