Page weight may matter, but I think amortized page weight matters most. It&#x27;s like the marshmallow experiment for the web. If you can make one request at 10x the size, but it&#x27;s only made 1&#x2F;100th as often (presumably spans multiple pages) then as long as people come back enough to justify that initial extra cost, you&#x27;ve effectively decreased to 1&#x2F;10th again.<p>That&#x27;s why I think AJAX, web manifest [1], indexedDB, localStorage, etc. need to be leveraged much more. Imagine most of your app loading without making a single request, except for the latest front page JSON, or the latest . You have a bunch already in indexedDB so you just ask the server &quot;hey, what&#x27;s new after ID X or timestamp T?&quot;<p>So your two minutes just became a couple milliseconds (or whatever your disk latency happens to be), and the data loads shortly thereafter, assuming there&#x27;s not much new data to send back. And if you don&#x27;t need any new resources, you only had to make a single request.<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;w3c&#x2F;manifest" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;w3c&#x2F;manifest</a>