Using URL Inspection Tool to Troubleshoot Slow Page Loading and Web Page Errors

Troubleshooting issues using Google Chrome browser developer tools

To fix page performance issues encountered in Google Chrome, take note of the following information and send it to the MSPbots Support Team: 

• General information (i.e., Request URL, Request Method; Status Code, Remote Address, and Referrer Policy) 
• Request headers (i.e., Tenantcode, Timezoneid, and Token) 
• Payload 
• Waterfall
• Errors

Follow these steps to gather the needed information: 

1. Open Google Chrome DevTools by pressing F12 on your keyboard.
   You can also launch Chrome DevTools using any of the following methods:
   • Press CRTL+SHIFT+I.
   • Click on the ellipsis ... in the upper right corner of the screen, then click More tools > Developer tools. 
     
     
     
     
   • Right-click on a blank area on the screen, then click Inspect. 
     
     
     
     
2. Investigate which component has performance issues. In the DevTools window, 
   1. Click Network. 
   2. Press CTRL+L to clear the network track log in developer tools. 
   3. Select the Preserve log option to continue tracking logs when you refresh.
   4. Identify the HTTP request type to monitor. If the MSPbots page is loading slowly or is unresponsive, select All. If a widget or area on the MSPbots page is loading slowly, select Fetch/XHR. Since the MSPbots API uses Fetch/XHR, we primarily monitor this type of request. 
      
      
      
      
   5. Click on the feature for troubleshooting. You can refresh the page to record the reload. 
   6. When all requests have been loaded, click Time to sort the time used to complete the request. 

      
      
      
      

   7. Identify any requests that took longer than the acceptable time and select them to view the details. 

   8. Then go to Headers > General and take a screenshot of the General section.
      
      
      
      
   9. Scroll down to the Request Headers section and take a screenshot of the Tenantcode, Timezoneid, and Token.
      
      
      
      
   10. Next, go to Payload > View Source and take a screenshot or copy the statement.
       
       
       
       
   11. Then, go to Timing and take a screenshot of the waterfall breakdown for the request.
       
       
       
       The waterfall is the graphical representation of the different stages of the request. It includes the total processing time of business programs and databases.
       
       
   12. (Optional) If the error icon is in the upper right corner, click on it and click Console at the bottom section of the window. 
       
       
       
       
   13. (Optional) Take a screenshot paywall, of all the errors. If there is a scene you need to record, you can use the tool ScreenToGif to create a GIF. 
   14. Send the screenshots, paywall, waterfall, and the copied statement to MSPbots Technical Support. 
   15. Close the DevTools window. 

Troubleshooting issues using Microsoft Edge browser developer tools

To fix page performance issues encountered in Microsoft Edge, take note of the following information and send it to the MSPbots Support Team: 

• General information (i.e., Request URL, Request Method; Status Code, Remote Address, and Referrer Policy) 
• Request headers (i.e., Tenantcode, Timezoneid, and Token) 
• Payload 
• Waterfall 
• Errors

Follow these steps to gather the needed information: 

1. Open Microsoft Edge DevTools by pressing CRTL+SHIFT+I on your keyboard.
   You can also launch Microsoft Edge DevTools using any of the following methods:
   • Press F12, then select Open DevTools.
     
     
   • Click on the ellipsis ... in the upper right corner of the screen, then click More tools > Developer tools.
     
     
     
     
   • Right-click on a blank area on the screen, then click Inspect.
     
     
      
2. Investigate which component has performance issues. In the DevTools window, 
   1. Click Network. 
   2. Press CTRL+L to clear the network track log in developer tools. 
   3. Select the Preserve log option to continue tracking logs when you refresh.
   4. Identify the HTTP request type to monitor. If the MSPbots page is loading slowly or is unresponsive, select All. If a widget or area on the MSPbots page is loading slowly, select Fetch/XHR.
      Since the MSPbots API uses Fetch/XHR, we primarily monitor this type of request. 
      
      
      
      
   5. Click on the feature for troubleshooting. You can refresh the page to record the reload. 
   6. When all requests have been loaded, click Time to sort the time used to complete the request. 

      
      
      
      

   7. Identify any requests that took longer than the acceptable time and select them to view the details. 

   8. Then go to Headers > General and take a screenshot of the General section.
      
      
      
      
   9. Scroll down to the Request Headers section and take a screenshot of the Tenantcode, Timezoneid, and Token.
      
      
      
      
   10. Next, go to Payload > View Source and take a screenshot or copy the statement.
       
       
       
       
   11. Then, go to Timing and take a screenshot of the waterfall breakdown for the request. 
       
       
       
       The waterfall is the graphical representation of the different stages of the request. It includes the total processing time of business programs and databases. 
       
       
   12. (Optional) Go to Console and take a screenshot of the errors, if there are any. 
       
       
       
       If there is a scene you need to record, you can use the tool ScreenToGif to create a GIF. 
       
       
   13. Send the screenshots, paywall, waterfall, and the copied statement to MSPbots Technical Support. 
   14. Close the DevTools window.