The rotating banner at the top of a homepage, cycling through three or five messages, is one of the most requested elements in web design and one of the least effective. The research against it has been consistent for more than a decade, it comes from the usability groups whose work underpins most of what we know about how people read web pages, and it has not meaningfully changed. Those groups stop short of banning carousels outright; their guidance is that if you use one, it needs good navigation, real content, and no auto-advance.
We do not build them. Here is the reasoning, which is worth having whether or not you work with us.
Why Carousels Get Requested
It is rarely a design decision. A carousel is what happens when several people each need their message at the top of the homepage and nobody wants to decide among them. Sales wants the promotion, the owner wants the credentials, marketing wants the new service line, and the carousel appears to give everyone the prime slot.
That is the appeal, and it is also the problem. The carousel does not resolve the disagreement, it just moves it below the visitor's threshold of attention, where it is settled by default in favor of whoever ends up on slide one.
What the Research Shows
Visitors ignore them. The Nielsen Norman Group's research on banner blindness found that people routinely skip anything that looks like an advertisement, whether or not it is one, and a large moving box at the top of a page reads as an ad. In a separate Nielsen Norman study of auto-forwarding carousels, a user hunting for a discount offer missed it entirely, even though the offer sat in the carousel at the top of the page in 98-point type, the largest item on the screen. She looked straight past it.
Engagement drops sharply after the first panel. Analysis of carousel interaction across the University of Notre Dame's sites found that on its main site only about 1 percent of visitors clicked any carousel feature at all, and of the few who did, 84 percent clicked the first slide. Whatever is on slides two through five is, for practical purposes, not published.
Rotation reduces visibility rather than increasing it. This is the part that gets overlooked. A message on a five-panel carousel is visible for one fifth of the time a visitor spends looking at that area of the page. Nielsen Norman Group's write-up on auto-forwarding elements makes the point directly: putting items in rotation reduces the probability that any one of them is seen at the moment someone is looking.
And moving interfaces take control away from the reader. People dislike having the page change under them while they are reading, and the reaction is measurable in how quickly they look elsewhere.
The Accessibility Problems Are Concrete
This is not a matter of preference. Content that starts moving automatically, runs for more than five seconds, and sits alongside other content must offer a way to pause, stop, or hide it, unless the movement is essential to what the thing does. That is WCAG Success Criterion 2.2.2, at Level A, the least demanding conformance level there is. A typical auto-rotating hero meets every one of those conditions. A great many carousels ship without a functioning pause control and fail it.
Beyond the standard, the practical barriers are easy to describe. A visitor with limited motor control cannot reliably click a target that is about to slide away. Someone reading slowly, including anyone reading in a second language or with a cognitive disability, does not finish the panel before it advances. Screen reader users encounter a region that changes underneath them, and unless the carousel is built to communicate which panel is showing, there is no reliable way to follow it. None of this is exotic. It is a meaningful share of any audience.
They Also Cost Speed
A carelessly built five-panel carousel loads five large images, plus the script that drives it, for content most visitors never advance past the first frame of. A careful build defers the offscreen slides, but the hero image remains the element the page's loading score is usually measured on. On a phone connection, that weight lands squarely in the part of the page load that determines whether someone stays. The heaviest element on the page is delivering the least.
And because carousels are tall, they push whatever comes next further down. The content that actually answers a visitor's question tends to sit just below the fold, displaced by a component they are already ignoring.
What We Build Instead
One clear message at the top of the page, with one obvious next step. A visitor should be able to tell within a few seconds who you are, what you do, whom you serve, and what to do next. That is the job of the top of a homepage, and it is a job that a single well-chosen statement does better than five competing ones.
The other messages are not discarded. They are given their own space further down the page, where they can be seen simultaneously rather than taking turns. Three static blocks in a row are visible at once, are readable at any speed, work with a keyboard, and load a fraction of the weight. If a message deserves the homepage, it deserves to be on the homepage rather than in a queue for it.
Deciding which message leads is the hard part, and it is the part the carousel exists to avoid. It is also the most valuable conversation to have about a homepage, because it forces a business to say what it is actually offering and to whom.
If You Have One Now
It is not an emergency, and it is worth measuring before ripping out. Check your analytics for interaction with panels after the first. If the numbers look like the research, you have a straightforward improvement available: promote the strongest message to a static position, move the rest down the page, and watch what happens to the next step you care about.
If you would like a read on what your homepage is currently doing with its first screen, tell us about your site.
---
Sources: Nielsen Norman Group, "Auto-Forwarding Carousels and Accordions Annoy Users and Reduce Visibility" and banner blindness research; Erik Runyon, carousel interaction statistics, University of Notre Dame; W3C, Web Content Accessibility Guidelines, Success Criterion 2.2.2.
Notice: provided for informational purposes only; not legal, financial, or professional advice.
Notice: The information provided in this document is for informational purposes only and does not constitute legal, financial, or professional advice. All materials and guidance offered by Generose Corporation dba Risingline are subject to its Client Services Agreement and are provided without warranty as to accuracy, completeness, or applicability to any specific situation. While Risingline takes reasonable precautions to ensure the reliability of the information presented, compliance with regulatory requirements varies based on specific circumstances, jurisdiction, and evolving standards. Recipients are encouraged to conduct independent due diligence and consult with qualified professionals before implementing any recommendations. Generose Corporation dba Risingline expressly disclaims any liability for actions taken or not taken based on this document. Receipt of this information does not establish a client, advisory, or fiduciary relationship between Risingline and the recipient.