basement
community
search
wall of shame
joined some time ago
joined some time ago
content has been deleted
posted 5/14/2023, 6:18 pm
joined feb 22, 2023
Do not induce vomiting if swallowed.
joined feb 22, 2023
I'd say no more than the number of times the user has to click on your website; I don't like when weird shit happens when I didn't tell it to.
posted 5/15/2023, 2:30 am
joined some time ago
joined some time ago
content has been deleted
posted 5/15/2023, 11:02 am
joined feb 22, 2023
Do not induce vomiting if swallowed.
joined feb 22, 2023
quoting sebastian:
What about for Analytics or loading fonts?
I don't want analytics being taken without me expressly allowing it, and fonts should really just be up to the user.
posted 5/15/2023, 3:55 pm
i think this ultimately depends how expensive your API requests and/or queries are, but I think the ultimate goal should be to keep page load times under 1 second, if possible.
some things are definitely going to take a long time for sure - i think your UX can account for that if, for example, you're making a bunch of bulk API requests to do something. Something like adding a "this may take a minute..." message might alleviate people clicking away.
But yeah i'd say you should be aiming for full interact-ability in about 1 second. that's the benchmark i try to strive for.
posted 5/20/2023, 6:12 am