Comment by wackget
2 days ago
Honestly the site[1] is very basic and pretty damn slow. When I click into a different category there is a noticeable delay of 1-2 seconds before the new page loads. I don't want to replicate this in any of my own projects.
Just checked, and it's pretty snappy... under Firefox... on 10-year old hardware... that was originally a Chromebook.
Have you tried visiting the site on a worse machine?
I don't know, there's an annoying (constant) delay when you click on anything.
Did they consult with Atlassian to build this?
I wanted to write, 'They have to load the entire catalogue for a category, including all the images. What did you expect?' However, having looked into it a bit more, it seems that they didn't particularly care about optimising load times.
That's what this type of SPA architecture leads to unfortunately. Routers should immediately display the navigated to route with place holder content / skeletons, but instead all the frameworks basically wait for all the data to load before transitioning. You can technically stream the data in but even a single awaited promise will block the navigation until it succeeds. And it's not an issue that shows up in dev because typically the data loading is instant.
Nope. Skeletons are the worst. Down with the necromancy!
They try to create a _perception_ of a quick answer while adding overhead and distracting people.
Skeletons are a loading state. Get rid of skeletons and you either have unresponsiveness or flashes of nothingness
8 replies →
It's not a perception if partial load shows some information faster than waiting for the full load
It far and away beats the alternative which is clicking on a link and nothing happening. Feedback should be within a frame or two of latency, not seconds...
2 replies →