I have encountered this issue as well.
Particularly on seeing ‘waiting on pubnub’ stuck on the cue on the loader which cause browser to crash on multiple instances.
I Shared this with the developers.
To better resolve this I performed the following.
1. Create a new browser profile instance in chrome.
- Go to chrome://settings/
- Manage Other People
- Click on Add Person
- Give it a name like ‘My Name - Webflow Only’
Note: For this chrome instance, do not ‘log in to chrome’ nor ‘sync chrome user’ in chrome settings. Your browser might ask you to, but don’t.
Note 2: Only use this browser instance only to log into webflow. Do not log into anything else.
2. Open new browser profile instance in a new window / system process.
- On your upper right corner of your chrome window, you should see your chrome instance Avatar/User dropdown button. Click on it to expose your Chrome user profiles.
- Now click on theprofile you just created such as ‘My Name - Webflow Only’ to open a brand spankin new chrome instance with fresh cookies.
- Do not sync your browser to log into gmail (or anything else) for that matter in this browser profile (yet).
Note: this is similar to incognito mode, the main difference is that incognito mode inherits some of the privacy and cache settings of your main browser instance of which the incognito mode was opened from.
3. Disable services and auto clear cache and temp files in new browser profile. - DO NOT perform on your regular browser profile
- On your NEW chrome profile instance, go to chrome://settings/
- Select ‘Advanced ▼’ to expose advanced settings, and scroll down to ‘Privacy and security’ section.
- Disable ‘Use a web service to help resolve navigation errors’ - this is enabled by default
- Disable ‘Use a prediction service to help complete searches and URLs typed in the address bar’
- Disable ‘Use a prediction service to load pages more quickly’
- Disable ‘Protect you and your device from dangerous sites’
- Disable ‘Automatically send usage statistics and crash reports to Google’
note: disabling these services is NOT recommended for normal browser instances.
- Auto Clear cache on exit:
- click on ‘Content Settings ►’ then click on ‘Cookies ►’
- Choose ‘Keep local data until I quit my browser’
4. Export HTML/CSS/JS/ASSETS into zip and then delete deprecated content and clean up css.
- Skim your html / css … exported files on your PC. Usually you’ll find things you should delete right away.
- In your css file, you might notice lots of duplicate classes such as ‘div 1’ ‘div 2’ ‘div 4’, that have identical attributes. This is ually an easy clean up by retagging div 2/3/4 as div 1 in your designer project, then deleting div 2/3/4.
- also delete deprecated CMS labels from CMS collections
- delete deprecated assets/pictures from assets panel
- delete deprecated fonts from your settings > fonts menu
- if you make any oppsies in designer mode you can revert back into an achieved instance and/or refer to your exported assets html+css for easy rebuiding
5. Compare Designer Performance to new Profile performance.
Use your regular browser for normal activities and to verify how your page is rendering.
Use new webflow only profile to log into webflow, when your normal browser is giving you issues with page load in designer.