Bubble optimization - Understanding how run.js works

Hey Bubble community,

I’m seeking advice on optimizing the initial page load in Bubble.io. I’ve identified run.js as a potential bottleneck. Can anyone provide insights into how run.js functions and how to improve its loading performance?

bump.

hey @desarrollo2, is this a consistent result? have you tried measuring a few times?

Yes, I’ve measured it several times and it always comes out the same with different tools.

we just checked on our end and run.js downloaded in 700ms… this could potentially be depended on your connection and other local factors.

Could you use dev-tools to show your response headers for that file?
specifically Server: and Content-Encoding: , . It should be cloudflare and gzip respectively


Does loading plugin libraries or executing workflows affect this file?

I asked internally and it seems like they are just too many moving parts to really pinpoint the issue. Recommendation is to reach out to the support team and they can dig into this more

1 Like

Run.js shows up as problematic in my performance profiler

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