How To Find the Root Cause of Performance Issues

1. Overview

Performance issues may have any number of underlying causes. These may be at the level of the entire LeadSquared application or a specific feature or service. When reporting an issue, it’s important to be clear on whether the issue is the result of genuine slowness, or the result of an error.
This article will help you understand the different types of performance issues you may encounter and the best way to troubleshoot each of them.

Note: Before attempting to diagnose or troubleshoot any issue, first check our status page for ongoing issues.


2. Network Issues

First, try and identify if the issue is user-specific or occurring for every user.

Ask Your Colleagues 

  • Are other sites being affected or just LeadSquared?
  • Is your entire team experiencing slowness?
  • Is the issue occurring for users on different connections? For example, if you’re using a wired connection, is the issues occurring for users on Wi-Fi as well?
  • If you have employees in other offices or working remotely, are they also experiencing the same level of performance?

If you answered ‘No’ to the questions above, you’re likely to be facing a network issue and not a LeadSquared specific problem. Many user-specific issues can be resolved by troubleshooting your internet connection, network and browser.


2.1 Troubleshooting Network & Browser Issues

  1. Ensure that your internet connection is working fine
    1. Open other websites/applications on your browser. Are other sites slow as well or is it just LeadSquared?
    2. Perform a speed test on your internet connection. Go to to check the ping, download and upload speed of your connection
  2. Check your browser
    1. Can you reproduce the issue on another web browser?
      1. LeadSquared works best with Google Chrome and Mozilla Firefox. We recommend downloading these browsers and updating them regularly.
    2. Clear your cache and cookies. This is not only a key troubleshooting tip; it may also resolve your issue altogether. Browsers retain a lot of information to help save your preferences and load faster. Due to constant updates to LeadSquared, your browser may try to load older versions of the application. This may result in slowness and other problems. Here’s how you can clear your cache and cookies –
      1. Google Chrome
      2. Mozilla Firefox
      3. Internet Explorer
      4. Safari
    3. Certain browser extensions, add-ons, and plug-ins may cause issues while rendering pages in LeadSquared. One such plug-in is “Dark Mode Extension” which causes issues with LeadSquared.
      Try to avoid such plug-ins and/or try private browsing mode and see if the issue persists.
      If disabling all extensions worked (private browsing), try adding the extensions back one by one. Once you’ve identified the extension causing the issue, report it to us at”.
  3. Check your network and firewall configurations
    1. It’s possible that your firewall may be blocking certain LeadSquared services. Check to see if you have any network ports that are locked down.
    2. Check if any network ports are blocked.
    3. Do you have anti-virus software installed? Temporarily disable your anti-virus and see if the issue persists.
    4. Do you have another network available? Check to see if you can reproduce the issue on the other network.
  4. Flush DNS
    The DNS cache stores the IP address of each website you visit. This helps your browser find addresses quickly, enabling faster connections. However, there are good reasons to flush your DNS, such as protecting your browsing history and helping resolve certain errors. This may solve the issue you’re currently facing in LeadSquared

    1. On Windows
      1. Press the Windows key and R to open the command line.
      2. On the Run window, type CMD and press Enter.
      3. Right click on Command Prompt and click Run as administrator.
      4. In the console, type the following command: ipconfig /flushdns
      5. If the command was successful, you will see the message “Successfully flushed the DNS Resolver Cache”.
    2. On Mac, the commands to flush DNS differ depending on the version you’re running. First open Terminal, then enter the command corresponding to your OS version
      1. OS X 12 (Sierra) and later
        macbook$ sudo killall -HUP mDNSResponder;sudo killall mDNSResponderHelper;sudo dscacheutil -flushcache
      2. OS X 11 (El Capitan) and OS X 12 (Sierra)
        macbook$ sudo killall -HUP mDNSResponder
      3. OS X 10.10 (Yosemite) | Versions 10.10.4+
        macbook$ sudo dscacheutil -flushcache;sudo killall -HUP mDNSResponder
      4. OS X 10.10 (Yosemite) | Versions 10.10.1, 10.10.2, 10.10.3
        macbook$ sudo discoveryutil udnsflushcaches
      5. OS X 10.9 (Mavericks)
        macbook$ dscacheutil -flushcache; sudo killall -HUP mDNSResponder
      6. OS X 10.7 (Lion) and 10.8 (Mountain Lion)
        macbook$ sudo killall -HUP mDNSResponder
      7. OS X 10.5 (Leopard) and 10.6 (Snow Leopard)
        macbook$ dscacheutil -flushcache
      8. OS X 10.4 (Tiger)
        macbook$ lookupd -flushcache
    3. On Linux,
      1. Most current Linux distributions do not use a DNS resolver cache in the same way that Windows and Mac OS X use. To confirm which particular daemon is installed for your Linux distribution, check the website or its forum pages.


