Link to my PageSpeed Insights report: https://pagespeed.web.dev/analysis/https-wefwef-app/n8mwvqotop?form_factor=mobile
As always you mfers invaded the PageSpeed screenshots with beans
Out of the loop, what’s with beans and why is it as usually? Lol
The front page recently had a post get 6000+ points which was something like “I heard Lemmy will upvote anything so here’s a can of fucking beans” with a picture of Heinz canned beans. Since then, there have been lots of bean memes and parody posts of the original bean post.
That’s hilarious. I remember seeing that original one with beans and pretty sure I swiped to hide it, haven’t seen any of the follow on memes, I think I managed to filter 196 😁
Someone posted yesterday about how lemmy users would upvote anything with a can of beans as an example. The can of bean made the top page with 5k+ upvotes, and now it’s an inside joke
As a web dev myself, I wanted to add to that that Google’s Page Speed insights are sometimes a little misleading or at least have to be interpreted and taken with a grain of salt. Sure, a site / web app might be marked as slow because certain thresholds aren’t met, without the user even noticing that the app is “slow”.
As an example, apps which load in lots of third party content. As a user, you would expect them to have this slight delay when opening and will be fine with it without perceiving it as slow.
It’s really more important for marketing websites because google will rank your page worse when it perceives the page as slow.
Oh, so the results aren’t meant for web apps like Wefwef. Speaking of Google’s ranking, so does it mean when Wefwef needs monetization/ads in the future, the PageSpeed results will impact Wefwef’s ability to promote itself or be monetized, if Google AdSense considers user experience when deciding ad revenue?
Late reply, but this is the exact reason why products as Wefwef usually do have dedicated and optimised marketing websites :)
Maybe the benchmark punishes heavy CPU load, something at the bottom says Moto G, which might be a phone released in 2013.
i think it’s an inherent limitation of pagespeed, since wefwef is not serving 1st-party content. the first contentfull load will be after the backend wefwef queries responds, which in this case took several seconds. there’s nothing the client can do about that, except for changing backends
