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

Compression Not Enabled

Why am I seeing this diagnostic?

When your webapp makes API calls, it receives responses from the API servers. These responses can contain various types of data, such as JSON, XML, or binary files. API response compression refers to the process of reducing the size of the response data before transmitting it over the network by applying compression algorithms such as GZIP or Brotli. The compressed response is then decompressed by the client to obtain the original data.

Not compressing large API responses can have several implications for you as a webapp developer:

  1. Increased Network Bandwidth Usage: Large API responses without compression consume more network bandwidth when transmitted from the API server to your webapp.

  2. Slower Response Times: Transmitting larger amounts of data without compression takes longer, resulting in slower response times. This delay can impact the user experience, as your webapp may take more time to process and render the received data.

  3. Higher Network Latency: Large API responses can increase network latency, especially for users with slower internet connections or when accessing your webapp from remote locations.

  4. Mobile Data Usage: Uncompressed API responses can consume a significant amount of users' mobile data plans. This can lead to increased costs for your users or affect their data usage experience, especially for mobile applications.

How do I fix this?

To mitigate the impact of not compressing medium and large API responses, consider the following:

  1. Enable Compression: Implement compression algorithms like GZIP or Brotli on the server side to compress API responses before transmitting them to your webapp. This reduces response sizes, improves network efficiency, and minimizes bandwidth usage.

  2. Support Compression on the Client: Ensure that your webapp is capable of decompressing and handling compressed responses. Most modern web browsers and HTTP client libraries have built-in support for decompressing responses.

  3. Content-Encoding Headers: Set appropriate Content-Encoding headers in the API responses to indicate that compression has been applied. This allows the client to identify and decompress the response correctly.

  4. Test and Optimize: Monitor the performance of your API calls, including response sizes and transmission times. Identify API endpoints that return medium or large responses and optimize them for better efficiency and user experience.

PreviousHigh Response TimeNextServer side API Failures

Last updated 1 year ago