HTTP requests checker

What the HTTP requests checker does

This tool analyzes a webpage and counts the resources it references, breaking them down by type: CSS files, JavaScript files, images, iframes, videos, and audio. It gives you a structural view of how many requests the page generates.

Every referenced resource is typically a separate HTTP request. Each request adds latency, and a large number of them can slow down loading, especially on high-latency connections. The count also includes resources from third-party domains, which may add connection setup overhead.

Why request count matters

Reducing the number of requests is a classic performance optimization. Fewer requests mean less connection overhead, less time waiting for responses, and fewer opportunities for a slow resource to delay the page. Combining files, using icon fonts or SVG sprites, and removing unused resources are common approaches.

Request count is not the only factor. A few large resources can be slower than many small ones, and HTTP/2 multiplexing changes some of the tradeoffs. Still, the breakdown by type helps identify where the page spends its requests and which categories are worth reviewing.

How to interpret the result

Review the breakdown rather than the total alone. A high number of JavaScript files may indicate a component-heavy page with many small modules. Many images may suggest an image-heavy layout that could benefit from lazy loading. Iframes and media can be especially costly because they may load their own resources.

Look for third-party resources. Widgets, fonts, analytics, and ads often account for a significant share of requests and can be outside your direct control. Prioritize what is essential for the page and consider deferring or removing the rest.

Common request-related issues

• Too many small files. Bundling or consolidation may help.
• Unused CSS and JavaScript. Libraries loaded but not needed on the page.
• Third-party bloat. Multiple widgets each loading their own assets.
• Unoptimized images. Many image requests that could be lazy loaded or combined.
• Redundant resources. Duplicate libraries loaded by different components.

Practical workflow

Review the breakdown on key templates and identify categories with unusually high counts. Remove unused resources, defer non-critical ones, and consolidate where sensible. Test performance after changes, since reducing requests sometimes trades against caching benefits. Re-check periodically as new features add resources.

Limitations

The checker counts resources referenced in the HTML response. It does not measure actual transfer times or sizes, and resources loaded dynamically by scripts may not be included.