Do you have any tips for lowering edge request on vercel?
#edge request
hushed creek
balmy talonBOT
Hi @hushed creek. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
To lower Edge Requests on Vercel, consider the following tips based on the knowledge sources:
-
Reduce unnecessary re-mounting and repeated requests: If your app frequently re-mounts components (like images), it can cause repeated requests. Use browser devtools to identify repeated 304 responses, which indicate content is being fetched multiple times. Optimizing your frontend to avoid unnecessary re-fetching can help reduce Edge Requests.
-
Limit excessive polling or data fetching: Applications that poll APIs for live updates or use libraries like SWR or React Query to reload data on user focus can generate a high number of requests. Review your data fetching strategies and reduce polling intervals or switch to event-driven updates where possible.
-
Leverage caching: Use proper caching headers (e.g.,
Cache-Control) to cache responses at the edge. This reduces the number of requests that reach your backend and serves more content directly from the cache. -
Optimize image usage: Serving a large number of images or using image optimization features can increase Edge Requests. Monitor your image usage and optimize images to reduce the number of requests.
-
Use static generation where possible: For pages that don't require dynamic data, use Static Site Generation (SSG) or Incremental Static Regeneration (ISR) to serve content directly from the edge cache, reducing the need for server-side requests.
For more details and monitoring, you can use the Edge Requests chart in your Vercel dashboard to identify which projects and regions are generating the most requests and optimize accordingly. Frameworks like Next.js are designed to help reduce unnecessary requests automatically, but reviewing your app's specific usage patterns is key to further optimization Manage and optimize Edge Network usage.
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
hushed creek
usually which one of the limits will end first on vercel? @balmy talon
balmy talonBOT
Let me check the knowledge base for you again. Give me one moment! :books:
The knowledge sources do not explicitly state which Vercel limit is most likely to be reached first, as this depends heavily on your specific application's usage patterns and architecture. Vercel provides included usage for several resources—such as Edge Requests, Fast Data Transfer, Function Executions, and others—with different thresholds for Hobby, Pro, and Enterprise plans Limits.
However, Vercel does provide typical monthly usage guidelines for each plan. For example, on the Pro plan, the guidelines are:
- Edge Requests: 10,000,000
- Fast Data Transfer: 1 TB
- Function Execution: 1,000 GB-Hrs
- Image transformations: 10,000/month
Which limit you hit first will depend on your app’s traffic, how much dynamic content you serve, how many images you optimize, and how much data you transfer. For static-heavy sites, Edge Requests or Fast Data Transfer may be reached first. For API-heavy or dynamic sites, Function Execution or GB-Hrs may be the limiting factor Fair use Guidelines.
Vercel recommends monitoring your usage in the dashboard to identify which resources are being consumed most rapidly for your specific project Manage and optimize usage.