Zipy
  • Welcome to Zipy ai
  • Getting Started
    • Install Zipy
    • Installing with Google Tag Manager
    • Supported frameworks
    • Security Overview
    • Sensitive User Data
    • SOC2 Type II
  • Zipy For Mobile
    • React Native Setup
      • Install React Native
      • Input Masking
      • Session Replay
      • Screen Transition Capture
      • Gesture Capturing
      • Unhandled Exception Capture
      • Custom Logging
      • Fetch and XHR Network Calls
      • Profiling
      • Device Information Capture
      • Session URL Retrieval
      • Identify Users
      • Firebase Integration
    • Flutter Setup
      • Install Flutter
      • Session Replay
      • Input Masking & Custom Masking
      • Screen Transition Capture
      • Gesture Capturing
      • Unhandled Exception Capture
      • Custom Logging
      • Http Network Calls
      • Dio Network Calls
      • Profiling
      • Device Information Capture
      • Session URL Retrieval
      • Identify Users
      • Firebase Integration
      • Session Recording Control
      • Data Sanitization
  • iOS Setup
    • Install in an iOS app
    • Identify Users
    • Screen Tracking & Tagging
    • Custom Logging
    • Session URL Retrieval
    • Session Recording Control
    • Input Masking & Custom Masking
  • Chrome Extension
    • Zipy Plug and Play Support
  • Configure
    • Zipy Recording Control
    • Release Version
    • Identifying Users
    • Adding Custom Identifiers
    • Anonymize Users
    • Source Maps
    • Blocking PII data
    • Ignoring Errors/Noise
    • npm Update
    • Support Integration
    • Session Stitching (rootDomain)
  • Product Features
    • Custom Events
    • Session Replay
    • Errors
    • Analytics
    • Time Filters
    • Multiple Filters
    • Clicked Element Filters
    • Manage Teams
    • Stack Trace
    • Console Logs
    • Network Requests
    • Network Headers and Payload
    • Custom Logs
    • Live Users
    • Alerts
      • Slack Alerts
      • Email Alerts
      • Live Alerts
      • Custom Alerts
    • Auto Resolve Errors
    • Zipy Labels Plugin
    • iFrame Support
    • API Performance
    • Heatmaps
    • Page Performance
    • Seen/Unseen Sessions
    • Public Session URL
  • FAQs
    • Install Zipy
    • Session Replay Definition
    • Error Tracking
    • Error Classification
    • Environment Support
    • Impact on your App
    • Performance Impact
    • Mobile Support
    • Network Data Capture
    • API Performance Diagnostic Help
      • High DNS Time
      • High SSL Connection Time
      • High Connection Setup Time
      • Large API Response Size
      • High Response Time
      • Compression Not Enabled
      • Server side API Failures
      • Client side API Failures
      • Insecure Connections
  • Troubleshooting
    • Errors in npm
    • Network header missing in Zipy
    • Can't see user data in sessions
    • No recordings or errors visible
    • No network timing split available
  • Product Videos
    • Ask AI
    • Getting Started
    • Session Replay
    • Multiple Project Creation
    • Team Management
    • Alerting on Slack
    • Time Filters and Daily Alerts
    • Custom Identifiers
    • Ignore Errors
    • Identify Users
    • Dashboard
    • Resolve Errors
    • New Error Digest
    • Jira and Slack
    • Online/Offline Network Status
    • Zipy on Zipy
      • Zipy Product Roadmap
  • Whats new
    • Product Updates
  • Legal & Policy
    • Terms of Service
    • Privacy Policy
    • Fulfillment Policy
    • Cookie Policy
    • Acceptable Usage Policy
    • Zipy Sub Processor List
  • Integration
    • Azure DevOps
    • Factors
    • RB2B
    • Webflow
    • WordPress
    • Amplitude
    • Coralogix
    • DevRev
    • Drift
    • Errorception
    • Freshchat
    • Google Analytics
    • Heap
    • HelpScout
    • Honeybadger
    • Hubspot
    • Intercom
    • Mixpanel
    • New Relic
    • Pendo
    • Raygun
    • Rollbar
    • Segment
    • Sentry
    • Shopify
    • Sumo Logic
    • TrackJS
    • Zendesk
Powered by GitBook
On this page
  • Overall API Performance and Health
  • Individual API Performance and Health
  • Resource timing and CORS
  1. Product Features

API Performance

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

PreviousiFrame SupportNextHeatmaps

Last updated 1 year ago

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 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 .

Resource Timing API
MDN Web Docs