3 ms·
The site doesn't need to be non-interactive, just load the data you intend to show right away in the initial request. Have your 10 interactive components pre-fi
by ehnto 7y ago
The site doesn't need to be non-interactive, just load the data you intend to show right away in the initial request. Have your 10 interactive components pre-filled, then they can update via web request after that. Single interactions are fine, but when the page initially loads and has to then load 10 other components, the latency adds up really fast and makes it all feel clunky. It still matters after the initial load, just not as much.
An example, when loading a Jira ticket, you have to wait for the page to be sent to you, but it's not usable yet, then you wait for the individual areas of the page all to be sent to you, and as each one loads in at a different time the page goes all over the place and it's not clear when it's actually done and you can safely click stuff without your click target jumping away.
After that, interacting with a single part of the Jira ticket can still induce a load, but it's just the one, and it's expected and I can tell when it's done.