6.0 B1 – Safari: Takes a verrrrrrry long time to switch between tabs

I’m on an M1 Pro machine with tons of ram, and switching between a component tab and a page tab in the new builder takes 20 seconds. See video. In this example, I had the page open, and then clicked the component tab, and immediately clicked back to the page.

Is that expected?

I’m developing locally using Desktop Server. Mac OS Ventura Public Beta on Safari 16.1.

Maybe it’s a side effect of developing locally?

I’m on a Mac using Ventura Beta and I don’t see this behaviour - when developing on a regular hosted site. FWIW.

Ok, good to know!

@devinelston, thanks for writing in! I haven’t seen this type of hangup personally. I just saw that you’re on a local environment so we can’t login to take a look around. Would you say that page you’re switching to is of a substantial size? I’ve built out some pretty monster test pages during this cycle using the new system with dozens and dozens of nested Components and standard Elements and of course, as pages get a bit longer the loading does take slightly more time, but I’ve never seen it take that long. Any other information you might be able to pass on could be helpful in diagnosing what could be going on there. Any custom plugins or scripting that could be blocking the load process?

Nothing too major. It’s a home page for a blog site, and has three sections pulling in posts just from their categories.

I’ll try it out on a staging server at some point and see if it’s just some local issue. If not, will get you login details at that point.

Sounds good, @devinelston!

Yeah, let’s disregard this feedback entirely. I just switched the site to Local by Flywheel, and it’s loading in about 7 seconds now. Still not terribly snappy, but way better than 20+.

BTW, what do you use to set up local development for yourself Kory?

@devinelston, thanks for letting us know and we will certainly keep an eye on this (as we always do in general with things like performance).

I use Local by Flywheel myself! I used to roll my own environment for years, but hey…if I can offload all of that stuff to someone else I will, haha. The great thing about Local is that you can quickly duplicate environments or spin up new fresh installs to test things out and then just destroy it when you need to. Certainly makes our development life much easier, but I think it is a great solution for general site-building / maintenance on a dev machine for sure.

Excellent, thanks @kory!

I suspected as much from seeing .local in the address bar in some of your videos. (If I’m remembering that right…)

No problem! And I’m sure it did at one point, haha…it has gone through so many iterations over the years. :slight_smile: