I never produced content, so I hope I do nothing “wrong here”. I just wanted to show you my work on secondra.com trying the last days to speed up the whole thing. Thanks to all the great girls & guys making bubble such a great venture, by the way! See the speedtests in attached files, in comparison to amazon.com / aribnb.com and secondra.com (bubble app), with a great result for not having millions for network routing.
Bubble is fast, as it helps as we know to reduce development time & cost.
Apps on Bubble are very fast in execution, if something is done around the apps to tune this in.
But lets start with the meta-idea, the ideas of Google and the web.
1. Google´s sick idea how web apps should look like today
Google has its own idea of how a web app should look like. I say “look” because they think, as they are super sucessful, that people “like” what they “design” or how they work, live and tell us an app should look like. Some think it is a post-communistic approach / a so called “Material Design”. Which is a joke. And if someone does it in another way, so well: I can be a superb funded enterprise, or you get…a BAD LIGHTHOUSE TEST, which ends up in bad rankings, and a very aweful feeling as a coder / bubbler and thinking:"…well maybe it was a bad idea to take bubble.io to create apps, because it is not a coding language as Ruby or React or other, and this must be worse than these best of breed frameworks or programming languages…:"
Which is not true. In no way at all.
Now let´s talk about what I did.
- Steps towards super speed and 95 Score in Google Lighthouse Test
I started with a Score of 5 (percent) two weeks ago. Even the app was not so slow, it was like I was trapped. So I started
setting up a PWA:
this was not so easy, as I thought, but in the end worked out to let the service worker work, and doing the important caching and more on my app. I did just configure it (some trys and errors, haha, until it worked…). The manifest still does not work, but as far as I see, has no influences on speed, more on other topics as behaviour on the mobile devices.
intensely change the configuration of showing groups & objects, rg on load entire / above fold, and then test hundreds (or thousands) time the effort for the page speed. Here I took the tool GT Metrix, and reduced results on just “Stop on load” as this is more the realistic usere centirc speed “impression” - as pages load and load even after user can work with it for some time… . Repeating groups I did defer in load, once with hiding, but then when users enters working, I said the rg should begin with scrolling >1 - ideally hiding it beneath fold of page. This speeds up a lot.
still not enough, I wanted a more crispy feeling on load, so I went on network things, to cloudflare, set up an account, echanged the name server adresses on my google domain account (where I have my web address bought). Then some hours again of config and always retesting the efforts on speed, leveraged web caching for my app on cloudflare´s network. And upgraded the plan there, but I am not sure it is necessary, they have also a free quite impressive plan, but I was so excited I just wanted more!
then went back to reconfigure & test again on the app, exchanged the first service worker, testing, and now the desktop app is really fast I think.
- Bubble is fast. Speed takes time & testing and some technical mirage.
- Bubble has no disadvantages in no way for me to any other option, but has a lot of advantages.
- Finally, even when speed is superb: the economic success is not guaranteed at all. People do not love a company for the fast app they have. They love ot for the spirit, the speed of adapting to market needs (which is bubble´s super strength) And sorry for my typing errors…;))
See Google Lighthouse with a normal / average page in my app (landing is of course slower, as I have 20 popups and dozens ogf other things plus a repeating group with products loading), but doesnt matter, - its fast!
Mobile secondra.com Lighthouse test: