API Performance

Use API Performance to monitor, analyze and get insights about your website's API performance

Zipy's API Performance helps you to monitor, analyze and quickly fix your API's performance issues.

Zipy provides you with not just analytics, but in-depth insights at multiple levels.

Overall API Performance and Health

You can see Insights and Analytics for your web application's overall API health by checking the graphs, diagnostics and API lists at the entire application level.

Insights give you a quick overview of your web application's APIs most important metrics like API latency, API failures and the impact of the API failures on your users.

You can also see detailed API Performance Diagnostics based on how your APIs are performing with recommendations on how to fix them.

Analytics provide you charts & graphs for various API performance metrics like API Latency, Network Timing Split, API Failures by Latency, API Failures by Geography etc.

Individual API Performance and Health

API Performance also allows you to dig to a particular API and get Insights and Analytics relevant to that API.

You can check detailed graphs, diagnostics and session recordings for every individual API. You can choose a time filter to check data over the time interval that you wish to focus on.

You can dig deeper into each session that may have slow performing or failing API(s) to check the user journey or to collect more information about each API call in the session.

Use the Network tab in Dev Tools to check more details like API response, API response size, Network timings split and even request & response payload (if enabled).

Resource timing and CORS

Zipy uses the Resource Timing API to retrieve information about the timing of various resources loaded by a web application. However, it is restricted by the cross-origin security policies enforced by browsers. By default, only resources loaded from the same origin as the web application are accessible for timing information.

To overcome this limitation, you can enable extended data collection for cross-origin resources subject to Cross-Origin Resource Sharing (CORS). This can be achieved by including the "Timing-Allow-Origin" HTTP response header in your cross-origin resources. For instance, you can grant access to resource timing for any origin by setting the header value to "Timing-Allow-Origin: *". Additional details about CORS can be found in the MDN Web Docs.