Description
If a request in the network tab is running long (excess of 10 seconds etc) use the following to check if it is us or them!
Background
This can be used to identify information relating to the time it took for our servers to respond to a long running request. This will help identify if it was us responding that took a while, or if it is related to something non Curve related. This is only one piece of the puzzle, but will help a CS rep to better troubleshoot a slowness issue.
Steps to Follow
- Left click the 3 horizontal lines in the upper right of the browser.
- Left click (or simply hover over) 'More tools'.
- Left click 'Developer tools'.
- Left click the network tab.
- In the second half of the network console, left click the Time column to sort the largest running requests up top (most ms).
- It can be helpful, in the upper half to left click on the long bars to find which request may have been long running if you are targeting something specific.
- Once you have found the suspected request, put your mouse over the bar.
- If done correctly, you will see a summary pop up of the request.
- Left click and the bottom half should then load up the detailed view of the requets.
- Left click the Headers tab.
- Collapse the General section, and scroll down a bit. Find the 'X-Request-Proceesing-Time' entry. This will have a D= followed by a time in milliseconds that it took our servers to respond for this specific request. If the overall time on this request was high, like 7 seconds, but response time was only 400 ms, it likely is NOT a curve issue. Conversely, if the request runs close in time to the overall request, this indicates that the Curve App Servers (or other infrastructure) is likely a culprit when addressing the reason for the delay.
Additional Information
- Left click the 3 horizontal lines in the upper right of the browser.
- Left click (or simply hover over) 'More tools'.
- Left click 'Developer tools'.
- Left click the network tab.
- In the second half of the network console, left click the Time column to sort the largest running requests up top (most ms).
- It can be helpful, in the upper half to left click on the long bars to find which request may have been long running if you are targeting something specific.
- Once you have found the suspected request, put your mouse over the bar.
- If done correctly, you will see a summary pop up of the request.
- Left click and the bottom half should then load up the detailed view of the requets.
- Left click the Headers tab.
- Collapse the General section, and scroll down a bit. Find the 'X-Request-Proceesing-Time' entry. This will have a D= followed by a time in milliseconds that it took our servers to respond for this specific request. If the overall time on this request was high, like 7 seconds, but response time was only 400 ms, it likely is NOT a curve issue. Conversely, if the request runs close in time to the overall request, this indicates that the Curve App Servers (or other infrastructure) is likely a culprit when addressing the reason for the delay.
Copyright 2026 by CD Newco, LLC, USA Proprietary and Confidential All Rights Reserved.
Disclaimer: All information presented herein is solely intended to train employees of Curve Dental customers on the use of the software application described in this Community Article and to illustrate how Curve software can be integrated into a typical practice's operations. Statements and examples used in this Community Article are not intended to contradict or in any way override the written or verbal instructions of the leadership of the customer ("Licensee"). The Licensee is responsible for establishing its own practices and procedures and making each of its employees familiar with them, including those related to the use of the application described in this Community Article. Nothing in this Community Article should be construed to be instructing any Licensee employee to violate any Federal, State, Provincial or other jurisdictional law or regulation; or to violate any aspect of the Licensee's established practices and procedures. The information contained in this document is the copyrighted property of CD Newco, LLC. No part of this document may be reproduced, republished, translated, stored in a retrieval system, or transmitted in any form, or by any means, mechanical, photocopying, recording, or otherwise, without the prior written consent of CD Newco, LLC. Licensees may print copies of this Community Article for their own internal use. CD Newco, LLC may take any action permitted by law to enforce its rights hereto. The information contained in this document is subject to change without notice. The enclosed materials are not a contract and create no rights upon the reader or obligations of any kind on CD Newco, LLC or its affiliates. CD Newco, LLC reserves the right to make changes to any products or services described in this Community Article at any time without notice. CD Newco, LLC shall not be liable for the actions or inactions of the reader in reliance upon the information contained in this document.
Trademarks: Curve is a registered trademark of CD Newco, LLC. Any other product and company names used herein are the property of their respective owners.
Version: This documentation was prepared in conjunction with the latest release of the subject matter of this Community Article, but may be utilized with future releases until such time that more current materials are published.
Comments: Any comments or suggestions regarding the information herein are welcome and should be emailed to the attention of: support@curvedental.com.