Cypress 'cy.intercept()' latency spikes under concurrent requests

When multiple cy.intercept() calls run concurrently, latency spikes often stem from the Cypress proxy's request serialization, which processes intercepted outbound calls sequentially within the same browser event loop. The proxy sits between the application and the network, and under load, queued intercepts accumulate round-trip overhead. Additionally, Cypress's default throttling limits outbound requests to one at a time per origin, and browser event-loop blocking during command execution further delays pending intercepts. These effects compound when tests issue several intercepts in quick succession, especially on older Cypress releases (12) that lack improved concurrency handling.

1. Run cy.intercept() with { respond: false, log: false } and record timestamps before and after each call to isolate queue time from response latency.
2. Compare intercept latency with and without concurrent cy.visit() or other commands to determine whether event-loop blocking is a contributing factor.
3. Check the Cypress version and review release notes for changes to proxy concurrency between major versions (e.g., 12.x vs 13.x).
4. If version is unknown, upgrading to the latest Cypress release often reduces serialization overhead, but verify that the application under test does not itself serialize requests.

To narrow the cause, it helps to know the Cypress major version in use, as proxy behavior and throttling defaults differ between releases. Could you share the Cypress version reported in your test environment?