Identifying Slow Searches in Bubble Using Dev Tools

gabriel.guerin · 2024-11-26T15:54:03.087Z

Hi everyone,

I’m trying to figure out why our Bubble app is slow. I’m using Edge as my browser and checking the network tab in the developer tools. I read AirDev’s best practices guide, which suggests looking at the request payload to find a search path that might show the source of slow searches.

However, my request payload looks different and seems encrypted. Is there another way to find the original source of a search using the network tab in the developer tools? I want to link it back to the Bubble editor because our admin dashboard is slow and has many elements.

Any help on how to do this would be appreciated. Thank you!

image3807×662 102 KB

rico.trevisan · 2024-11-26T16:05:35.668Z

I think those are Elastic Search searches, they are always like this. I think. Is it binary data?

Maybe open the network tab, filter for Fetch/XHR, and domain:*.bubble.io (or your own domain) to see the individuals searches that are happening. I’ve uncovered a few issues in my apps where I had an RG – one search – and then one search for each item inside that RG.

georgecollier · 2024-11-26T16:12:01.111Z

rico.trevisan:

I think those are Elastic Search searches, they are always like this. I think. Is it binary data?

No, it’s just an encoded API call.

gabriel.guerin:

request payload to find a search path that might show the source of slow searches.

You’re looking at the request payload - you need to look at the response payload (the data we’re getting back from Bubble).

gabriel.guerin · 2024-11-26T17:36:14.882Z

Hey @georgecollier, thanks for your quick reply.

I already checked the response payload in the network tab of the developer tools. It tells me which data type I’m looking at, but it doesn’t give me the path. From the Airdev screenshot below (taken from the link I posted), they look at the request payload, not the response payload. They have something called search_path.

image1920×429 31.2 KB

I’m wondering if this search_path doesn’t exist anymore and if it’s impossible to find. The reason I’m doing this is that our app has three heavy search requests that slow down page loading. All these searches are on a data type called Session. I’ve tried updating some searches on this session data type, but nothing has changed.

Is there any method to achieve what I’m looking for?

system · 2025-02-04T15:54:11.299Z

This topic was automatically closed after 70 days. New replies are no longer allowed.