How to diagnose Axios performance using timing, progress events, and limits?

Diagnosing Axios performance requires capturing accurate request timestamps, monitoring upload/download progress to detect stalls, and enforcing size limits that may reveal throughput constraints. However, it is unclear which combination of interceptors, event listeners, or configuration options provides the most reliable timing data without adding overhead, and how to correlate progress events with network conditions to isolate bottlenecks.

Which Axios mechanisms yield precise start‑and‑end timestamps for both Node.js and browser environments? How can progress events be translated into transfer‑rate metrics that highlight slowdowns? What strategies exist to enforce request or response size limits and surface limit violations for performance analysis?