Assuming one has to go with an image carousel (see this question for reasons why this isn't the best UX to begin with), how long should the carousel wait before beginning and switching?

I recently was giving UX feedback on a website containing a carousel which started almost immediately and switched off the "logo" homepage type image, which was disorienting, so more than 0.25 seconds is clearly necessary.

  • 2
    For text containing slides user should be able to read the text, a good reading timings is in speed of rotation question. – Alexey Kolchenko Aug 11 '13 at 3:23
  • 3
    This question is EXPLICITLY about how long to leave a delay on the carousel. It is NOT about whether or not a carousel is suitable, or whether or not the carousel should be manually triggered or not. Can we focus answers on answering that particular issue. There are plenty of other questions on here about whether or not Carousels are / are not good ideas. – JonW Aug 12 '13 at 13:51

According the opinion that carousels are evil and one should not use them, regardless of what the customer thinks, the conclusion is: "Longer is better".

The ideal time is "infinity" (i.e. don't use carousel). If you are forced to use some finite time, then make is as longer as possible without getting fired.

  • 7
    You've not really addressed the question here. The opening line of the question itself is "Assuming one has to go with an image carousel..." so the use of one is not negotiable in the scope of this question. And saying 'make it as long as possible without getting fired' isn't really a constructive answer. – JonW Aug 12 '13 at 8:23
  • Why not? If someone has to go with carousel, but he think it is not a good idea, it is reasonable to make it not to start by itself, but to wait for example the user to click on button "start". On the same assuming the good developer will trade for such bad solutions and will try to trade off the maximal possible in order to make his design better. – johnfound Aug 12 '13 at 11:35

In television production, standard "hold" time for on-screen copy is 2x reading speed. In other words, if you have a block of copy on the screen, it should stay on the screen long enough to quickly read it through twice. This is to allow time for orientation, focusing on the text and slow readers.

That being said, a web page is much different than a television screen -- much more content vying for your attention. You will also need to take into account what percentage of the screen is being taken up by the carousel and what else is visible. You might be able to assume that users have learned that carousels normally change content and will focus on it relatively early to see if it contains anything they are interested in.


This is difficult to answer without more info on the carousel content, as others have said. I also agree with the comment on using reading time as a rule of thumb, if text is involved.

One additional answer could be to do a usability study (potentially with eye tracking data if you have access to those tools). You could set all transitions to be manually initiated then ask test participants to "click next" (however that fits into your carousel design) when they feel they have seen and absorbed the contents of the image. Average those times over some number of users, and add something like 50% to account for various reading/viewing speeds and other biases, and use that number.

This could be done pretty quickly and informally in a "hallway test" fashion. All you need is a few people roaming your halls, a stopwatch, and a build of your carousel with automatic transitions disabled. Change up the imagery in this test version if everyone you've got available is already familiar with your carousel, to further help with accounting for bias.


We had a carousel on our sites and we are progressively moving away to a single large image that can be changed by clicking on to all the exposed thumbnails below.

Its early days (2 weeks) yet but we have seen a small increase on time on page, and a small lowering in exits from these pages.

  • 3
    That's useful to know, however the question is explicitly about the delay to include on the slides. Yes, there are alternative implementations to consider but that is not what is being requested here. – JonW Aug 12 '13 at 13:53

A good workaround (since carousel is evil) is to pause the carousel when the user hovers over it. It is not ideal, but at least people get to see what they are about to click on.

  • 3
    The OP is not looking for workarounds though, the question is about how much of a delay to use, considering that a carousel has to be used in this instance. – JonW Aug 12 '13 at 13:52

I think this is impossible to answer precisely because there are too many variables to assess when deciding how long someone needs to look at an image or read text: do they have their glasses on; are they trying to read the text on the side of your product which is difficult to read because it's slanted; are they really interested in the image and want to have a long, clear look; etc, etc.

Therefore I think the answer is not to automatically move content.

Give the user controls, such as play and pause, or give them left and right scrolling buttons, or pips that allow them to select the slide they wish to look at.

Give the user clear controls and let them make the decision if and when they want to look at the other slides.

  • 2
    The OP is not asking for alternative methods of implementation, it is explicitly about the delay to include on the slides. Yes, there are alternative implementations to consider but that is not what is being requested here. – JonW Aug 12 '13 at 13:53
  • I think in some cases 'null' is a fair answer in response to a question that requires a value. – Toni Leigh Aug 13 '13 at 16:04

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.