Global Network Path Analysis

When a user in Mumbai reports that your site is slow, but it's fast in New York, the issue is often in the "Network Path." This includes everything between your server and the browser: DNS resolution, SSL handshakes, and third-party API latency.

Visualizing the Network Waterfall

Every supaguard run generates a Network Trace (HAR). This is your primary tool for path analysis.

1. Open an Execution Result: Navigate to a recent check result.
2. Click 'Network': Explore the waterfall of all requests.
3. Identify the Bottleneck:
   • Long DNS (Magenta): Your DNS provider is slow in that region.
   • Long SSL (Yellow): Your SSL handshake is poorly optimized.
   • Long TTFB (Green): Your server or database is slow to respond.

Using Regional Diagnostics

By rotating checks through East US, West Europe, and Central India, you can compare paths.

Simulating Poor Network Conditions

To test how your application handles high-latency paths (e.g., users on 3G or overseas connections), use Playwright's network throttling.

import { test } from '@playwright/test';

test('low bandwidth experience', async ({ page, context }) => {
  // Simulate 3G network conditions
  await context.setOffline(false);
  await page.route('**/*', route => {
    // Artificial delay of 200ms per request
    setTimeout(() => route.continue(), 200);
  });

  await page.goto('/');
  // Assert that your 'Skeleton Loader' appears
});

When to use Network Path Analysis

• CDN Troubleshooting: Verify if your edge cache is actually being hit in all regions.
• API Performance: Identify slow third-party dependencies (e.g., Stripe, Segment).
• Security Blocks: Detect if specific regions are being blocked by an over-aggressive WAF rule.

Master the Network

• Firewall Allowlisting
• Global Monitoring Network
• API Monitoring Guide