I can actually see that the log in portion is working quickly. It’s the next page where things are taking forever to load. I have some ideas now actually thinking about it, but I won’t be able to check it until Thursday when I’m back in my office.
I have a lot of RGs loading at once in this big one-page app. Each of these groups is using the Search&Autocorrect plug in for “search on the fly” type of searching. That function works great BTW. However…
If I start with any of these RGs already hidden on page load, then Search&Autocorrect does not work/load. The group that uses S&A needs to be visible on page load. I think it’s a bug that S&A must be visible on page load in order for it to work. Once loaded the RGs can be hidden and revealed again and S&A works fine after that.
So what I have done currently is use workflows on Page Load that simply hide each of these many RGs while covering them with a loading screen. Once the entire page is loaded the loading screen is hidden and off we go.
In this way however ALL of my entire app’s RGs and data that use S&A load their respective data slowing the whole thing down. If I didn’t need to use S&A in all of these groups then I could just start the main page will all of these RGs hidden and therefore none of them would load their data until they are made visible later when the user needs them, if I’m not mistaken.
So if there is no fix for S&A so that it can be hidden on page load and still work, I’ll need to figure out another way to do similar searches that does not utilize that plug in, or delete that functionality so I can have all of these many RGs hidden from the start to speed up the user experience.
As always, thoughts and opinions are welcomed.