Course contentsShow
← Web Development
Lesson 2202 of 2,98240. Browser DevTools Deep DiveFree lesson

Identifying Slow Resources

Sort by size and duration to find performance bottlenecks like large images, slow API calls, or blocking scripts.

Identifying Slow Resources

What you'll learn: How to pinpoint performance bottlenecks by sorting network requests by size and duration in DevTools.

Now that you can inspect individual request timing and waterfall patterns, it's time to hunt down the resources that are actually slowing down your site. The Network Panel gives you powerful sorting capabilities to quickly spot the worst offenders.

The Two Key Metrics

Think of your network activity like a restaurant kitchen. Some dishes take forever to prepare (long duration), while others are massive portions that take forever to carry out (large size). Both types create bottlenecks, but for different reasons.

Sort by Size

Click the "Size" column header in the Network Panel to sort requests from largest to smallest. Look for:

  • Unoptimized images – Multi-megabyte JPEGs or PNGs that should be compressed or converted to modern formats
  • Bloated JavaScript bundles – Hundreds of kilobytes of code that could be split or tree-shaken
  • Oversized fonts – Font files with character sets you're not actually using

Large files consume bandwidth and take longer to download, especially on slower connections.

Sort by Duration

Click the "Time" column to find the slowest requests. Common culprits include:

  • Slow API calls – Backend endpoints taking seconds to respond
  • Blocking scripts – Synchronous resources that freeze page rendering
  • Third-party services – External analytics or ad scripts with poor response times

Long duration often indicates server-side problems, poor network conditions, or resources loaded from distant servers.

The Quick Win Pattern

Sort by size first, tackle anything over 500KB. Then sort by time and investigate anything over 1 second. These extremes usually offer the biggest performance improvements with the least effort.

Key Takeaway: Sort Network Panel requests by size to find oversized assets and by duration to find slow-loading resources—these are your first optimization targets.