EngineeringScore
Performance Medium

Reduce the number of requests

Every distinct file the browser fetches (scripts, styles, fonts, icons, tracking pixels) adds a round trip, and even small requests carry latency overhead that adds up fast, especially on connections with high latency like mobile networks. A page can look lean by total size and still feel slow purely because of how many separate requests it makes.

Why it matters

Every extra request adds latency, especially on slower connections; an excessive request count is a common, fixable reason pages feel sluggish even when total size looks fine.

How to fix

  1. 1 Bundle scripts and stylesheets during the build.
  2. 2 Combine or sprite small icons/images.
  3. 3 Remove unused third-party embeds and duplicate libraries.

Common mistakes

  • Loading several small third-party scripts individually (each with its own analytics/tag-manager dependency) instead of consolidating through a single tag manager.
  • Shipping unbundled ES modules to production, multiplying the request count for what could be a handful of bundled files.
  • Using many small individual icon images instead of an icon font or a single SVG sprite.

How to verify

  1. 1 Open devtools network panel and check the total request count for a typical page load.
  2. 2 Identify the largest contributors (script tags, image requests) and confirm which are genuinely necessary.
  3. 3 Re-run the count after bundling/consolidating to confirm the number actually dropped.

Related checks

Performance Page WeightPerformance Cache HeadersPerformance Render Blocking

Ready to see where you stand?

Scan your site and get your Engineering Score with a prioritized roadmap in under a minute, no signup required.

Scan your site