HTTP requests checker
Count the resources requested by a webpage.
Last submissions
What this checker does
The HTTP requests checker counts the resources a webpage requests. It looks at the HTML and identifies references to CSS files, JavaScript files, images, iframes, videos, and audio. The total gives a rough picture of how many separate network requests the page may trigger.
Each request adds overhead: connection setup, headers, and time. Reducing the number of requests is one of several ways to improve loading performance, especially on slower connections.
What is counted
The tool reports totals for several resource types:
- CSS files: external stylesheets linked in the document.
- JavaScript files: external scripts referenced by the page.
- Images: image elements and other image references found in the HTML.
- Iframes: embedded frames.
- Videos and audios: media elements.
The count is based on references present in the HTML. It does not include resources loaded later by JavaScript, CSS background images, or requests made by third-party embeds after they initialize.
Why request count matters
Browsers can open multiple connections in parallel, but there are limits. Many small requests can still add up, particularly on high-latency networks. Each request may involve DNS lookups, TLS handshakes, and waiting for a response.
Fewer requests are not automatically better. A single large file can be slower than several smaller ones in some cases. The goal is to understand the page’s composition and remove unnecessary requests, not to minimize the number blindly.
Reading the results
The output shows counts by resource type. A page with many scripts and stylesheets may benefit from bundling or removing unused files. A page with many images may benefit from lazy loading, responsive images, or format optimization.
The checker does not measure file sizes or load times. It also does not tell you which requests are necessary. Use the counts as a starting point for review.
Practical guidance
- Remove unused resources: check whether all referenced scripts and stylesheets are needed on that page.
- Combine where sensible: bundling small CSS or JS files can reduce request overhead, though modern HTTP/2 reduces the benefit.
- Lazy-load below-the-fold media: images and iframes that are not immediately visible can be deferred.
- Audit third-party embeds: social widgets, fonts, and analytics add requests you may not control directly.
Limitations
The checker analyzes the initial HTML for the URL you provide. It does not execute JavaScript, so dynamically loaded resources are not counted. It also does not measure actual network activity in a browser.
Use the results alongside browser developer tools and performance testing for a complete view of page loading behavior.
Similar tools
Measure the total size of a webpage, including all of its resources.
Find JavaScript tags and display their defer and async attributes.
Count the total number of HTML elements in a page to assess DOM complexity.
Popular tools
Check which images on a page are missing alt attributes for accessibility and SEO.
Check which images on a page use lazy loading and which load immediately.
Measure the total size of a webpage, including all of its resources.
Check whether a page is blocked from search indexing by meta tags, headers or robots.txt.