If you want to keep FILTER and SORT available (which you probably do), there is only one possible solution:
Load the entire page DATA, but render PAGES with only some results (for example 100-500). It's not the "loading" that is slow anyway, but the "rendering" of 13.000 items onto a single page. With PAGES, we can still use FILTER and SORT, because it will re-render pages on filter and sort action. The point of PAGES is to limit the amount of items rendered on screen, which in your case is the underlying problem.
You can see an example of how pagination works here:
https://codepen.io/javve/full/neQKbe
As you can see, filter (and sort) will affect all items, including those not displaying, and pages will update themselves. The main thing I don't like about PAGES, is that the page-button need to display at the bottom of screen, below all items. It's not optimal for the user, and I don't want to start adding page buttons at top AND bottom of screen, and also having to add some "page 1 / 3" information ... It's clumsy and unintuitive.