deco-loader-n-plus-1-detector

To fix N+1 API calls in SSR, scan your section loaders for map or forEach loops containing external API requests, then replace them with batch endpoints or existing data bridging to reduce server-side latency.

An N+1 API pattern in server-side rendering occurs when loaders make individual API calls for each item in a list, triggering excessive requests that degrade SSR page performance.

Yes, you can detect N+1 query issues across VTEX and Shopify integrations by analyzing loaders in shelves and search results where per-product API calls are commonly executed inside iteration loops.

The best way to optimize per-product API requests in Deco loaders is to reuse existing product data, implement batch endpoints, apply caching strategies, or utilize lazy loading to minimize external calls.

Your Deco storefront loader causes slow SSR response times when it executes external API calls inside iteration loops like map or forEach, creating an N+1 request bottleneck that delays page rendering.