I feel like this should be a duplicate but I couldn't find anything. I am trying to reconcile two conflicting observations regarding slideshow-style web sites, or heavily paginated content (which I view as sort of a variant of the same thing):
- They're used heavily, so there must be a reason. And they're used by a lot of high profile sites so, to me at least, their UI designers have some credibility.
- They're almost universally frustrating to me.
The frustrations I run into here are pretty representative of my usual experience:
Slow load times: It takes approximately 12 seconds for the content of each slide/page to load. With 10 slides that's 120 seconds of total wait time to read all of the content. Here is one slide:
Often, it takes longer to load to page than it does to read the text that is on it.
Piecewise loading: As the page loads and images, etc. are filled in, at least on Chrome (desktop), the text of the page jumps around on the screen. The consequences are 1) having to wait for the page to load to be able to read the text and 2) disorientation if you interact with e.g. scroll bars while the page is loading.
High overhead: To load the entire contents of this article (front page + all slides), and this is with AdBlock enabled:
- 2293 total requests
- 2.8 MB transferred
- For less than about 900 bytes or so of article text per page (approximately 0.03 to 0.05% of downloaded data was actual text information) + one trivially tiny image per page (example).
Comment confusion: While this particular article has comments disabled, on articles like this it is often unclear if comments are per-slide, or shared by the article as a whole. For the latter, you often see users commenting on the particular slide that they are currently viewing, and these comments don't always make sense in the context of other slides.
These points are for the desktop version. On mobile browsers the issues are often magnified.
Other similar examples include:
Counter Example: This Flickr image gallery
So this isn't to say that they're all bad. For example, Flickr seems to use them appropriately and effectively. Compared to the Forbes article:
- Load times are reasonable.
- Navigation is easy, the "previous" and "next" buttons don't require scrolling past the end of the content to access.
- In-place loading solves the "piecewise" page assembly problem with things moving around the page.
Yet there are so many sites with designs like the Forbes example, and there has to be a reason.
Now, compare this to the flat layout of e.g. this BuzzFeed page, which delivers a similar type of content (top N stuff), but on a single page. While load time is heavy, it's still tiny compared to the total load time and overhead of the Forbes article, much easier to read quickly, and aside from the silly topic, a generally pleasant viewing experience.
Another non-slideshow example to compare to is this page, which delivers a "top list" style collection of text content, but effectively does it all on one page rather than as a heavily paginated / slideshow interface.
Trying to come up with some advantages to slideshows, here's what I can think of, none of them are strong:
- Hypothetically allows a higher ratio of ad content per article: Not great UX but a reasonable marketing decision. But a flat layout (e.g. BuzzFeed) still provides plenty of sidebar space for advertisements, so I'm not sure about this.
- Some sense of semantic appropriateness? E.g. "it's a list of 10 things, so separate slides/pages reflect this".
- Theoretically I could imagine this interface was initially attractive because it allows small parts of the page to load instead of having to wait for the whole thing. But, as commonly implemented now, this purpose has been solidly defeated.
I can't think of anything compelling.
So my questions are:
- What was the initial drive behind slideshow style web UIs? And if the initial motivations are no longer applicable, why do they continue to be in use?
- When is it appropriate to use a slideshow? Text-centric content does not seem to be a good case, although it is heavily used. How can I answer "Should I use a slideshow?" and what's the key set of differences, for example, between the frustrating Forbes layout and the smoother Flickr layout?
- Assuming a slideshow must be used, how can it be implemented effectively without having the load time / overhead / confusion issues identified above?
It seems to me that the common issues are poor implementation / inappropriate use, not the slideshow / paginated concept itself.