Anthony Skinner Yes, this is exactly what is happening with us. The thing is, we need to be able to load hundreds of rows or even thousands for an entire year of sales history (we do this for creating reports in external tools - and even at that we have to literally copy/paste the entire HTML table manually from the rendered page to a spreadsheet because TSA hasn't implemented CSV export on all the pages). If yours is as slow as your video shows imagine how slow loading 1200 rows is, or 10000.

Typically in web apps, you should be able to perform queries up to tens of thousands of records before performance starts getting a little sluggish. I suspect this is a problem with how the queries are coded. If they are using a framework it might be the N+1 problem, where an ORM allows queries to be written in more human-readable fashion, but also allows for too many queries to be performed. It takes a good bit of thought and planning to avoid this problem.