Some article websites (I’m looking at msn.com right now, as an example) show the first page or so of article content and then have a “Continue Reading” button, which you must click to see the rest of the article. This seems so ridiculous, from a UX perspective–I know how to scroll down to continue reading, so why hide the text and make me click a button, then have me scroll? Why has this become a fairly common practice?
deleted by creator
Nah that’s not it. The text content is an infinitesimal portion of a modern Web page.
Many webpages are > 1mb, that’s a million letters if you will.
Articles usually have images and possibly embedded videos. So it’s not just text.
Even so, a decent webserver wouldn’t really care.
Maybe it loads faster for mobile users though if you only load text and a single image at first.
I’m not sure what you’re getting at.
The comment I replied to said that maybe the “read more” button is an effort to conserve bandwidth by only sending half the text.
I said that the text is such a tiny portion of the bandwidth required to transmit a web page that it wouldn’t make sense to try conserving it by only sending half.
You’re absolutely correct in that only sending images on the visible part of the page is a common way to conserve bandwidth.
You’ve got that the wrong way. It’s <1mb. Just read the less than symbol out loud.
No, many web pages are larger than 1mb.
Oh yeah I misunderstood what they were saying my bad
The cost of making a new request for the rest of the news is higher than just returning the full news. The only use case where this makes sense is where news are behind a paywall and you just want to show a teaser to Anonymous readers.
It can be particularly good in soft-paywall situations, where you want to give people a certain number of clicks per month before they have to start paying.
I don’t think I’ve ever actually seen these “keep reading” buttons used in that way, though.
You mean you can save a couple of kilobytes after having loaded 2MB of java script libraries and trackers?