Hello Bubble Community,
I recently started promoting my application and I’m a little bit shocked at the amount of WU consumed on page load for the index page. For context, its an event promotion platform that loads today’s events on the index page when visiting the site (with the option to switch dates/locations/event types). I had 187 new visitors to the site yesterday and apparently 7200 WUs were dedicated to page loading. I’ve added a screen shot of my repeating group’s data source logic for reference. Is this normal? Any tips on how to optimize the page load in order to get the WU down?
Hi there,
Without any other context, 38WU per visitor for page loading alone seems high. Cash you give a sense for how many records are getting found/ displayed with this search? And what are those conditions doing?
Conditions are around hiding the repeating group if there are no events present and re-sizing if the screen gets to a certain size.
I believe I set it up that there are only 30ish records being returned based on having around 30 events a day…but im not positive that is what is happening. I’ll have to figure out how to determine if I’m returning all the events.
Some other context that might help that I’ve seen in my research:
-I’m not setting a certain state on page load
-I’m ignoring empty constraints, only because when I do not ignore them I get no events (based on one video I saw…that means that I’m getting this data twice?)
Is there any other information I can provide that might give you a better idea of what is going on?
How many total page loads are you getting, across all visitors?
Yesterday it appears I had 158 page views for the index page
Can you share a link, or screenshot how elements are shown on the page? Are you possibly displaying each event’s thing’s thing, or some deep searching within the items displayed in the repeating group? Is there anything else in the page?
This is the only repeating group on the page, with the filters up top used to change what is populated in it. Each event item has a company associated to it which is its own associated record, and an event type which is its own associated record.
With a search setup like that your RG is going to load everything that isn’t blocked by a privacy rule.
Then each time a value in any of your dropdowns and datepicker changes, it will do another search.
