We found 32 issues in Citstores's product page, a modelled 11.9–37.2% of conversions.

The problem

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.

Why it matters

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 problem

Shoppers cannot see the shipping cost from this product page. They have to reach checkout to find out what shipping will cost.

Why it matters

Surprise shipping costs at checkout are the number-one reason people abandon carts. Baymard Institute research puts it at 48% of abandonments.

The problem

The Add-to-Cart button is not visible above the fold on mobile. Shoppers have to scroll to find how to buy.

Why it matters

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.

What to do

Add a prominent 'Add to Cart' button in pink (#E6396B, matching the price tag) directly below the price/save row, before the Specifications list, so shoppers can purchase without scrolling past the spec details.

The problem

The main content of the product page takes longer than 2.5 seconds to appear ("Largest Contentful Paint" is slow).

Why it matters

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.

The problem

The cart has no shipping estimator; shoppers can't preview shipping costs without starting checkout.

Why it matters

Unknown shipping costs are the single biggest cause of cart abandonment. An estimator answers the question before it becomes a reason to leave.

The problem

The cart doesn't offer any express wallet button (Apple Pay, Google Pay, Shop Pay, PayPal Express).

Why it matters

Express wallets skip 60-80% of the checkout form. Shop Pay alone lifts checkout completion by ~1.7x. On mobile especially, one tap vs six form fields is the biggest single conversion lever left in ecommerce.

What to do

Add real express checkout buttons (Apple Pay, Google Pay, Tabby, Tamara) directly above or below the 'Proceed to Checkout' black button in the Order Summary panel, similar to how Amazon or Shopify stores surface one-tap wallet buttons right next to the primary CTA, instead of only listing payment logos in the footer.

The problem

The checkout has more than 8 form fields. Industry-best checkouts collect 6-8 fields; industry-average is 11.3.

Why it matters

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 problem

The checkout has no address autocomplete (Google Places, Loqate, SmartyStreets, or similar). Shoppers type every line of their address manually.

Why it matters

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 problem

The checkout page does not show when the order will arrive. Buyers commit to buying without knowing the delivery date.

Why it matters

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 problem

The checkout has no signals declaring it can be driven by AI agents. No ACP or UCP meta tags, no /.well-known/agentic-commerce endpoint, no Stripe ACP integration.

Why it matters

OpenAI's Agentic Commerce Protocol (ACP) and Google's Universal Commerce Protocol (UCP) are the emerging standards for agent-driven checkout. Stores that declare readiness get preferential routing from ChatGPT and Google AI. This is 2026's biggest new distribution channel.

The problem

The product page shows no star rating or review summary above the fold. Shoppers have to scroll to find social proof.

Why it matters

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.

What to do

Add a star rating widget (e.g. '★★★★☆ 4.5 (32 reviews)') directly under the 'DuneVoyager' title/SKU line near the price block, and make it a clickable anchor that jumps to the 'Reviews' tab already present near the bottom of the page.

The problem

There's no returns or exchange policy communicated on the product page itself. Shoppers have to hunt the footer or FAQ to find it.

Why it matters

"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.

What to do

Expand the 'Return Policy' line in the note box (next to 'Delivery Time from 2 to 5 Days' and '2 Years warranty') to show the actual return window, e.g. 'Free 14-day returns', instead of just a bare label with no visible terms.

The problem

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.

Why it matters

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.

What to do

The stacked WhatsApp and chat bubble icons in the bottom-right overlap the page edge; move them into a single collapsible widget or shift them lower/inline so they don't risk covering content when the page is scrolled on smaller screens.

The problem

Cart items can't be edited in place: quantity changes or removals are missing or require leaving the cart.

Why it matters

Shoppers adjust quantities at the last moment. If editing is hard, they either abandon or check out with the wrong items and return them later.

The problem

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.

Why it matters

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.

The problem

On this long product page, the Add-to-Cart button disappears once the shopper scrolls down. There is no sticky bar that keeps it reachable.

Why it matters

Shoppers scroll deep into reviews and details, decide to buy, and then have to scroll all the way back up. Every extra scroll is a chance to get distracted and leave.

The problem

Clicking the product image doesn't open a zoom view. Shoppers can't inspect details, fabric, or quality up close.

Why it matters

Zoom is how online shoppers replace touching the product. Baymard finds inadequate image inspection among the top reasons for product-page abandonment.

The problem

The product gallery only shows the product isolated on a white background. No lifestyle, in-use, or scale reference images.

Why it matters

White-background photos are neutral but not persuasive. Lifestyle images (worn, used, in a real setting) lift conversion 30-50% and cut returns because buyers understand the product better.

What to do

Replace or add at least one of the four thumbnail slots (currently all white-background shots like the stand/case close-up) with a lifestyle photo showing the iPad Pro 13 in someone's hands or on a desk in use, to give shoppers a sense of real-world scale and context.

The problem

The product page does not have a Q&A section or a real specifications table. Shoppers cannot answer their own questions before buying.

Why it matters

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 problem

Some interactive elements on the mobile page are smaller than 44x44 pixels. Fingers struggle to hit them accurately.

Why it matters

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 problem

The checkout doesn't show which step the buyer is on or how many steps remain. It feels like an infinite form.

Why it matters

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.

What to do

Add a horizontal step indicator above the 'Contact' heading (e.g. 'Information > Shipping > Payment') with the current step bolded/highlighted in the same blue used for 'Sign in', so users know where they are in the checkout flow.

The problem

The store logo in the checkout header links straight back to the homepage.

Why it matters

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 problem

The checkout uses separate First Name and Last Name fields instead of a single Full Name field.

Why it matters

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.

The problem

Some input fields use `type="text"` when they should use `type="email"`, `type="tel"`, or `inputmode="numeric"`. Mobile keyboards do not adapt.

Why it matters

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.

The problem

Personal-info fields are missing correct `autocomplete` attributes, or one is set to `autocomplete="off"`. Password managers and browser autofill do not work smoothly.

Why it matters

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 problem

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.)