2.2 Generating a Traceroute for Troubleshooting

When troubleshooting slowness, our support team may need additional information about the path your browser takes to get to your LeadSquared instance ( You need to generate a traceroute to your LeadSquared instance, as well as to to help us analyze the performance issue.


  1. Press the Windows key and R to open the command line.
  2. On the Run window, type CMD and press Enter.
  3. In the Dos window, type “tracert <subdomain>”, then press Enter.
  4. Copy the results of the traceroute.
  5. Repeat the steps with “tracert”, then press Enter.
  6. Copy the results of the traceroute.
  7. Email us ( the results of both traceroutes labeled appropriately.


  1. Open the Network Utility app (you can search for it using Spotlight).
  2. Click the Traceroute
  3. Type “https://<subdomain>”, then click Trace.
  4. Copy the results of the traceroute.
  5. Repeat the steps for “”.
  6. Copy the results of the traceroute.
  7. Email us ( the results of both traceroutes labeled appropriately.


2.3 Unresolved Issues

  • If the issue is still unresolved and can’t be reproduced on other machines, contact your IT team and reference this article.
  • If the issue is specific to one machine, it is most likely caused by a group policy setting, antivirus, or other software interfering with LeadSquared.
  • If the issue still persists, please feel free to reach out to us at Let us know what browsers you’ve tried, which users are experiencing the problem, detailed replication steps, and screenshots (if any).


3. Errors on the LeadSquared Platform

You may receive certain errors while using LeadSquared. These shouldn’t be confused with slowness issues. Here are some examples of errors –

Area ErrorPossible Cause
Entire PlatformError Processing Your RequestDatabase issues on our side
500 Oops!
APIs504Database issues on our side
500Code Issues
429API Rate Limits. Check our API Rate Limits article to learn about your plan and steps to manage rate limits.


3.1 Troubleshooting Errors

  1. Wait for a few minutes and then re-try. Our database may be facing heavy loads. If you wait and try again your request may get processed successfully.
  2. If you’re still receiving an error, contact us at and report the specific error(s) you’re receiving.


4. Slowness on the LeadSquared Platform

If you’ve followed all the steps above and are confident that the issue is not caused due to a problem on your side, use this guide to determine the best course of action for each issue.

  1. Is everything slow, or is it just one LeadSquared page (e.g., dashboard, manage leads, manage activities, etc.) that is experiencing issues?
  2. Is there a specific action that you’re unable to take? (For example, search is taking too long, page filters are not loading, bulk updates are not working, etc.)

Use the categories below to narrow down the issue –

4.1 Overall Platform Slowness

Pages such as Manage Leads, Manage Activities, Manage Tasks, Smart Views, Lead Details, etc. are slow.

  1. Navigation from one page to another is slow.
  2. Create, update and delete operations on leads, activities, tasks, etc. are slow.


Contact us at

Console Information 

  1. Mention the issue type as ‘Pages Not Loading’ and include the name of the page(s)
  2. Let us know which browsers you’ve tried, which users are experiencing the problem, detailed replication steps, and any screenshots (if any).
  3. You can give us more details on the issue by sharing a screenshot of any console errors.
    1. On your browser, right-click on the page that is slow, then click Inspect. (Alternatively, you can enter Ctrl+Shift+I).
    2. Now navigate to the Console tab and take a screenshot. This will help us identify the element(s) that may be causing the issue.

console errors

Capture .har file

  1. On your browser, right-click on the page that is slow, then click Inspect. (Alternatively, you can enter Ctrl+Shift+I).
  2. Select the Network tab, then enable the Preserve log checkbox.
  3. The small red circle in the top-left of the console indicates that it is recording. If the circle is black, click on it to begin recording.
  4. Navigate the scenario or reproduce the issue. You will observe that data is being collected.
  5. Click the red circle to stop recording after the error is observed.
  6. Right-click in the list of entries loaded and select Save as HAR with Content to download the .har output file.

Note: Please select the Network Issue Troubleshooting icon on the top right corner under Sources to avoid a pause message or debugger tool message.


4.2 Automation

4.2.1 Trigger Delay

Sometimes the automation trigger may take time to fire. In these cases, leads may not immediately enter your automation based on the triggered action (new lead, lead update, activity update, etc.).

Database issues on our side.


  1. Check if a bulk trigger is used in the automation. For example, if you have enabled the trigger on import option and import 25000 leads, it might take longer to trigger the automation for all 25000 leads. Please check the request history page to ensure that the import action is successful. 
  2. If you’re still receiving an error, contact us at
    1. Report the issue as ‘Automation Trigger Delay’
    2. Provide details of the automation (name, link), sample leads and support access to your account.


4.2.2 Card to Card Delay

Leads in your automation may be taking time to move from one card to another.

Delays due to queuing, database issues, automation not set up optimally, etc.


  1. Automations use a staggered re-try logic where the re-try takes place every 5 minutes up to 3 times. If you wait about 20-30 minutes, the lead may enter your automation successfully.
  2. Ensure the automation is set up optimally. One major reason for card to card slowness is too many If/Else evaluation cards stacked one below the other. A great feature to help you address this issue and optimize your automation is the Multi If/Else condition.
  3. If the issue still persists after you’ve optimized the automation, contact us at, report the issue as ‘Automation Card to Card Delay’ and provide the automation name.


4.2.3 Delay in Wait Condition

The wait condition may sometimes execute with a delay. For example, you may have set a wait condition for 5 mins, but the wait card may execute after 10 mins, causing a delay in the automation chain. 

Delays due to queueing, database issues, etc.

Contact us at, report the issue as ‘Delay in Wait Condition’ and provide the automation name.


4.2.4 CRON Delay

The CRON job may sometimes execute after the configured scheduled time. 

Delays due to queueing, database issues, etc.

Contact us at, report the issue as ‘CRON Delay’ and provide the automation name.


4.3 Bulk Actions

You may face slowness while performing the following bulk actions –

  1. Import
  2. Export
  3. Update
  4. Delete

Your bulk action request gets queued and then executed by LeadSquared. When large numbers of records are involved, this may take some time.


  1. Each request you make gets queued. Avoid making multiple requests for the same actions.
  2. Navigate to the Request History page and check the status of the bulk update operation. Refresh the page to see the latest, updated status.
  3. Bulk delete requests are processed overnight, so you can only expect to see the refreshed data the next morning.
  4. If you still haven’t received your data, contact us at and report the issue with –
    1. Details of import/export action + screenshots.
    2. Support access to your account.


4.4 Email Campaigns

You may face one of the following slowness issues with emails campaigns –

  1. Bulk emails (emails sent to a large number of leads)
  2. Scheduled emails
  3. Tracking


  1. If you send a large number of emails, they may take time to get delivered to all recipients.
  2. Scheduled emails may also sometimes get delayed due to database issues.
  3. LeadSquared tracks email opens, clicks and other metrics in the Email Campaign Report. This data may sometimes take time to reflect in the report.

Contact us at and report the exact email campaign issue. Be sure to provide the email campaign name and support access to your account.


4.5 Connectors and Telephony

Apps and connectors in the Apps Marketplace help integrate your LeadSquared account with other third-party services like SMS, cloud telephony, social media services, etc. These connectors may be slow for a number of reasons.

Many of our connectors use third-party APIs and web services. In these cases, a delay may be caused due to issues with third-party services.

Contact us at, report the issue as ‘Connector Slowness’ with

  1. Details of the connector (name of the connector/connector Id).
  2. Sample leads and screenshots.
  3. Support access to your account.


4.6 Rules, Webhooks, and Lapps

4.6.1 Rules Delays

Rules may execute with a delay after the triggering event.

Delays due to queueing, database issues, etc.


  1. Contact us at, report the issue as Rules delay and provide the rule name.
  2. We suggest moving from rules to the newer and more powerful – Automation feature, to avoid issues of this type.


4.6.2 Webhook Delays

Webhook execution may be delayed at times.

Delays due to queueing, database issues, etc.

Contact us at, report the issue as ‘Webhook Delay’.


4.6.3 Lapps Delay

Lapps may have code issues that cause delays and slowness.

Delays due to queueing, database issues, etc.


  1. Check Lapps logs.
  2. Contact us at, report the issue as Lapps delay and provide the Lapps details.


Any Questions?

Did you find this article helpful? Please let us know any feedback you may have in the comments section below. We’d love to hear from you and help you out!

Was this Helpful?

Notify of
Inline Feedbacks
View all comments