Audit run by UXFix on 8 September 2026 against 115 rules. Every finding below is shown with the screen we captured, in the order they cost conversions. Nothing here was sponsored or reviewed by the store.
Grade C, needs work. Most points are lost on transparency and decision.
Each category is scored 0–100 from the rules that apply to it.
Cart shows full cost breakdown: items, shipping estimate, tax estimate. Shipping estimator (ZIP/country) available in cart. And 3 more.
Shipping cost or estimate discoverable from PDP. Price visible without scroll or interaction on desktop and mobile. And 5 more.
Delivery expectation shown before final purchase. Trust/security signals visible near payment step. And 4 more.
Reviews present with summary rating visible above fold. Returns/exchange policy visible on PDP (not buried in footer). And 3 more.
Total form fields 8 or fewer (industry average is 11.3). Address autocomplete (Google/Loqate) present. And 6 more.
Across 25 audited stores, as of 8 September 2026. Method and full ranking: the UXFix ecommerce benchmark.
Scores above 25% of audited stores
The same rule pass UXFix runs on every store. No store data and no analytics access — everything below was observable from the public storefront.
Product page to payment step, one real product, both viewports.
When shipping, tax and totals first become visible to the shopper.
Field count, labels, autofill, error placement, recovery after a failed submit.
Payment marks, security copy, returns and contact reachability at the pay step.
Tap target sizes, thumb reach, keyboard type, viewport zoom on focus.
Whether an AI shopping agent can read price, stock and shipping from the page.
What we could not check: 23 rules could not be judged from the public storefront on the date above. They were dropped from the score, not guessed at.
115 rules were run. 23 could not be assessed and were dropped rather than guessed, leaving 92 scored. A further 3 findings are held back from this page because our wording for them was not fit to publish.
Rules already passing. No action needed on any of these.
The issues, in the order they appear below.
Right idea, wrong placement or timing: price visible without scroll or interaction on desktop and mobile, cart shows full cost breakdown: items, shipping estimate, tax estimate and full total including shipping and tax visible before payment entry. And 9 more.
Each finding shows the screen as we captured it on 8 September 2026, what the problem is, and what it costs in conversions.
Shoppers cannot see the shipping cost from this product page. They have to reach checkout to find out what shipping will cost.
Surprise shipping costs at checkout are the number-one reason people abandon carts. Baymard Institute research puts it at 48% of abandonments.
The product price is not visible above the fold on desktop or on mobile. Shoppers have to scroll to find out what the product costs.
Price is the single strongest predictor of whether a shopper stays or bounces. If they can't see it in the first second, they're gone. This is the highest-impact fix on any product page.
The cart does not show a full cost breakdown. Some of subtotal, shipping, tax, or total is missing before checkout.
Baymard research: 48% of shoppers abandon at checkout because of surprise costs. If the cart hides shipping or tax until the final step, you are training buyers to bail.
The full order total (including shipping and tax) isn't visible before the buyer starts entering payment details.
Surprise costs at the payment step are the #1 abandonment trigger in every study. Buyers want the final number before their card leaves the wallet.
The Add-to-Cart button is not visible above the fold on mobile. Shoppers have to scroll to find how to buy.
On mobile especially, buyers scan the top of the page and decide within seconds. If the primary purchase button isn't in that first view, many will leave before scrolling.
Move the primary CTA (e.g., 'Add to Bag') to appear before the cookie consent modal, or reduce the modal's height by using a slim bottom banner instead of a full card, so the black 'Accept all/Reject all' buttons don't block the product page's purchase button; ideally add a sticky 'Add to Bag' bar pinned above this cookie overlay.
The product page doesn't clearly say whether the item is in stock, low stock, or out of stock.
Stock signals affect two decisions. "In stock" builds confidence. "Only 3 left" adds urgency. Silence makes shoppers hesitate.
The product page shows no star rating or review summary above the fold. Shoppers have to scroll to find social proof.
Ratings are the fastest trust signal on a product page. A shopper who lands and doesn't see any social proof in the first view assumes it's a low-quality product or a new store.
This is an error state, not a product page—fix the underlying server error causing this page to load instead of the actual product; once resolved, ensure the product template includes a star rating and review count near the product title/price area.
There's no returns or exchange policy communicated on the product page itself. Shoppers have to hunt the footer or FAQ to find it.
"What if I don't like it?" is the last question in every purchase. If the answer isn't obvious, hesitation kills conversion, especially for higher-price items and apparel.
This appears to be a server error page rather than a live PDP; once the page loads correctly, add a 'Free 30-day returns' or similar line near the Refresh/Homepage button area shown here, styled to match the black 'Refresh Page' pill button for consistency.
The cart has no shipping estimator; shoppers can't preview shipping costs without starting checkout.
Unknown shipping costs are the single biggest cause of cart abandonment. An estimator answers the question before it becomes a reason to leave.
The cart does not clearly show tax, either as an amount or as a note that tax will be calculated at checkout.
Buyers in the US and Canada expect a tax line before they commit. Silence at the cart step means a jump in the total at checkout, and that jump is what makes them abandon.
The checkout has more than 8 form fields. Industry-best checkouts collect 6-8 fields; industry-average is 11.3.
Every extra field drops conversion by roughly 2%. Fields cost you money in a direct, measurable way. A checkout with 13 fields loses ~10% of buyers compared to one with 8.
The checkout has no address autocomplete (Google Places, Loqate, SmartyStreets, or similar). Shoppers type every line of their address manually.
Address autocomplete cuts address-entry time roughly in half on mobile and drops delivery-failure rates from typos. It also feels premium, buyers notice.
The checkout page does not show when the order will arrive. Buyers commit to buying without knowing the delivery date.
Delivery timing is often the deciding factor between two stores. If your competitor tells the buyer "arrives Tuesday" and you say nothing, you lose. Especially for gifts.
The structured product data that AI shopping agents read (ChatGPT, Google, Copilot) is incomplete on this page. Some or all of these are missing: product ID (GTIN), brand, review data, availability, shipping details.
AI-referred traffic converts 42% higher than regular traffic (Adobe, 2026). But agents only recommend stores whose product data they can read. Incomplete data means invisible to AI shoppers.
An aggressive popup (newsletter, discount, chat prompt) covers this product page shortly after it loads. Cookie banners don't count; this is the newsletter-style overlay.
Popups on first visit interrupt intent. First-time shoppers are still evaluating; a modal that blocks the price or ATC is a fast way to lose them.
The cookie-consent banner (with 'Accept all'/'Reject all' buttons) overlaps the bottom of the product image and partially covers the jumpsuit's lower half; since price, color swatches, size selector, and Add to Bag are all above it, the product core is not blocked, but consider anchoring the banner as a slim bottom bar rather than a centered card so it doesn't obscure product imagery.
The main content of the product page takes longer than 2.5 seconds to appear ("Largest Contentful Paint" is slow).
Every extra second of load time drops conversion by ~7% (Google, 2024). 2.5s is Google's threshold for a good experience. Above 4s is considered poor and hurts search rankings too.
When a shopper selects a variant (size, color, style, or edition), the selected state isn't clearly indicated with both a visual highlight AND a text label.
Ambiguity here causes wrong-variant orders. The shopper thought they picked Large, actually picked Medium, and it costs you a return plus a lost repeat customer.
Add a text label near the swatches (e.g. 'Color: Black') and give the selected swatch a visible ring or checkmark outline distinct from the unselected beige swatch, since currently both circles look identical in styling.
The product page does not have a Q&A section or a real specifications table. Shoppers cannot answer their own questions before buying.
Considered purchases (electronics, appliances, tools, tech gear) live and die on the details page. When shoppers cannot find dimensions, materials, compatibility, or answers to obvious questions, they leave to research on Amazon or a competitor and often buy there instead.
The product description is one big block of text with no headings, bullet points, or sections. Shoppers can't scan it.
Nobody reads walls of text online. If the description isn't scannable, the buyer misses the key features and either bounces or buys the wrong thing and returns it.
Add a collapsible 'Product Details' section under the size selector (below the 'Add to Bag' button) with bullet points for fabric content, fit notes, and care instructions, similar to how the reviews section below uses clear headers—this gives shoppers scannable info instead of jumping straight to reviews.
Some interactive elements on the mobile page are smaller than 44x44 pixels. Fingers struggle to hit them accurately.
44x44 pixels is the minimum touch target Apple and the WCAG 2.2 guidelines recommend. Below that, mis-taps happen: buyers hit the wrong swatch, wrong quantity, wrong link, and abandon in frustration.
The cart does not show a delivery estimate for each item. Buyers cannot see when their order will arrive.
Delivery timing is the second-biggest factor after price, especially for gifts and urgent purchases. Uncertain arrival dates push buyers to competitors who are clear.
A discount has been applied but there is no explicit line showing the discount amount and label. The saving happens silently.
Buyers who applied a code want to see it working. A silent adjustment feels like the code did not work, and they may re-apply, try a different code, or abandon in frustration.
The checkout doesn't show which step the buyer is on or how many steps remain. It feels like an infinite form.
Not knowing how long a task will take is one of the strongest predictors of abandonment. A visible "Step 2 of 3" gives buyers the confidence to push through the next 30 seconds of typing.
Add a horizontal breadcrumb bar under the FASHION NOVA header (e.g. 'Information > Shipping > Payment') with the current step ('Information') bolded or underlined in black, matching the site's minimal black/white style, so shoppers know where they are before entering delivery info.
The store logo in the checkout header links straight back to the homepage.
A stray click on the logo dumps the buyer out of checkout, and on some stores it also loses the form data. Small leak, easy fix.
The checkout uses separate First Name and Last Name fields instead of a single Full Name field.
Two fields cost two taps and two keyboard focuses on mobile. Baymard research shows a single Full Name field measurably lifts checkout completion, especially on phones.
Some input fields use `type="text"` when they should use `type="email"`, `type="tel"`, or `inputmode="numeric"`. Mobile keyboards do not adapt.
The wrong keyboard is a small papercut on every entry. Type an email on a phone with a QWERTY (no @ key) or a phone number without the number pad, and completion drops.
Personal-info fields are missing correct `autocomplete` attributes, or one is set to `autocomplete="off"`. Password managers and browser autofill do not work smoothly.
WCAG 2.2 requires autocomplete on personal-info fields for accessibility. Beyond compliance, correct autocomplete makes checkout a 2-tap experience for returning buyers, huge for mobile conversion.
The checkout does not offer a "Same as shipping" checkbox for the billing address, with the box checked by default. Buyers have to type their address twice. (This rule only applies to physical-product stores.)
For most orders, billing and shipping addresses are the same. Making the buyer re-enter their address is duplicate work and a common source of typos.
The phone number field is required with no explanation why. Buyers who value their privacy hesitate or abandon.
"Why does a t-shirt store need my phone number?" is a real objection. Without a rationale, some shoppers will not give it and will leave.
The checkout form uses placeholder-only labels: the field's purpose is shown as grey text inside the input, and disappears the moment the buyer starts typing.
Placeholder-only labels violate WCAG accessibility, but they also just cost sales. A buyer who types a wrong value, then forgets what the field was for, has to erase everything to see the label again. Frustration compounds.
Add small persistent labels (e.g. bold 'First name' / 'Last name') above the 'First name' and 'Last name' inputs, similar to how 'Country/Region' has its own label above the dropdown, so the field purpose remains visible after typing.
The payment step doesn't show any trust or security signals near the payment fields (padlock icon, "Secure checkout", PCI badge, Verified by Visa).
Buyers are at their most anxious when typing card numbers. A visible security signal near the field removes that anxiety and lifts conversion.
Add a small padlock icon with 'Secure Checkout' text directly above or beside the Shop/PayPal/G Pay buttons (around the 'Express checkout' label) and repeat a lock icon inline with the Email/Delivery form to reassure users their data is protected before they enter personal info.
There's no visible way to reach help from the checkout page: no phone number, no chat widget, no "Need help?" link.
When something goes wrong mid-checkout (a declined card, a missing address field), a visible help option is the difference between recovery and abandonment.
Add a visible 'Need help?' link or live chat bubble in the black header bar next to the FASHIONNOVA logo (or bottom-right corner as a floating widget), since currently only a cart icon appears there with no support contact option for shoppers stuck on payment or address fields.
The card-payment form is missing the `autocomplete` attributes mobile browsers need to autofill saved cards.
iOS and Android can autofill a saved card in one tap when the fields are labeled correctly. Without it, the buyer types 16 digits, expiry, and CVV manually, and many abandon.
The product page is missing a <link rel="canonical"> tag, or its variant URLs use fragment hashes (#) instead of stable paths or queries.
Canonical URLs tell search engines and AI agents which URL is the real one for this product. Fragment-only variant URLs cannot be shared or bookmarked and get lost when an agent tries to reference a specific variant.
The quantity selector on this product page is either missing on mobile, or too small to tap comfortably.
Fat-finger errors turn quick purchases into frustrating ones. Apple's tap-target guideline is 44px minimum; anything smaller mistaps often on real thumbs.
Add a quantity stepper (- / number / +) directly above or beside the 'Add to Bag' button, sized at least 44px tall to match the button, similar to the black/beige color swatches row but for numeric quantity input.
The brand name is shown as plain text, or is missing from the product page.
Shoppers who love a brand want to see more from them. A brand link is one of the easiest ways to raise average order value and repeat visits.
The product page does not show which payment methods you accept. Shoppers only find out at checkout.
Some buyers filter on payment method (Apple Pay, PayPal, Klarna, Afterpay) before they commit. Others want to see a familiar logo (Visa, Mastercard) as a trust signal. Hiding this costs sales you would have won.
Cart line items do not include machine-readable product identifiers (SKU, GTIN, product_id). Agents see only display names.
Without a stable identifier per line, agents cannot cross-check items against a catalog, apply price rules, or reconcile the order. Display names change with translation and localization, they are not safe identifiers.
When an error message appears, the form visibly jumps, moving fields under the buyer's cursor or thumb.
Layout jumps cause mis-clicks and lose the buyer's place in the form. On mobile they routinely cause wrong-field input.
UXFix scores every store twice: once for human shoppers, once for the agents now doing the browsing on their behalf. Fashionnova scores 56 for humans and 73 for agents. 3 of the 12 agent rules are not fully met.
Derived from this store's own captured product-page content. Coverage judges whether that content answers each query — it is not a measurement of search volume or of what any AI currently recommends.
Fashionnova (fashionnova.com) scored 56/100 on 8 September 2026 in UXFix's independent audit of its product page, cart and checkout, judged on 92 of the 115 rules run.
The audit found 34 failing checks. The costliest: shipping cost or estimate discoverable from PDP, price visible without scroll or interaction on desktop and mobile and cart shows full cost breakdown: items, shipping estimate, tax estimate.
Fashionnova scores 73/100 on UXFix's AI Shoppers rules, which test whether an AI agent can read price, stock and shipping from the store and complete a purchase there.
UXFix ran the same 115 deterministic rules it runs on every store: a full purchase walk on desktop and mobile, from product page to payment step, using only the public storefront. No store data or analytics access was used, and every finding is shown with the captured screen.
Against 25 scored stores in the UXFix benchmark, Fashionnova ranks 19 with 56/100. The benchmark median is 58. As of 8 September 2026.
Fashionnova is not a badly built store. It passes 46 of 92 assessable rules. What it has is a band of friction between the product page and the payment step, and every part of it is named above.
The 39 findings above come to roughly 100 developer hours of estimated effort in total. Most are settings or template changes rather than rebuilds. A further 12 rules are only partly met and worth a look after these.
The pattern repeats across the stores we audit: the score is rarely lost on visual design, and it is rarely lost in one place. It is lost on when the cost appears, how many decisions stand between a shopper and paying, and whether a machine can read any of it.
Modelled, not measured. We re-audit for free to check.
The same rules, the same evidence, the same estimates, on your product page, cart and checkout. Free, no card, about two minutes.
Quote the score with its date, or embed the live badge. The badge links back to this page and stays current if we re-audit.
Recent audits from the same benchmark corpus.
