Failed script pops or slow script pops can be hard to diagnose. Using this guide you can narrow down the cause and easily prevent this problem.
Possible Issues and Troubleshooting Measures:
Be sure the computer meets our minimal specifications.
|Third party script||
If you are using a third party script it may not be responding in a timely manner. Try the script manually, be sure to time it. Try it over a wide span of time keeping track of the results.
Make sure the browser is up to date and is operating correctly. Check the chrome task manager as the incident happens.
Contact your Internal support team for additional diagnostics. If this issue continues, please contact SingleComm.
Additional Info for Support Teams:
To further diagnose issues with slow scripts you can open Chrome Developer Tools and look at the Network tab where you can find additional information about load times of various page elements such as the example circled in red below.
The example below depicts:
- A problem with embeds at 2.47 seconds. Around 1.2 seconds embed Xhr requests would be a more normal range.
- An 11.57 script load time on that particular computer, at that particular time.
- (Continue testing against multiple computers, and outside the network to reduce the variables. If the problem persists please reach SingleComm for further diagnostics.)