@mitchgillin We already have that issue in our top priority. For now you can try the following things:

• Use collapsible UI for filters, only render when required or interacted by user.
• Use small sizes for filter queries

Would it not be more efficient if ReactiveSearch sent one search request to ES, compiled from the needs of all components, and then each component subscribes to the result and pulls out "their" data? Or do you have a use case where you'll update a filter widget without updating the main search result or the opposite?

@janhoy This is how ReactiveSearch works, it generates a combined query (via msearch, multi search) for all the components that would be affected by a given interaction. Except during the initialization phase, where ReactiveSearch fires independent queries for each component instead of combining them together. The above issue is specific to this scenario - there is room for improvement here.