Too many HTTP requests per page: what it is, why it matters, and how to fix it
The page references more than 80 resources, resulting in excessive HTTP requests that slow down page loading.
Where this fits: performance in SEO
Why too many http requests per page hurts your rankings
Each HTTP request incurs overhead from DNS lookup, TCP connection, TLS handshake, and server processing. While HTTP/2 multiplexing helps, excessive requests still compete for bandwidth and processing time. Browser connection limits can cause request queuing, delaying critical resources.
This is a high-severity issue: it directly suppresses rankings or click-through on the pages it affects. It belongs in your current sprint, prioritised by how many pages carry it.
How to fix it
Reduce requests by bundling CSS and JavaScript files, using CSS sprites or icon fonts, inlining small resources, removing unused third-party scripts, and implementing lazy loading for non-critical resources.
Frequently asked questions
What does "Too many HTTP requests per page" mean?
The page references more than 80 resources, resulting in excessive HTTP requests that slow down page loading.
Why does too many http requests per page matter for SEO?
Each HTTP request incurs overhead from DNS lookup, TCP connection, TLS handshake, and server processing. While HTTP/2 multiplexing helps, excessive requests still compete for bandwidth and processing time. Browser connection limits can cause request queuing, delaying critical resources.
How do I fix too many http requests per page?
Reduce requests by bundling CSS and JavaScript files, using CSS sprites or icon fonts, inlining small resources, removing unused third-party scripts, and implementing lazy loading for non-critical resources.
How serious is this issue?
This is a high-severity issue: it directly suppresses rankings or click-through on the pages it affects. It belongs in your current sprint, prioritised by how many pages carry it. It belongs to the performance family of checks.
How do I find every page affected by this on my site?
Run a free Dr Urls audit: it crawls your site, detects too many http requests per page on every affected page, shows example URLs, and generates a ready-to-use fix task. Re-scan after fixing to verify the issue is gone.
Does your site have this issue?
A free Dr Urls audit crawls your site, finds every page affected by too many http requests per page, and hands you a ready-made fix task.
Check my site free