Filtering speed and efficiency is a bit of a rabbit hole, but one that’s worth going down. In addition to a lot of great discussion on the forum, I highly recommend this book The Ultimate Guide to Bubble Performance - the new edition is out (now 210 pages!) - Tips - Bubble Forum
From your description I can’t exactly make out how you’ve set up your RGs, but here are some general guidelines I follow that make things work faster for the user and minimize the Bubble capacity I’m using. Not sure if this translates 100% to whatever page score metrics thought.
- Keep the filtering server side (which it looks like you’ve done)
- Use a scrolling RG so that Bubble is only pulling a few records at a time
- Keep datatypes lightweight
- Set up the user interface so that the user selects filter options and then hits “search”, then that kicks off a workflow to set custom states which the RG filter refers to. This limits the number searches and retrievals you are asking Bubble to do.
There are also scenarios where if the total amount of data isn’t that huge, and the user is going to do a lot of filtering and fiddling with the data, it could make sense to bring all the data client side and then filter client side with “:filter”. But I’ve avoided that because it’s not scalable.