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
  • Why am I seeing this diagnostic?
  • How do I fix this?
  1. FAQs
  2. API Performance Diagnostic Help

High Response Time

Why am I seeing this diagnostic?

When your webapp makes API calls, you expect to receive timely responses from the API servers. API latency refers to the time it takes for an API request to travel from your webapp to the API server and for the corresponding response to return to your webapp. API latency includes the Request and Response travel time over the network and it also includes the processing time required for handling the API request by the API server. So, API latency can be influenced by various factors, including network congestion, server load, server processing time, and the overall network infrastructure between your webapp and the API server.

High API latency refers to prolonged delays in receiving the API responses. This can have several implications for you as a webapp developer:

  1. Slower User Experience: High API latency can lead to delays in rendering or updating data in your webapp, resulting in a slower and less responsive user experience. Users may experience frustration due to the perceived sluggishness of your webapp.

  2. Performance Bottlenecks: If your webapp relies on multiple API calls to deliver functionality or fetch data, high API latency can become a performance bottleneck. Slow responses can impact the overall speed and efficiency of your application, affecting its scalability and ability to handle concurrent user requests.

  3. Increased Load on Resources: Long API response times can result in increased resource utilization on both the client and server sides. Your webapp may need to maintain open connections or hold threads while waiting for the API responses, potentially leading to resource exhaustion.

  4. API Dependency Impact: If your webapp relies heavily on specific APIs, high latency from those APIs can significantly impact your application's functionality and performance. It's crucial to monitor and optimize the API latency for critical API dependencies.

How do I fix this?

To address high API latency, consider the following approaches:

  1. Network Optimization: Analyze and optimize your network infrastructure, including routers, switches, and bandwidth allocation, to ensure efficient data transmission and minimize network latency.

  2. Server-Side Optimization: Optimize the server-side infrastructure and API server configurations to handle requests more efficiently, reduce processing time, and improve response times.

  3. Caching and Data Prefetching: Implement caching mechanisms to store frequently accessed data on the client-side or intermediate caching layers. Additionally, consider prefetching or preloading data in advance to reduce the need for real-time API calls.

  4. Asynchronous Processing: If feasible for your use case, consider implementing asynchronous processing or background tasks for API calls that don't require immediate real-time responses. This allows your webapp to continue functioning while waiting for the API responses, improving overall responsiveness.

  5. Load Balancing and Scaling: Distribute the API load across multiple servers or instances using load balancing techniques. Scaling your infrastructure horizontally can help handle increased traffic and reduce API latency.

Monitoring API latency and establishing alerting systems can also help identify performance issues and take proactive measures to optimize latency.

PreviousLarge API Response SizeNextCompression Not Enabled

Last updated 1 year ago