Hmm. There is a lot of difference between a sales brochure site, and a business to business site / app, with things in between. If you are running a marketing

Hmm. There is a lot of difference between a sales brochure site, and a business to business site / app, with things in between. If you are running a marketing or sales oriented site, you want to minimize friction. It sounds like you are doing more of a “captive user” app, similar to the government/healthcare oriented stuff I have been working on the last few years. In that case, you still want to tune things a bit, but you do have goals and criteria which might not match this article. Make sure things which can be cached are. (And don’t sweat the size of static assets too much, the second visit is just an HTTP header swap) Minimize the number of requests. Schedule requests for supplemental data in a component or form to load after the primary data. Minimize the size of dynamic data messages, though this can be hard when you work with devs who like very long names. Accept the fact that many of your web clients may have round trip latency well over 200 milliseconds, as well as the occasional multi second delay or request loss, and plan to work around that without hanging.