3 ms·

I only count 67 MB, with cache disabled an no add-ons.

• ebg13 7y ago
  Same for me if I don't do anything on the page. But then if I actually scroll the page it gets exuberant. I think it's loading the same assets many times in parallel and possibly repeatedly. Also, "only", lol. Look at this hilarious bucket of shit: https://i.imgur.com/36CBn5y.png https://i.imgur.com/36CBn5y.png And that's in Chrome! Firefox actually handles this page's bullshit gracefully, by saying "NO! FUCK OFF, WEBPAGE!" ("Will-change memory consumption is too high. Budget limit is the document surface area multiplied by 3 (730032 px). Occurrences of will-change over the budget will be ignored.")
  • Stratoscope 7y ago
    In all fairness, you probably have the "disable cache" box checked in your developer tools. If you turn that off, the multiple duplicate requests in the network tab go away. Presumably the duplicates get served from cache. Of course it would be better if they didn't make duplicate requests in the first place!
    • nimos 7y ago
      Yeah it works out OK with caching. Very easy to track down with the new initiator tab on the in Chrome Dev Tools. They have _initLightBoxItems which removes all the images/gifs from the dom and then readds them which is bound to the scroll event (with a 50ms throttle).
• bathtub365 7y ago
  67MB is big for a webpage.