No Stupid Questions
No such thing. Ask away!
!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules (interactive)
Rule 1- All posts must be legitimate questions. All post titles must include a question.
All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.
Rule 2- Your question subject cannot be illegal or NSFW material.
Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding META posts and joke questions.
Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.
On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.
If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.
Rule 7- You can't intentionally annoy, mock, or harass other members.
If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.
Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- Majority of bots aren't allowed to participate here.
Credits
Our breathtaking icon was bestowed upon us by @Cevilia!
The greatest banner of all time: by @TheOneWithTheHair!
view the rest of the comments
As a person who knows nothing about web development, can you not load the pages in smaller chunks, so that the first screen or two worth of stuff loads fast and the rest could load while you are looking at it. That way, to the user, it appears to load quickly enough to keep them from leaving?
It’s a bullshit excuse - a couple pages of text loads in a second or two in even poor connections. Their optimizing for ads and tracking
Let me correct my other comment here: I miss when a 9600 baud modem was fast but holy crap has the internet gone downhill. Now get off my lawn
You can, but you would have to do it through scripting which would rely on whatever methodology you're using not breaking with browser updates and standards changes, whether or not the user has scripting enabled to begin with, whether not their adblockers or other plugins mess it up, etc. And then you can wind up just deferring the issue. Let's say the user intends to quickly skim through your page to see if it actually appears to contain what they're looking for or whether it's just SEO bullshit, so they scroll down right after the first chunk loads and hit the point where the next chunk should load, and unexpectedly find that it didn't do so instantly (because it probably won't) and it appears your content cut off mid-page. They'll assume your site is just broken and you've never seen another user hit that back button so fast.
So the answer is "yes, but," and may not be worth the trouble.
Clicking a "continue reading" button is not an ideal solution either, but at least the user will (should) realize that they've performed an action that will load more content, as opposed to having it happen behind their backs in a manner that they weren't initially aware.
Yeah this shit annoys the hell out of me with certain websites where I'm trying to ctrl-f information. It hasn't loaded the whole page until I scroll down, so my search ends up being worthless.
You lose backwards compatibility with web browsers if you do that.
It also doesn't help reader apps or plugins, SEO or various other things to have the site stream the text instead of just loading it.
Basically it moves you from standard thing everything understands to non-standard thing which might break. It's just not worth it.
What you're talking about is called lazy loading. It loads text first and CSS and then images after.
Most modern sites now do this along with needing to load it at all until you hit the continue button. That not only reduces your browser load, it also reduces server load as well.
There are many other reasons to have the continue button, but the positives outweigh the negative. It's not considered a dark pattern and helps the content team improve on their content.