Replies: 5 comments 1 reply
-
I'm not experiencing that on Google Chrome, maybe the computer setup too, low memory, firewall, antivirus, and the browser itself |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
-
A year and a half later, and still it takes 5 seconds to load... The old feed had no such issue |
Beta Was this translation helpful? Give feedback.
-
am i the only one who feels this jumping mascot while loading is kinda annoying.. |
Beta Was this translation helpful? Give feedback.
-
I did a test on mine and it averaged 4 seconds loading time. I'm following 58 people, unsure on # of topics but it's probably similar. |
Beta Was this translation helpful? Give feedback.
-
It takes around three seconds on a fast university connection, if not longer, to load the front page feed.
The current feed design also suffers from this too - it's better at around a second and a half (still not good though). But this wasn't always the case! There was some sort of change around half a year ago (maybe longer?) that greatly bumped up the latency - before that, I hadn't ever seen the loading octocat.
Although I don't actually know anything about GitHub's web stack, I suspect a lot of this latency comes from rendering the feed client-side. GitLab - which relies heavily on client-side rendering - used to be borderline-unusable on my previous 5.3 mbit/sec connection. This article illustrates it, kinda: https://carter.sande.duodecima.technology/javascript-page-navigation/
Beta Was this translation helpful? Give feedback.
All reactions