The Network Panel
Inspecting HTTP requests, headers, timing, and responses
Skills taught: web.network-panel, web.request-inspection, web.waterfall-reading
Reading the Network panel
Open DevTools (F12), click the Network tab, then reload the page. Every request the page makes appears as a row.
Name — Filename or URL of the resource
Status — HTTP status code (200, 404, 500, etc.)
Type — Resource type (document, fetch, script, img, font)
Initiator — What triggered this request (HTML parser, JS code, CSS)
Size — Response size (compressed + uncompressed)
Time — Total request duration (from send to last byte)
Waterfall — Visual timing bar showing when the request happened
Inspecting a single request
Click any row to see the full details of that request and response:
- Headers tab — Request headers (what you sent) and Response headers (what the server sent back). Check here for Authorization, Content-Type, CORS headers, and Cache-Control.
- Preview tab — Pretty-printed response body. JSON is interactive, HTML is rendered, images show visually.
- Response tab — Raw response body as text.
- Timing tab — Breakdown: DNS, TCP, TLS, Waiting (TTFB), Content download. Long TTFB = slow server. Long Download = large payload.
- Cookies tab — Cookies sent in the request and set in the response.
Filtering requests
Type filter buttons (above the request list):
All → Show everything
Fetch/XHR → Show only API calls (most useful for debugging APIs)
JS → JavaScript files
CSS → Stylesheet files
Img → Images
Font → Font files
Doc → HTML documents
Search box filters:
'api' → Requests with 'api' in the URL
'-status:200' → Requests that did NOT return 200
'larger-than:100k' → Responses over 100KB
Tip: Check Disable cache (checkbox in the toolbar) while developing so you always get fresh responses. Uncheck it when testing caching behavior. Also check Preserve log to keep requests visible across page navigations — useful for debugging redirects.
Frequently Asked Questions
Why do I see (from disk cache) or (from memory cache) in the Network panel?
These mean the browser used a cached copy instead of making a network request. 'From disk cache' — the response was saved to disk from a previous visit and the Cache-Control headers allow reuse. 'From memory cache' — the response is in RAM, available until the tab closes. These are good for performance — it means the user did not have to wait for a network request.
How do I replay a request in the terminal?
Right-click any request in the Network panel → Copy → Copy as cURL. Paste the result in your terminal. This gives you the exact same request (same URL, same headers, same body) that the browser sent. You can then modify it with curl flags to test variations.