I just have got to ask, shot in the dark here > Is there any way I can try to incorporate a pre-loader element, either Wix or custom made, for ANY PAGE (or the entire site) that actually RENDERS near-instantly on my Wix site while the rest of the code loads? I saw how to make it for individual elements…
I think I know the answer, but figured this cannot hurt. My current load time on mobile devices be it on 4G or wifi is about 10 seconds for a completely blank Wix page. I just need something there to show the user we are loading stuff and it takes that much time, so they do not abandon. 10 seconds is a long time. And its just a blank white page there. If I could put ANYTHING there that would show up and actually render right away and faster than the rest of Wix code and elements, it would really be awesome. But I kind of know the answer is just a no right now.
Hi Omid,
First of all - keep in mind that since were still in alpha, the performance you’re observing is FAR from what you should expect from the released version. We’re in the process of finalizing a big performance push which should be going into production soon and we expect to dramatically improve things. We’ll announce it in the announcement forum when it happens.
As for showing things as quickly as possible in the render cycle - You’re right in that you can’t put a page/site-wide pre-loader that shows before everything loads. If, after our performance improvements, you still feel this is necessary, feel free to add a feature request.
But… when you’re writing your own WixCode with JavaScript, it sometimes depends on what you’re doing on page load. I’m not sure this is relevant to your question, but let me put it out there just in case:
Before onReady() (code which simply isn’t in the onReady or any event handlers)
This is where you should be doing anything that doesn’t depend on components in the page (e.g. going out to some external service and getting data). This actually happens in parallel with the page render, so it’s triggered very early in the cycle and where relevant is a great tool to get things running quickly.
In theonReady() event
This is where you can start working with the components on your page, and is triggered right before the page content shows. It’s a great place to fill data, show/hide components and such. For example - you could have a preloader showing by default when the page loads, and hide it in the onReady event. btw, you have control over final showing of the page - you can return a Promise in the onReady event handler, which will prevent showing of the page until it’s resolved (although this somewhat opposite to what you’re trying to achieve, just including for completeness).
I really do hope you guys can deliver an acceptable render time (I will truly be happy within anything less than 5 seconds personally and can fully defend it as a reseller). We are at your mercy on that front. So all I can do is hope and pray it happens sooner than later. I’d love to see dramatic changes, but honestly I will be fine with anything even acceptable and just average (< 5s render) at this point as you can imagine!
When I signed up for Alpha, I asked about this very thing and was told performance will not be degraded or at least it is not expected to. Not sure if that was accurate info. Not sure if Alpha has caused this or this is just general changes in Wix editor/code that affect all sites or something else entirely. But I can assure you compared to 3-4 months ago, all of my Wix sites on this particular account load much slower in a consistent manner now. Hopefully, it’s related to Alpha and yall’s performance push will bring it to a swift and sweet end. I trust you guys fully understand and feel the urgency of this particular topic and that you will deliver a one two punch on it soon to address the known issues.
The technical information you provided will come in handy soon. I fully appreciate it Uval.
Hi Omid,
We do indeed feel the urgency. I hope this will be addressed really soon. We’re putting the final touches on the performance fixes and hope to bring them into production very soon.
Just to clarify a bit:
Performance of sites with no WixCode in them should not be affected at all by the alpha.
But… We expect the performance improvements we’re working on to improve site performance across the board for a wide range of sites including those which don’t include WixCode features. So, cautiously optimistic that all your sites will be performing much better soon.
What I am reading is this and please correct me if I am wrong:
Wix IS working on performance improvement for all sites regardless of alpha/wixcode involvement.
Wix Alpha in specific is suffering, well, from certain performance issues like any other alpha software that are also going to be resolved sooner than later in their own right aside from general performance improvements that Wix is working on.
I just hope after doing this performance fix, we no longer have to deal with 10 seconds of a white screen on a mobile device before Wix banners and a mobile menu on a blank wix site end up rendering… That part right there is what really concerns me. It is the last remaining big shortcoming at Wix that has persisted for as many years as Wix has been around. Don’t get me wrong, things have improved a bit on speed/performance over the years, but they are just not where they are supposed to be in 2017, just far from it. So unless this performance fix can speed up render time on mobile by at least 2-3 times, it is not going to make me much happier about Wix performance (alpha or not), and I do speak as a Wix pro and a Wix Ambassador, so I am a fan. I know this may sound snotty and demanding, but it is not. I just have used Wix for long enough to feel comfortable bluntly and honestly speaking to the team behind it as a user who wants to see you all and the platform fully reach profitability and success in a sustained and long term manner. I am also quite frankly super tired of slow load issues and the “fixes” provided in KB when there clearly is something else (200 server calls and then some) that take 10 seconds before any of my own work and optimization can even start mattering (before render begins)…
I want to emphasize, the 10 second of mobile whiteness number is from a totally blank wix site. …
This SSR roll out and whatever other secret sauce you guys got cooking better be good lol
OK so one year later, how can I get internal preloader for my pages, because speed is truly not that improved from many of my anecdotal observations and reports of my users. I got the preloader in place right now, one for full site preloader on headers that is supposed to work on every page but only does it on initial landing. Then I wanted to get a regular internal preloader for my pages and it seems I have to add this preloader manually to every single page. From what I have been able to figure out, there is no way to make a prelaoder work on every page transition. Can you please confirm this? I even made it appear on all pages and it still only works on first view.
Omid, there is a tread on this very forum called, from memory “true preloader” (but I am never able to find even my own posts back, so don´t hold me up on it). It´s a preloader that is inserted into the head-tag thru that rather new possibility of adding custom code into head and body. I use it and it works on every page, also mobile. If you cannot find it, let me know, I´ll repost.
Giri, I already have that. I need a secondary. My internal page transitions are taking too dang long. And that metatag business does not kick in regardless of how I want it to between internal page changes after that first landing. I actually am on that post you refer to myself. see my site, and try clicking on some buttons, with any luck of normalcy of your equipment and not being located at wix offices/network, you will most likely have to wait 2-3 seconds for anything on the page to change at all to “register” with you the user that a click was made to an internal page and its happening… none… resulting in more clicks by users which adds to the lag even more… so i need an INSTANT INTERNAL PRELOADER which I can always code in where this is critical on my conversion buttons to show that and then load that new page. I cannot use a lightbox as lightboxes are very laggy themselves and do not render rightaway anyway. so I am trying to see if there are any particular means available as a workaround to make this a bit more tolerable for the users.
Tal, I am familiar with that video as well and it does not address further INTERNAL page transitions at all from what I can tell. unless I have made a mistake in my code and am not getting the results I should. But from multiple checks I have done, I have the correct code. the ALL PAGES option run once, is the problem more for me. I have set the Add Code to Pages to be ALL PAGES - LOAD CODE ON EACH NEW PAGE.But I am getting the same results as ALL PAGES LOAD CODE ONCE. It only happens on first initial visit of the user and any further internal page changes do not get a preloader at all.
www.symmetracreative.com you can see for yourself. Would love to find a way to make it kick in inbetween internal page changes too.
Did you ever solve this? I too am running into the same issues. We’re close to 1500 members and I am afraid we will have to take our services to a new platform if we can’t get the speed up. Missing out on hundreds of new members daily… A preloader would significantly help, so that members at least know that something is happening and hopefully won’t be as frustrated.
@founder22854 Are you referring to the loading time for the Members Area of your site? It will be helpful if you can provide more information, including your site URL. Thanks.
)