Similar psychology:
When an action takes longer than about a second, you could show a short message saying it's still working, so people wait rather than panic clicking elsewhere.

Try loading the text and key details before heavy images, so people on slow connections can still choose something without waiting for high-resolution previews.

One option is to load a few results, then fetch more as soon as someone swipes to the second, so the next ones are ready before they reach them.

For long setup or sync tasks, consider a progress bar plus a note that it's safe to go do something else, so people know they needn't watch it finish.

On long loading screens, it may help to show a riddle for people to think about, so a wait well beyond the Doherty Threshold feels less boring.

Responses slower than the Doherty Threshold can make people doubt anything is happening, which might increase churn as some give up and leave mid-wait.
Responding within about 400 milliseconds, or giving people something to read during longer waits, could help keep their attention from drifting.
Acknowledging every tap straight away could reduce frustration, as people see their action registered and don't tap again or wonder if it's frozen.
An interface that keeps pace with users, within the Doherty Threshold, may feel smoother and more enjoyable to use than one that leaves them waiting.