Large CMS performance because of 100 record limit

I have a hobby website with wine tasting notes, which I recently ported from Drupal 7 to Webflow ( - in Dutch, sorry). My readers like to filter for tasting notes for specific wines or wines from a specific region etc. So apart from Webflow Search (which does not allow a lot of customisation, unless you can prove me wrong?), I’ve created a tasting notes filter page (Proefnotas) which allows you to filter e.g. for all tasting notes concerning wines from the Pauillac appellation in Bordeaux (Proefnotas), or wines from that same appellation from one year, e.g. 1982 (Proefnotas).

To achieve this, I’ve used the otherwise outstanding Finsweet Attributes. But… It’s useability is limited by the fact that the Webflow CMS only returns 100 records at a time, and currently I’m at 7200+ records… Attributes being JS, it can only function if all records are loaded in the front end, which takes far too long. Go ahead and click one of the URLs above and you’ll know what I mean - you can track progress with the counters on top of the result list?

So is there really no way to interact directly with the Webflow CMS and perform queries like the ones above? Or should I consider an alternative to Attributes? Or not use the CMS and integrate with another backend database (if so, what would be your suggestion?).

If the CMS only returns 100 records at a time, why does Webflow offer 10,000 records in its CMS? I only encountered this performance issue after paying for a Business subscription, so I feel a bit cheated.

Last minute addition: I just read the CMS announcement of earlier this month (Scaling the Webflow CMS to new heights | Webflow Blog) but that does not cover my problems…

Thanks & kind regards --Mike

No code way there is no other solution, but you can always create a gateway server that fetches data from the Webflow CMS applies the filterings you need and give you back the html or the json data you need to render content

Thanks, but not very realistic for a hobby project…

Cheers --Mike

7200+ items doesn’t seams to me a so little project. In any way another simpler way would be to use attributes but load data from external. And basically dump your whole database into a json file, you can set up automations to do that automatically, but you would still need custom coding