Roku Billing Transaction Page Down

I'm able to get to it.

It's periodically very slow for me, but loads eventually. In fact, the developer portal, in general, is painfully slow overall.

Do not use the "new site" report https://developer.roku.com/transactions
Instead use the "old site" report https://owner.roku.com/Developer/Transactions

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:

"https wrote:
<tr>
<td>12/01/15</td>
<td>17684638</td>
<td>Sale</td>
<td>1A7F3110-6F96-4E99-A402-A56001169350</td>
<td>Agario - beta</td>
<td></td>
<td></td>
<td>$0.00</td>
<td>CAD</td>
<td>&nbsp;</td>
<td></td>
<td>&nbsp;</td>
<td></td>
<td></td>
<td class="t-last"></td>
</tr>

The very same transaction blows up to 3005 characters due to ver-bogosity:

"https wrote:
<div class="transactions row bg" data-reactid=".5.5:0.1:0">
<div class="col-md-4 col-sm-6 col-xs-12 col" data-reactid=".5.5:0.1:0.0">
<span class="transaction-label" data-reactid=".5.5:0.1:0.0.0">Channel Name</span>
<span class="transaction-text" data-reactid=".5.5:0.1:0.0.1">Agario - beta</span>
</div>
<div class="col-md-8 col-sm-6 col-xs-12 col" data-reactid=".5.5:0.1:0.1">
<span class="transaction-label" data-reactid=".5.5:0.1:0.1.0">Transaction ID</span>
<span class="transaction-text" data-reactid=".5.5:0.1:0.1.1">1A7F3110-6F96-4E99-A402-A56001169350</span>
</div>
<div class="col-md-4 col-sm-4 col-xs-12 col" data-reactid=".5.5:0.1:0.2">
<span class="transaction-label" data-reactid=".5.5:0.1:0.2.0">Roku Account</span>
<span class="transaction-text" data-reactid=".5.5:0.1:0.2.1">17684638</span>
</div>
<div class="col-md-4 col-sm-4 col-xs-12 col" data-reactid=".5.5:0.1:0.3">
<span class="transaction-label" data-reactid=".5.5:0.1:0.3.0">Transaction Type</span>
<span class="transaction-text" data-reactid=".5.5:0.1:0.3.1">Sale</span>
</div>
<div class="col-md-4 col-sm-4 col-xs-12 col" data-reactid=".5.5:0.1:0.4">
<span class="transaction-label" data-reactid=".5.5:0.1:0.4.0">Amount</span>
<span class="transaction-text" data-reactid=".5.5:0.1:0.4.1">
<span data-reactid=".5.5:0.1:0.4.1.0">$ 0.00</span>
<span data-reactid=".5.5:0.1:0.4.1.1"> </span>
<span data-reactid=".5.5:0.1:0.4.1.2">CAD</span>
</span>
</div>
<div class="col-md-4 col-sm-4 col-xs-12 col" data-reactid=".5.5:0.1:0.5">
<span class="transaction-label" data-reactid=".5.5:0.1:0.5.0">Product ID</span>
<span class="transaction-text" data-reactid=".5.5:0.1:0.5.1"></span>
</div>
<div class="col-md-4 col-sm-4 col-xs-12 col" data-reactid=".5.5:0.1:0.6">
<span class="transaction-label" data-reactid=".5.5:0.1:0.6.0">Expiration Date</span>
<span class="transaction-text" data-reactid=".5.5:0.1:0.6.1"></span>
</div>
<div class="col-md-4 col-sm-4 col-xs-12 col" data-reactid=".5.5:0.1:0.7">
<span class="transaction-label" data-reactid=".5.5:0.1:0.7.0">Partner Reference ID</span>
<span class="transaction-text" data-reactid=".5.5:0.1:0.7.1"></span>
</div>
<div class="col-md-4 col-sm-4 col-xs-12 col" data-reactid=".5.5:0.1:0.8">
<span class="transaction-label" data-reactid=".5.5:0.1:0.8.0">Original Transaction ID</span>
<span class="transaction-text" data-reactid=".5.5:0.1:0.8.1"></span>
</div>
<div class="col-md-4 col-sm-4 col-xs-12 col" data-reactid=".5.5:0.1:0.9">
<span class="transaction-label" data-reactid=".5.5:0.1:0.9.0">Original Purchase Date</span>
<span class="transaction-text" data-reactid=".5.5:0.1:0.9.1"></span>
</div>
<div class="col-md-4 col-sm-4 col-xs-12 col" data-reactid=".5.5:0.1:0.a">
<span class="transaction-label" data-reactid=".5.5:0.1:0.a.0">Reason</span>
<span class="transaction-text" data-reactid=".5.5:0.1:0.a.1"></span>
</div>
<div class="col-md-12" data-reactid=".5.5:0.1:0.b">
<span class="transaction-label" data-reactid=".5.5:0.1:0.b.0">Comments</span>
<span class="transaction-text" data-reactid=".5.5:0.1:0.b.1"></span>
</div>
</div>

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!