Audit & Analysis

Network Inspector — Watch Requests on Any Web Page

Watch requests as a page loads with status codes, methods, resource types, durations, failures and expandable request and response headers. It works on local, staging and authenticated pages because it observes the tab you are already debugging.

What is Network Inspector?

The Network Inspector in UltraDevKit helps you work with a live web page. Watch requests as a page loads with status codes, methods, resource types, durations, failures and expandable request and response headers. It works on local, staging and authenticated pages because it observes the tab you are already debugging.

Category

Audit & Analysis

Best for

Find the API call returning a 4xx or 5xx while debugging a feature; Spot slow images, scripts or font requests on a real page load

Runs on

Any page in Chrome

When you'd use it

• Find the API call returning a 4xx or 5xx while debugging a feature
• Spot slow images, scripts or font requests on a real page load
• Confirm request headers and payloads without opening a separate proxy
• Investigate a failed request on a page behind a login or on localhost

How to use Network Inspector

1. Open Network Inspector before reproducing the behaviour you want to study.
2. Reload the page or trigger the interaction that makes the request.
3. Filter by URL, method or resource type, then switch to Failed or In flight.
4. Select a request to inspect its status, timing, headers, body and error text.

Network Inspector FAQ

Does it capture requests made before I open the tool?

No. Start it before reloading or repeating the interaction. The inspector keeps the most recent 500 requests while it is active.

Why can Chrome ask for debugger access?

The tool uses Chrome's debugger transport to observe Network events in the current tab. It does not send captured traffic to UltraDevKit or another service.

Can it show response bodies?

It shows response metadata and headers. Reading every response body would add privacy, memory and performance costs, so use the URL and headers to narrow the issue before opening the request in DevTools.

Works well with