The "reimagined" site Reports section is an unmitigated disaster that starts bombing when reaching significant number of transactions. I am guessing the reason is the awful HTML generated for the tables, for example a single transaction from the old site is 248 chars:
Why do we care? Well this was a single line/item from the table - one download or purchase. The "payoff" comes when there are thousands of transactions and the browser will need 3005/248 = ~12 times the memory. Particularly offensive are the unused `data-reactid` attributes, there are 40 of them per txn, each setting a distinct name string. The problems start when a developer has big number of app installs, then browser tab RAM usage explodes and the tab will likely crash.
Can the web developer that produced this ReactJS-ive sludge - kindly descend here to explain the need for it? I am sure with shared efforts we can trim down the lard off this memory hog, it's in our common interest!
PS. To compare RAM used, i just did this experiment - pulled my July month in the "classic" reports in Chrome, checked memory in its task manager - 118MB. Then did the same in the "reimagined" reports, it is slow... wait for it... slow... wait for it... loaded. 685 MB!