> no reduction in total work This does not 100% track with observed client-side performance. Another poster mentioned caching, which obviously reduces total wo

> no reduction in total work This does not 100% track with observed client-side performance. Another poster mentioned caching, which obviously reduces total work. I would also add shifting the work via pre-computation as another commonplace way to improve performance. > It takes less code to build a string in a datacenter than it does in a browser? The string build in a datacenter might be happening in a warmed-up JIT of some language, on a machine with enough capacity to do this effectively. By contrast, the browser is possibly the slowest CPU under the most outside constraints (throttling due to power, low RAM, multitasking, etc.). It is generally going to be better to do the work in the datacenter if possible.