I would say it depends on the current experience. For instance, if you have a slow site, make it faster but don't go into nanoseconds. If it's still slow afterwards, try faking speed (queue actions, improve render chain, caching etc). There were some studies that actually showed that loading just some resources and giving the user the "it's loading" message would actually have them question their connection/phone and not blame the slow experience on the website. Not good, but still better than having them blame it on you because then you lost them. However if the UX is still not good enough, you can go into milliseconds and really make it fast. That said, I'm positive that with the evolution of tools and languages + add some good affordable providers that offer fast CDN and easily configurable HTTP/2 features (Netlify for instance) most of the hard work will be taken away fromthe developers and making your site fast should not be something we'll have to focus on in the future because that's just the way they'll be made :)
No comments yet.