Hi everyone,
I’m curious to hear what small changes you’ve made to your Bubble apps that actually improved performance.
Sometimes it’s not a major redesign that’s needed, but little things like optimizing database searches, reducing unnecessary workflows, or loading data only when it’s needed.
For those who’ve worked on apps that started getting slower as they grew, what made the biggest difference for you? I’d love to hear about real-world experiences, especially tips that aren’t immediately obvious to beginners.
Well, when I started building with Bubble over 3 years ago, some of my workflows would go on forever because I wanted to cover every conditional I could think of.
I’ve since learned that idea is worthless.
I now do workflows that are several steps less than what I thought was needed…
Even if it meant dividing a workflow into 2 workflows sometimes and still cutting out a ton of steps.
Workflows don’t have to be complicated.
I found the easier you make them the better.
One small change worth checking is the data source behind each repeating-group row. A list can look simple while each cell starts another search for a count, status, or related record.
I’d start with one slow screen and check three things:
- Can an advanced
:filtered condition become a constraint on the original search?
- Is a nested search in each row actually needed, or can the row use an existing related Thing?
- If the UI only needs a total, can the expression return
:count rather than load the full list?
Then compare the same screen with the same data before and after each change. Page speed and workload aren’t always the same issue, so I’d measure both rather than judge by workflow step count alone.
Bubble’s search optimization guide has useful examples: Searches | Bubble Docs
Where do you notice the slowdown most: initial page load, searching/filtering, or saving changes?
So, the question was about what changes you made to your Bubble site to make it faster.
Since your site isn’t built on Bubble, I think that’s probably an interesting question to hear you answer without using OpenAI.
Preloading images via page header. Making images webp format
@boston85719 Do tell!.. please
Thanks for the detailed breakdown! I hadn’t really thought about how nested searches inside repeating groups could add up as the number of records grows. Comparing performance before and after each change seems like a much better approach than assuming fewer workflow steps automatically means a faster app.
Good point! Images can definitely affect how quickly a page feels ready to use, especially when there are several large ones loading at once. Using optimized formats like WebP and avoiding unnecessary image loading seems like a simple place to start.
One thing that made a huge difference on a couple apps I worked on was switching static dropdown data from database lookups to option sets. Sounds small but when you have repeating groups loading and each row is doing a search just to populate a status label or category name it adds up fast.
Also privacy rules. Most people think of them as just security but they actually reduce the amount of data the client downloads. If you set them up properly the browser only gets the fields it actually needs instead of pulling entire records.
And honestly just splitting pages. I inherited an app once that had basically everything on one page with tons of conditionals hiding and showing groups. Moved the main sections onto their own pages and load time dropped noticeably because Bubble wasn’t trying to evaluate all those conditions on every page load.