Skip to main content

Why is the app slow and how can I speed it up?

Learn how to improve the performance of MCA Pilot.

V
Written by Victor Fteha
Updated today

We are actively working to make the MCA Pilot app faster. In the meantime, try these fixes in order — the first two solve most performance issues:

  1. Clear cache and hard reload — While on MCA Pilot, open Chrome DevTools (F12 or Ctrl + Shift + I), right-click the refresh button and select "Empty Cache and Hard Reload." Here's a video showing how. Or do a hard refresh: Ctrl + Shift + R (Windows) or Option + Command + R (Mac).

  2. Test in incognito mode — Open the app in an incognito/private browser window to rule out cache or extension conflicts. If it works there, your cache needs clearing (see step 1).

  3. Hide unused pages — Go to Settings > Visibility tab > Pages section and hide any pages you don't use. This reduces what the app loads on startup.

  4. Check your role and deal visibility — Reps see only their own deals; Managers see their team's deals; Admins see all deals. If deals are missing from the pipeline or other views, verify your role and deal assignments in How to Set Up a New User in Your Workspace.

  5. Reset pipeline view with 'Restore order' — If deals disappeared from the pipeline or columns are out of order, click the 'Restore order' button on the pipeline page to reset to defaults.

  6. Remove custom buttons — Custom action buttons can block the UI. If you can't open deals or other records, go to Settings, remove any recently added custom buttons, then reload.

  7. Close slow dialogs — If a confirmation window (Submit, Delete, etc.) loads more than 5 seconds, click the X to close it. The action will still complete in the background.

Most issues — slow pipeline, missing deals, button conflicts — resolve with a cache clear or hard refresh. Start there.

If you continue to encounter performance issues, please let us know what specific actions are being slow (e.g. loading a page, updating a record, creating a record, triggering an action button, etc.) so we can check it out.

Did this answer your question?