# Model Height and Size Info on Product Pages A/B Test

Page: https://alidemirbas.com.tr/en/lab/ab-test-library/tests/model-height-and-size-info-on-product-pages-ab-test

## Hypothesis

If shoppers can see the model's verified height and the size the model is wearing, they may judge their own size more confidently against that reference. Less of the hesitation that makes shoppers leave the product page undecided could then mean a higher purchase conversion rate (CR).

## When to run this test

Size chart opens followed by exits without an add-to-cart, session recordings of shoppers switching between sizes, or questions about what size the model wears are the signs of size hesitation on apparel pages. If the model details ease that doubt, shoppers settle on a size faster and go on to add to cart and buy more often. If the doubt comes from a wrong size chart or sold-out sizes, fix those first. Verify each product's model height and size, and do not launch if you cannot verify them or they conflict across products.

## Primary metric

**Purchase conversion rate (CR)**: Compare purchases per assigned visitor with and without verified model sizing information.

## Other metrics

- **Add-to-cart rate**: Track progress toward purchase through add-to-cart.
- **Size chart interaction rate**: Read this alongside purchases and returns; fewer chart opens are not automatically better.
- **Return rate**: Track returns and, where available, size-related return reasons.
- **Product review time**: Interpret time alongside outcomes; longer review can be useful.

## What to check before and during the test

- **Information**: Add the model's verified height and the size actually worn.
- **Other content**: Keep images, stock, size chart and product copy unchanged.
- **Detail set**: This test includes height and size; testing size alone is a separate comparison.
- **Placement**: Choose one readable placement and keep it fixed.
- **Category**: Review apparel types where sizing needs differ.

## What to watch when reading the result

- Do not ship on a conversion gain alone if return rate or size-related return reasons get worse, since model information cannot guarantee fit. Fewer size chart opens or shorter product review time are not good signs by themselves; read them alongside purchases and returns.
- Treat the result as describing only the products and garment types you tested. Do not extend a gain seen on one product to the whole catalog; validate it separately in categories where sizing needs differ. Compare returns only once orders in both arms have had time to come back.
- Write the details as one plain sentence rather than in technical terms, and check on mobile that the text stays legible and does not run over the image. If the label is hard to read, a flat result may say more about the presentation than about the information.
- Purchases happen less often than add-to-carts, so a small gap may not show up at this traffic level. Work out the visitors you need with the [sample size calculator](https://alidemirbas.com.tr/en/calculators/sample-size-calculator) before launch, divide it by daily traffic per arm to plan the run, and do not decide until you reach that number.

## Frequently Asked Questions

### Which model information is displayed?

Show verified model height and the size actually worn in one readable location. Displaying size alone is a different information comparison.

### Is reduced size-chart use a positive result?

Not necessarily. Use purchase conversion as the primary outcome and assess returns. Less inspection can reflect clarity or missed information.

### How can return reasons help interpretation?

Model information may reduce uncertainty but cannot guarantee fit. Compare size-related reasons over equal follow-up and inspect garment categories with different sizing needs.
