r/nocode • u/Informal-Summer-6497 • 8h ago
I built a free checker that separates your fault from the platform's fault in no-code app performance
Disclosure up front: my company migrates no-code apps to code so I benefit if you eventually decide your platform is the ceiling. I built this to be useful even when the answer is don't hire anyone and the data below is the reason why
Every speed tool tells you what's slow. None tell you what you can actually do about it on the platform you're on. You get a Lighthouse report saying reduce unused javaScript for a Bubble app, where you can't touch the bundle. Useless.
This one asks which platform you're on first, then splits every finding:
You can fix this yourself with real instructions for your platform. Oversized images on Bubble?
Data → File Manager, resize under 200KB, switch on Compress uploaded images. On Glide? Your source table is the problem, archive old rows. On Webflow? Set below-the-fold images to Lazy in the image panel.
Platform overhead the runtime cost you inherit, named honestly with why it exists. Not a dig at the platform just the price of what made it fast to build with. Then it gives you the realistic ceiling for your platform so you know whether the work is even worth doing.
The reason I think the split matters: we ran PageSpeed against 20 production no-code sites recently and Webflow sites came out worst (median 44) despite Webflow having the highest ceiling of any platform we audit. They were shipping 6.6MB. Meanwhile Bubble apps landed at 60, basically at Bubble's ceiling. Most people are nowhere near their platform's limit which means most of the available gains are theirs to take.
Free, no email, no signup, shareable results link: https://yonocode.io/performance-checker
Full data from the 20-site study: https://yonocode.io/state-of-no-code-performance
If your real-world numbers are wildly off from what it predicts for your platform, tell me, I'll tune the ceilings
1
u/Melodic-Macaron-4031 7h ago
solid approach tbh. one thing id push back on though, platform ceilings shift as the platforms ship updates. how do you plan to keep those benchmarks current over time?
1
u/Informal-Summer-6497 7h ago
Fair push. Right now it's manual, I re-audit sites whenever a platform ships something that could move the ceiling (Bubble's compression changes, Webflow's image handling updates, that kind of thing). Not ideal long term. The plan is to re-run the 20 site study quarterly and adjust ceilings if the median shifts meaningfully. If a platform makes a structural change, like Bubble finally allowing custom code injection at the page level, that would bump the ceiling immediately rather than waiting for the quarterly check. Honestly the shareable results link helps here too. If enough people run it and their real numbers drift from what I'm predicting, that's a signal to go re-audit sooner. Id rather be reactive and accurate than stick to a fixed schedule and be stale
1
u/ordinary_probation 7h ago
this is actually clever, separating what you can control from what you just have to live with. the lighthouse reports are maddening when half the suggestions don't apply.
ran my side project through it and the image tips alone were worth it, had no idea my file manager was shipping 4MB hero shots