A loading or processing screen is the strangest surface in your product to think about proof, because it is the one place the reader is not doing anything — they clicked, and now they are stuck waiting for the system to finish. That waiting is a genuine gap in attention: for a few seconds, the reader has nowhere else to look and nothing else to do, which is exactly why designers reach for it as a place to say something. But the reader's state during a wait is not the neutral, receptive state of someone browsing. It is a state of mild impatience that grows with every second, laced with a quiet doubt — is this actually working, or is it stuck? Anything you put on that screen is read through that impatience. A progress bar answers the doubt directly: it says the system is alive and moving. A testimonial does not — and if it is the wrong testimonial, or it arrives without any sign of progress behind it, it does not fill the wait, it draws attention to it. The question is not whether a loading screen has attention to spend; it clearly does. The question is whether a testimonial is what that particular moment of attention can actually use.
The reader's state on a loading screen is captive but impatient
The person watching your loading screen is captive — they cannot proceed until the system does — but captivity is not the same as receptiveness. Their attention is pinned to one question: when will this be done? Every second that passes without a signal of progress raises the suspicion that something has gone wrong, and that suspicion is the real risk of a wait, not the wait itself. Research on perceived performance is consistent on this: a wait with visible progress feels far shorter than an identical wait with none, because the reader's anxiety is driven by uncertainty, not by duration. This is what makes a loading screen a hostile place for pure persuasion. A testimonial arguing your product's value is answering a question the reader is not asking right now — they already committed to the action, that is why they are waiting — while ignoring the question they are asking, which is whether the wait is normal. Content that ignores the reader's actual state reads as noise, and noise on a loading screen reads as a stall. The discipline here is the same one behind matching a testimonial to the reader's real question rather than the one you wish they were asking — and on a loading screen the reader's real question is is this working, not is this good.
The one testimonial that works: proof that the wait is worth it
If any testimonial belongs on a loading or processing screen, it is one that reframes the wait as the product doing valuable work. This applies to a very specific kind of loading: not the two-second spinner between pages, but the genuine processing wait — the report being generated, the data being imported, the analysis being run, the file being rendered. In that case the wait is not dead time; it is the product earning its value, and a testimonial can make the reader feel that. A line like "the analysis took a couple of minutes and saved me a full day of manual work" placed under a progress bar on a long processing screen does a job nothing else can: it tells the reader that what they are waiting for is exactly what makes the product worth using, converting impatience into anticipation. The wait stops feeling like a delay and starts feeling like the moment the value is being built. That reframing only works when the wait is real and substantial — when there is genuinely something worth waiting for — and when the testimonial speaks to the outcome of this specific process, not the product in general.
Three things make such a testimonial help rather than aggravate. First, it must sit alongside a progress indicator, never replace one — the reader's core anxiety is uncertainty, so proof without a visible sign that the system is moving deepens the doubt rather than easing it. Second, it must speak to the value of the wait itself, not generic product praise — "this saved me hours" fits a processing screen, "best software we've ever bought" does not, because the reader is waiting for a result and wants to hear the result is worth it. Third, it must be short and calm — a wait is not the moment for a paragraph or a demanding layout; one quiet line that the eye can absorb without effort, because a reader watching a bar fill has little attention to spare for reading.
Why most loading screens should show progress, not proof
Be honest about the base rate: most loading screens are short, and on a short wait a testimonial is not just unnecessary, it is counterproductive. The cardinal rule of a brief wait is reassure and get out of the way — a clean spinner or a progress bar that visibly moves does more to keep the reader calm than any quote, because it answers the only question they have. Dropping a testimonial onto a two-second load flashes content the reader cannot finish reading before it vanishes, which registers as visual noise, not proof. Worse is the loading screen that shows a rotating carousel of testimonials with no progress indicator at all — a design that mistakes filling the time for easing the wait. That screen actively harms the experience, because it gives the reader words to read while withholding the one thing they actually want: evidence the system is working. The failure mode is the same one behind proof that reads as insecurity because there is too much of it — a loading screen crowded with rotating quotes signals a product padding the wait rather than one confident enough to just show progress and finish. If the wait is short, the right content is a progress indicator and nothing else.
Where and how to use it, precisely, if at all
If you use a testimonial on a loading screen, the rule is progress first, proof second, and only on a genuinely long wait. The progress indicator is the primary element and must be the most prominent thing on the screen — a bar that moves, a percentage that climbs, a step counter that advances. The testimonial sits underneath or beside it as a quiet secondary layer, present only on processing screens that last long enough for the reader to read it, and framed to make the wait feel worthwhile. Never let proof compete with or obscure the progress signal, never rotate quotes fast enough to feel like a slideshow, and never use a testimonial as a substitute for telling the reader how long they have to wait. On every short load — page transitions, quick saves, brief spinners — leave the testimonial off entirely; the reader wants speed and certainty, and a clean progress indicator delivers both.
The rule
Put a testimonial on a loading or processing screen only when the wait is genuinely long, a visible progress indicator remains the primary element, and the quote speaks to the value of what the reader is waiting for rather than the product in general. The reader on a loading screen is captive but impatient, and their real question is "is this working," not "is this good" — so a value testimonial without visible progress deepens the anxiety it means to ease. The one proof that earns its place is the short, calm line that reframes a substantial wait as the product doing something worth waiting for — and on every short load, the screen that serves the reader best is a clean progress bar and nothing else.