How to keep requests under 50 per page
Keep requests under 50 per page. Each request adds latency, especially on mobile networks, and many requests usually mean too many small files and third-party tags. Bundle CSS and JavaScript, inline tiny assets and remove third-party scripts you do not need.
By ratemysite.ai editorial team. Updated .
How do you fix it?
- Open the Network panel in Chrome DevTools, reload the page, and read the request count at the bottom.
- Group requests by domain, and list which third parties add the most.
- Bundle small CSS and JavaScript files, inline tiny icons as SVG, and use a font subset in one file.
- Remove tags, widgets and trackers you no longer use, and load the rest after the main content.
- Re-run the audit and confirm the Request count check passes.
Why does request count matter?
A request is one file fetched over the network, such as an image, a script or a style sheet. Every request carries overhead: headers, scheduling and sometimes a new connection. On a mobile network with 100 ms round trips, 80 requests can add several seconds before all files arrive. Pages that load files from a dozen other domains pay for extra DNS and TLS handshakes for each one.
How do I reduce the number of requests?
First remove what you do not use: old plugins, duplicate libraries and tracking tags. Then combine what is left. Bundle your own scripts into one or two files, put critical CSS inline, and use SVG sprites or inline SVG for small icons. Load below-the-fold images lazily so they do not compete with the first screen. Review third-party tags every quarter, because they are the hardest requests to control and often the slowest.
How much does this check matter?
- This check is worth about 1.4% of the overall score.
- A finished report is reused for 24 hours before you can re-analyze it.
- Each page is fetched with a timeout of 10 seconds, and HTML larger than 2 MB is not audited.
What else do people ask?
- Does HTTP/2 make request count irrelevant?
- It reduces the cost, but not to zero. Each request still adds headers, scheduling and, for third parties, extra DNS and TLS setup.
- What is a reasonable number?
- Under 50 is a good target for most pages. Simple content pages often need under 25.