Display 'Applied Filters' in an Overview (28% of Sites Don't)

Last month I watched someone shop for running shoes on their phone. She tapped through five filters. Size, colour, price, brand, waterproof. Then she scrolled the results, got distracted by a photo, scrolled back up, and stopped. She looked genuinely lost. Not because the shop was broken, but because she could no longer remember what she had asked for. Nothing on the screen told her.

That small moment of confusion is one of the most common and most avoidable failures in e-commerce. Baymard's usability testing found that 28% of sites do not show an "applied filters" summary. Nearly a third of shops take the clearest signal of intent a user can give and let it vanish the instant the results load.

Why does a hidden filter state break the experience?

Because the user is now doing memory work that the interface should be doing for them. When someone applies five filters, they have effectively written a sentence: "I want waterproof trail shoes, size 42, under 120 euros, from these two brands." That sentence is the whole point of the visit. If the screen shows only the results and not the query behind them, the person has to reconstruct their own reasoning every time they pause, scroll, or come back from a product page.

This is where products quietly lose people. Not at checkout, not at payment, but in that grey zone where the user stops trusting that the system is on their side. They feel it before they can name it. Something is off. The results look fine, but the confidence is gone.

What does the user actually lose when filters are invisible?

They lose control, and control is the entire emotional core of filtering. Filtering is the one moment where a passive browser becomes an active decision-maker. The user takes the wheel. An applied-filters overview is the dashboard that confirms the wheel is connected to something.

Without it, three things go wrong at once. First, the user cannot verify their own query, so doubt creeps in about whether the results are even correct. Second, they cannot easily undo a single choice, because there is no visible chip to remove. And third, on a long results page they lose all sense of place. Was the price cap 120 or 150? Did the brand filter actually stick? The absence of an answer is itself the damage.

Why is this so much worse on mobile?

On mobile the filter controls usually live behind a panel that slides away the moment you tap "apply." Desktop often keeps a sidebar in view, so the user can glance left and see their selections. That safety net does not exist on a phone. The panel closes, the results appear, and the query is gone from the screen entirely.

This is why the applied-filters summary is not a nice-to-have on mobile. It is the only surface where the user's choices remain visible after the panel disappears. A row of removable chips sitting just above the results does the whole job. Each chip names one active filter. Each chip can be tapped to remove it. The user always knows what they asked for, and can change one thing without reopening the entire panel and starting over.

Is an applied-filters overview a polish detail or a requirement?

It is a requirement, and treating it as optional polish is exactly how it gets cut. When a build runs late, the summary chips are the kind of thing that looks skippable on a feature list. The core filtering "works," after all. The results are correct. But correctness of output is not the same as usability of experience, and this is a distinction I have spent my whole career sitting with. A specification can be technically complete and still leave the actual human invisible. That was true of the 60-page documents I used to write as a business analyst, and it is true of a filter panel that returns the right products while hiding the reasoning behind them.

The number is what makes this concrete. When I run a UX audit, "28% of sites get this wrong" is not an opinion I have to defend. It is a benchmark. It reframes a design decision as a measurable gap between a site and the standard its users have already come to expect elsewhere. That is the kind of finding that moves a client meeting, and it connects directly to how I think about spotting the invisible cracks in a product, something I have written about before in the context of what most website feedback gets wrong.

What does getting it right actually look like?

A visible summary of every active filter, placed directly above the results, with each filter individually removable. That is the entire fix. No new technology, no redesign, no research budget. The data to render it already exists, because the site needed those values to produce the results in the first place.

The deeper lesson sits underneath the pattern. Good UX is rarely about adding something impressive. More often it is about not throwing away context the user already gave you. She told the shop exactly what she wanted in five taps. The only real question was whether the shop would bother to remember.

Most of design is just that. Listening, then showing you were listening.