41–50 of 178 posts
What's baffling to me is how people love to spend seemingly infinite time playing with tech stacks and what not but then pay very little attention to basic details like what to load and how many resources do they really need.
My boring html-only pages load pretty fast.
Not just load time, but "time to read content" has exploded. Once the webapp has downloaded and it can start doing REST like requests for the actual content, it also needs to start loading pop-ups and the "continue reading"-button, that can hide the content after it is loaded. So once all that is done, the user needs to click away cookie consent banner, newsletter sign-up and the continue reading button. And only now…
The irony of this post is that the single heaviest resource loaded by this page is a 750kb image used only for the meta tags as a sharing image which most people consuming and downloading the page will never see. What's baffling to me is how people love to spend seemingly infinite time playing with tech stacks and what not but then pay very little attention to basic details like what to load and how many resources do…
Not just load time, but "time to read content" has exploded. Once the webapp has downloaded and it can start doing REST like requests for the actual content, it also needs to start loading pop-ups and the "continue reading"-button, that can hide the content after it is loaded. So once all that is done, the user needs to click away cookie consent banner, newsletter sign-up and the continue reading button. And only now…
What's the point of "continue reading"? Why not just show the full thing immediately?
Not just load time, but "time to read content" has exploded. Once the webapp has downloaded and it can start doing REST like requests for the actual content, it also needs to start loading pop-ups and the "continue reading"-button, that can hide the content after it is loaded. So once all that is done, the user needs to click away cookie consent banner, newsletter sign-up and the continue reading button. And only now…
What's the point of "continue reading"? Why not just show the full thing immediately?
Not just load time, but "time to read content" has exploded. Once the webapp has downloaded and it can start doing REST like requests for the actual content, it also needs to start loading pop-ups and the "continue reading"-button, that can hide the content after it is loaded. So once all that is done, the user needs to click away cookie consent banner, newsletter sign-up and the continue reading button. And only now…
this "felt" too much work so i thought of redesigning the workflow so we ended up with usernamepassword>
we made the entire process take time to accommodate the ~6 seconds of captcha which currently does not "feel" as taking that time because people are now not happy with loading and wait spinnners generally or stuff taking time, they want everything to be instant. this is just gaming the system so that we can work around technical limitations
We can wish that crappy websites didn’t get more bloated every year, but as long as they still load fast enough most people don’t know the difference or care. Everything has an opportunity cost, so once things are good enough the resources that could be spent optimizing will be spent elsewhere instead, and bloat that can be added to solve other business goals will be added. It’s understandable to get frustrated by th…
That would only be true if every one of your customers had fast, loss free, reliable internet 100% of the time they want to access a website. Even in a modern city this is rarely the case. So I'm afraid the real answer is that webdev is just not mature yet.