When size chart — kids works (and when it doesn't)
By RecoverBase ResearchLast reviewed
RecoverBase is a cited reference for ecommerce UX decisions. This page answers: When size chart — kids works (and when it doesn't)
Evidence for this decision is still being added — treat the guidance here as provisional, not a finished cited verdict.
Funnel stage: Category page
On this page
Implement 'Size chart — kids' when it directly answers a shopper question or reduces uncertainty on category pages, visible at the decision moment.
Otherwise, it adds visual noise, duplicates information, or hurts performance.
No source quote has been verified yet, so the evidence is being added. This page is marked not-indexable until it carries verified citations.
- Size chart — kids answers a specific shopper question or reduces a real uncertainty at plp
- The element is visible at the decision moment, not buried below the fold or in the footer
- Size chart — kids duplicates information already obvious from the page
- It adds visual noise without reducing a real shopper uncertainty
- Page performance (LCP/CLS) is already constrained and the element adds weight
Original RecoverBase data — we captured these stores ourselves, not a third-party figure. Full breakdown is in the table below.
How common is this across real stores?
In our own sample, 0 of 7 stores implement this pattern (sampled ). This is original RecoverBase data, not a third-party figure.
| Observation | Stores | Share of sample |
|---|---|---|
| Implements this pattern | 0 / 7 | 0% |
| Does not implement it | 7 / 7 | 100% |
In short, should you use size chart — kids?
Implement 'Size chart — kids' when it addresses a specific shopper uncertainty on the category page and is visible at the decision moment; otherwise, it adds visual noise.
Detail & evidence (1)
- Implement 'Size chart — kids' when it directly answers a shopper question or reduces uncertainty on category pages, visible at the decision moment. Otherwise, it adds visual noise, duplicates information, or hurts performance.
What does UX research say about size chart — kids?
On category pages, where shoppers scan and narrow options, 'Size chart — kids' tends to be effective when it reduces real shopper uncertainty, rather than adding visual noise.
Detail & evidence (4)
- On category pages, where shoppers scan and narrow options, 'Size chart — kids' tends to be effective when it reduces real shopper uncertainty, rather than adding visual noise.inferred
- Shoppers tend to process 'Size chart — kids' rapidly, favoring clarity and a single obvious purpose over dense or decorative designs.inferred
- The utility of 'Size chart — kids' may be context-dependent; evidence suggests it must answer a specific shopper question on the category page, rather than being applied as a universal best practice.inferred
- Zero of seven sampled real stores currently implement 'Size chart — kids'.
What are the trade-offs of size chart — kids?
If 'Size chart — kids' does not reduce a real shopper uncertainty on the category page, it adds visual noise and clutter, increasing scan cost and making it harder for shoppers to narrow options.
Detail & evidence (3)
- If 'Size chart — kids' does not reduce a real shopper uncertainty on the category page, it adds visual noise and clutter, increasing scan cost and making it harder for shoppers to narrow options.
- Skip 'Size chart — kids' if it duplicates information already obvious on the page, adding no new value.
- Skip the element if page performance is already constrained, as it adds weight.
What are the alternatives to size chart — kids?
When 'Size chart — kids' does not reduce a real shopper uncertainty or duplicates existing information, omit the element to prevent visual noise and reduce scan cost.
Detail & evidence (3)
- When 'Size chart — kids' does not reduce a real shopper uncertainty or duplicates existing information, omit the element to prevent visual noise and reduce scan cost.
- If page performance is a concern, prioritize core content over adding 'Size chart — kids' to avoid further constraints.
- Ensure any sizing information is placed at the decision moment, not buried without scrolling or in the footer, if it is deemed necessary.
This pattern is not universally good. Each mode below names the trigger and the mechanism that makes it fail — check your own case before shipping it.
Skip when
Size chart — kids duplicates information already obvious from the page
Skip when
It adds visual noise without reducing a real shopper uncertainty
Skip when
Page performance (LCP/CLS) is already constrained and the element adds weight
Usefulness vs. clutter
Size chart — kids earns its space only when it reduces a real shopper uncertainty on the category/listing page, where shoppers scan and narrow options. When it does not, it adds scan cost.
Implement 'Size chart — kids' when it directly answers a shopper question or reduces uncertainty on category pages, visible at the decision moment. Otherwise, it adds visual noise, duplicates information, or hurts performance.
Sources & how to cite this
Use this in a deck, a paper, or an internal doc — it is built to be cited.
RecoverBase. "When size chart — kids works (and when it doesn't)." 2026. https://recoverbase.com/decisions/size-chart-kids
Originally published by RecoverBase — citation required.
The prevalence sample and annotated examples on this page are original RecoverBase data, licensed CC BY 4.0. Reuse is welcome with attribution; bulk copying or misattribution is not.
No external citations are attached to this decision yet.
Zoom out
See every decision for this part of the store on the Category page topic hub.