Skip to main content

API Metrics

Open in QuickMonitoring→ Sites → [Your Site] → Scans → API Metrics

During the crawl, QuickMonitoring intercepts every XHR and Fetch request your pages make. It records the endpoint, method, status code, response time, and payload size. This gives you visibility into API health as experienced by real page loads — not synthetic pings to an endpoint in isolation.

What you'll see​

Go to Sites → your site → API Metrics (sidebar).

A list of all API calls intercepted during the crawl:

  • Endpoint — the full URL of the API call
  • Method — GET, POST, PUT, DELETE, etc.
  • Status code — the HTTP response the page received
  • Latency — response time in milliseconds
  • Source page — which page triggered the call

Sort by response time to find slow endpoints. Filter by 4xx/5xx to see API errors that real page renders are triggering.

How to use it​

  1. Run a scan
  2. Go to Sites → your site → API Metrics (sidebar)
  3. Sort by response time to find slow API endpoints affecting page load
  4. Filter by 4xx/5xx status to see API errors during real page renders
  5. Click any entry to see which page triggered the call and the full request/response details

This is especially useful for sites that load data client-side — you can see exactly which API calls are slow or failing before a user reports it.

Pass condition​

✅ You've earned this achievement when the API Metrics section shows at least one intercepted API call, or a "no API calls detected" confirmation on a static site.

Common issues​

  • No API calls showing on a dynamic site — If the site uses server-side rendering and delivers complete HTML, there may be no client-side API calls during the crawl. Check whether your app fetches data after initial load via JavaScript. If it does and nothing appears, check if the API calls are fired by user interaction (scroll, click) rather than on page load — the crawler captures load-time calls only.

  • All calls showing 401 — The crawler hits your API endpoints without authentication tokens. The 401 responses are real and accurate — they're what unauthenticated users see. This is expected behavior for authenticated APIs. To test authenticated API behavior, configure bypass credentials (see Phase 4 → Bypass Setup).

  • API endpoints showing very high latency (1000ms+) — These are real numbers from real page loads. A 2-second API call during page load is a user experience problem, not a false positive. Investigate and optimize the slow endpoint.

  • Duplicate entries for the same endpoint — The same API call may fire on multiple pages. Each instance is recorded separately so you can see which pages are making the call.