Most of the time is spent rendering the page. Maybe, but it's the client spending that time, not the server. It's largely a separate issue from what it is bein

Most of the time is spent rendering the page. Maybe, but it's the client spending that time, not the server. It's largely a separate issue from what it is being discussed here. Save the most user-time per engineering hour you can. If your server can handle 100 requests a second and you know you're soon going to be receiving 1000 requests per second, it makes more sense to address that with HTTP caching than twiddle with your javascript includes. A browser can't render a page that the server is too overloaded to send.