Why it matters

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 problem

The phone number field is required with no explanation why. Buyers who value their privacy hesitate or abandon.

Why it matters

"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 problem

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.

Why it matters

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.

What to do

Add persistent bold labels (e.g., 'Email', 'First name', 'Address', 'Card number') above each input field similar to the 'Discount code' pattern implied by section headers 'Contact' and 'Delivery', so users retain context after typing; this is especially critical for the unlabeled card number, expiry, and CVC fields in the Credit card section.

The problem

There's no visible way to reach help from the checkout page: no phone number, no chat widget, no "Need help?" link.

Why it matters

When something goes wrong mid-checkout (a declined card, a missing address field), a visible help option is the difference between recovery and abandonment.

What to do

Add a persistent help affordance in the top header bar next to the Crystal Stores logo (e.g. a 'Need help? Chat with us' link or support phone number), or embed a live chat bubble in the bottom-right corner of the page so shoppers stuck on the credit card or address fields can get assistance without leaving checkout.

The problem

The checkout does not declare support for delegated-payment (ACP tokenization). Agents cannot pass a tokenized payment method on the buyer's behalf.

Why it matters

Delegated-payment is the piece that actually lets agents complete a purchase without asking the buyer to type their card. Stripe and PayPal both support this via their ACP modes. Without it, agents can prep the order but hand it back to the buyer to finalize.

The problem

Cart line items do not include machine-readable product identifiers (SKU, GTIN, product_id). Agents see only display names.

Why it matters

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.

The problem

When an error message appears, the form visibly jumps, moving fields under the buyer's cursor or thumb.

Why it matters

Layout jumps cause mis-clicks and lose the buyer's place in the form. On mobile they routinely cause wrong-field input.