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?

  • jaschen@lemmynsfw.com
    link
    fedilink
    English
    arrow-up
    0
    ·
    8 months ago

    Web Manager here. Some good answers here. Let me add a few more.

    Engagement. If you land on a page and don’t engage on the page and leave, Google doesn’t even count you as a User. The more things you do on the page, Google will rank you higher.

    Data analysts: we are testing if the article is valuable or not. If nobody is clicking continue, we know that we might need to rework the article.

    Page load: The biggest and I mean biggest reason someone leaves a page is page load speed. If you’re deep in researching some information, regardless of your internet speed or if the fault is on the user side and your page load is over 3 seconds, you will leave the site. Loading only 1/4 of the page helps with this along with other tricks like caching at the CDN and lazy loading.

    There are tons more reasons, but we found that with the “Continue” button, it wasn’t detrimental to the site performance.

    • dual_sport_dork 🐧🗡️@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      8 months ago

      regardless of your internet speed or if the fault is on the user side and your page load is over 3 seconds, you will leave the site

      As both a developer and an end user, this drives me batshit.

      Seemingly no one has figured out that if users are bouncing due to page load times, maybe the problem is actually because your page that was supposed to be, say, a recipe for a bologna sandwich doesn’t need to first load an embedded autoplaying video, an external jQuery library, a cookie notice, three time delayed popovers, an embedded tweet, and a sidebar that dynamically loads 20 irrelevant articles, and a 2600x4800 100vw headline image that will scroll up at half speed before the user can even get any of the content into the viewport. Just a thought. I don’t care what your dog-eared copy of Engagement For Dummies says. It is actually wrong.

      I have made the business I work for quite successful online by taking all of the alleged “best practices” things that clearly annoy the shit out of everyone, and then just not doing those things.