Performance Issues
If SalesOS feels slow or unresponsive, follow these troubleshooting steps to identify and resolve the issue.Quick Checks
Before diving into detailed troubleshooting, try these quick fixes:Refresh the page
Press
Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac) to do a hard refresh that clears the page cache.Check your internet connection
Run a speed test at fast.com. SalesOS requires a stable connection with at least 5 Mbps download speed.
Slow Page Loading
Browser Cache
A full or corrupted browser cache can slow down page loading:- Open browser settings
- Go to Privacy or History
- Click Clear browsing data
- Select Cached images and files (not passwords or form data)
- Clear and reload SalesOS
Too Many Open Tabs
Each open tab consumes memory. If you have many tabs open:- Close tabs you are not actively using
- Keep SalesOS in a dedicated browser window
- Consider using a browser extension to suspend inactive tabs
Browser Extensions
Some extensions can interfere with SalesOS:- Ad blockers — May block API calls or resources
- Privacy extensions — May block cookies needed for authentication
- Heavy extensions — Extensions that monitor all page content slow down rendering
Pipeline View Performance
If the pipeline specifically is slow:Too many deal cards visible
Too many deal cards visible
A pipeline with hundreds of visible cards can be slow to render. Use filters to reduce the number of visible deals:
- Filter by owner (show only your deals)
- Filter by date range
- Filter by priority or tags
- Save the filtered view for quick access
Large custom field payloads
Large custom field payloads
Deals with many custom fields take longer to load. If your admin has added a large number of custom fields, consider whether all of them need to display on the card summary view.
Drag and drop lag
Drag and drop lag
If dragging cards between stages feels sluggish:
- Reduce the number of visible cards with filters
- Close other browser tabs to free up memory
- Use the card menu to change stages instead of drag and drop
Search Performance
If global search or filtering is slow:- Be specific — Use more specific search terms instead of single characters
- Use filters — Combine search with filters to narrow the dataset
- Wait for debounce — Search triggers after you stop typing for 300ms; do not press Enter repeatedly
Real-Time Updates
If chat messages, notifications, or pipeline updates are delayed:WebSocket Connection
SalesOS uses WebSocket connections for real-time features. If real-time updates are not working:- Check if your network or firewall blocks WebSocket connections
- Corporate proxies sometimes strip WebSocket upgrade headers
- VPNs can interfere with persistent connections
Notifications Delayed
If notifications arrive late:- Check that desktop notifications are enabled in your browser
- Verify your notification preferences in SalesOS settings
- Ensure you have not enabled Do Not Disturb mode
- Check if your browser is throttling background tabs (some browsers reduce activity for inactive tabs)
Data Export Slowness
Large exports can take time to prepare:- Exports with fewer than 1,000 records should be nearly instant
- Exports with 1,000-10,000 records may take 30 seconds to a few minutes
- Exports with 10,000+ records are processed in the background; you receive an email when ready
Device-Specific Issues
Low-End Devices
If you are on an older or low-powered device:- Close unnecessary applications and browser tabs
- Use the list view instead of the Kanban pipeline view (lighter rendering)
- Avoid having multiple SalesOS tabs open simultaneously
- Disable browser animations in accessibility settings
Mobile Devices
SalesOS on mobile may feel slower due to:- Smaller screens require more scrolling and navigation
- Mobile browsers have less memory available
- Cellular connections may have higher latency
When to Contact Support
If performance issues persist after trying the above solutions, contact support with:- Your browser name and version
- Your operating system
- Your approximate location (for network routing analysis)
- Which specific pages or actions are slow
- A screenshot of the browser developer console (Network tab) showing slow requests
- The approximate time when you experienced the issue

