Pagination

Right now performance is fine but not great. Depending on the computer, initial load and clearing all filters is noticeably slow, taking about 250ms-400ms in my own testing. I've tracked this down to DOM repaint performance; we have a _lot_ of nodes on the page, so we should try to reduce that count.

I'm currently favoring pagination to limit the number of results we show at once. It tends to be more accessible than infinite scrolls and is easier to implement and maintain. A count of about `30` records per page seems good to me, but an open question I have is if we should have the ability to allow users to adjust this?

Start by tracing the result rendering and filter-clearing entry points responsible for the initial load and repaint cost. Evaluate pagination at about 30 records per page, including whether users should adjust the page size. Done means fewer DOM nodes are rendered at once, pagination remains accessible, and initial loading and clearing filters improve.

Written by the indexing model from the issue text.