Hi all,
Occasionally I've checked in on progress of the BaNano project.
It's a cool and innovative idea, and is certainly a framework I've considered using.
The thing that has continued to hold me back though, is load times, especially the initial load of the site.
I was doing some testing on the kitchen sink site here:
https://magenta-vacherin-2f7e6b.netlify.app
I have what I consider a reasonable internet connection.
Speedtest indicates 214.37mbps download speed.
I'm testing on my PC with the following:
Windows 11
Chrome Browser
PC has Ryzen 5 3600 with 16GB RAM and is generally fast.
Your milage may vary, but for me over multiple tests, the typical initial load time for the site is around 13 seconds.
On a single occasion it loaded in 9 seconds, but on a number of occasions it would take 17 seconds.
If you look at online articles, such as this one, it estimates that 67% percent of users will abandon a website that takes 12 seconds to load:
https://www.websitebuilderexpert.com/building-websites/website-load-time-statistics/
I was searching on the forum, but couldn't find much discussion on this.
The closest I could get was this:
https://www.b4x.com/android/forum/t...proving-perceived-performance-on-7-29.137742/
However that is simply showing how the wait animation can be implemented.
So my question is, would a typical website be as slow to load as the demo site?
Do any strategies exist (beyond a wait animation) that would reduce the load times?
Obviously I could create a separate static website that would load quickly, with the interactive 'application' taking much longer.
This would definitely help to an extent.
I don't want to be too negative, I think this is a very interesting concept, and I appreciate a lot of work as gone into it.
I'd appreciate any thoughts or ideas that anyone might have on this.
However, if I'm honest, I still think that most users won't be happy with load times of 13+ seconds.
Occasionally I've checked in on progress of the BaNano project.
It's a cool and innovative idea, and is certainly a framework I've considered using.
The thing that has continued to hold me back though, is load times, especially the initial load of the site.
I was doing some testing on the kitchen sink site here:
https://magenta-vacherin-2f7e6b.netlify.app
I have what I consider a reasonable internet connection.
Speedtest indicates 214.37mbps download speed.
I'm testing on my PC with the following:
Windows 11
Chrome Browser
PC has Ryzen 5 3600 with 16GB RAM and is generally fast.
Your milage may vary, but for me over multiple tests, the typical initial load time for the site is around 13 seconds.
On a single occasion it loaded in 9 seconds, but on a number of occasions it would take 17 seconds.
If you look at online articles, such as this one, it estimates that 67% percent of users will abandon a website that takes 12 seconds to load:
https://www.websitebuilderexpert.com/building-websites/website-load-time-statistics/
I was searching on the forum, but couldn't find much discussion on this.
The closest I could get was this:
https://www.b4x.com/android/forum/t...proving-perceived-performance-on-7-29.137742/
However that is simply showing how the wait animation can be implemented.
So my question is, would a typical website be as slow to load as the demo site?
Do any strategies exist (beyond a wait animation) that would reduce the load times?
Obviously I could create a separate static website that would load quickly, with the interactive 'application' taking much longer.
This would definitely help to an extent.
I don't want to be too negative, I think this is a very interesting concept, and I appreciate a lot of work as gone into it.
I'd appreciate any thoughts or ideas that anyone might have on this.
However, if I'm honest, I still think that most users won't be happy with load times of 13+ seconds.