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?
It’s two fold:
-
it’s good proof of “user interaction with site” to sell to advertisers
-
they can use that to load more ads or refresh current ones after it loads more text, and you’re already bought in on the story so you’re likely going to keep going.
I suspect a third reason is to try adding other news stories at the end in case the current one didn’t grab your attention, but that doesn’t seem to be as consistent amongst sites that I’ve seen do this. I run ad blockers though, so I don’t really see the sites the way they expect me to.
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
Nowadays, this is a mute point.
*moot
Moop.
Moot point!
Moo point
Thanks for the laugh, guys! :D I’ll leave it as is
Moot 😊
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.
The only use case where this makes sense is where news are behind a paywall
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?
-
Enshittification
Because fuck you, that’s why.
Then you click it, and it’s like 2 sentences and the rest is ads. Might be one of the reasons.
Just a guess: to prevent bots from scraping the full content?
Doubt it. My web analytics indicate that bots click on every single element on the page, whether it makes sense or not.
For this reason it’s a good idea not to allow your site to generate any kind of circular self-referential loop that can be achieved via navigation or clicking on things, because poorly coded bots will not realize that they’re driving themselves around in circles and proceed to bombard your server with zillions of requests per second for the same thing over and over again.
Likewise, if you have any user initiated action that can generate an arbitrary result set like for example adding an item or set of items to a quote or cart, it is imperative that you set an upperbound limit on the length of result or request size (server side!), and ideally configure your server to temp-ban a client who attempts too many requests that are too large in too short of a time span. Because if you don’t, bad bots absolutely will eventually attempt to e.g. create a shopping cart with 99999999999999999 items in it. Or a search query with 4.7 gigabytes worth of keywords. Or whatever. Either because they’re coded by morons or worse, because they’re coded by someone who wants to see if they can break your site by doing stuff like that.
it’s a good idea not to allow your site to generate any kind of circular self-referential loop that can be achieved via navigation or clicking on things
Don’t nearly all sites have a logo at the top that will take you back to the homepage? I’m not really following.
My intuition is that the only safe solution is to rate limit requests; a poorly coded bot could definitely just be a while loop for the same URL ad infinitum.
[e] Unless there’s something to this I’m not thinking about.
Apparently it can boosts engagement?
At the Times, which got 60 percent of its June visitors from mobile, the “show full article button” has resulted in “moderate increase” in the time readers spend, according to Paul Werdel, senior product manager on mobile.
Quartz, which also introduced its own “read full story” button alongside its design refresh in June, has used the button to boost the performance of its mobile Engage ads, which appear directly below the button. The Huffington Post uses a similar approach, presenting readers with a 300 x 250 banner ad below its own “read more” button. Huffington Post VP of Engineering Sam Napolitano said that preliminary data on the feature has been “very positive” since its addition.
Because they want you to obnoxiously see as many ads as possible because they don’t care if you read the article, only view ads. This is the new shitty web. MSN, Newsweek and Yahoo are the scummy kings.
- Some people prefer pages to scrolling (it’s amazing the strength of opinion about this for either point of view)
- Advertisements are charged per impression. So each page counts as a new impression
- Be grateful websites no longer auto scroll web pages
- Some things lend themselves to page by page. For example very long articles (this is why books replaced scrolls)
- Be grateful that websites stopped animating page turns etc
- Sometimes web developers don’t care and just use a bought in package
it’s amazing the strength of opinion about this for either point of view
Regardless of user preference, on the web it’s a fool’s errand to try to force your content into a page-by-page format. Designing a paged content presentation that’s guaranteed to work on every device with every screen size is so close to impossible that it’s not worth bothering. And that’s before you take into account whether or not the user prefers to view in landscape or portrait, what aspect ratio their screen has, what zoom level their browser is set to, or even how their browser implements zoom and content rescaling. So 9 times out of 10, you’ll wind up with your content being broken into pages that the user still has to scroll around in to see all of anyway. Or where everything will be illegibly microscopic. Or both! Especially if they turn up on a mobile device – which is something like 92% of all web users these days. Every time you fail you will annoy the shit out of your user base, and you will fail more often than you succeed.
No, the sole driving factor behind sites breaking articles into “pages” is so they can load more ads on each page change.
(This does not apply to non-website mediums, obviously. IDGAF how you digest your e-books, manga, or whatever.)
There we go, a strong opinion.
Maybe to make the article seem shorter, so you’re more inclined to keep reading. Once you’re halfway through, you’re more likely to want to read the rest. Both halves are probably filled with ads, so the longer you stick around, the better.
while data collection and advertisement is a big part of it, they probavly try to “save” on bandwidth, you might not read the entire article.
deleted by creator
wow. not a web developer myself, but that would’ve been the only justification for this besides farming engagement for advertisers.
deleted by creator
deleted by creator
