How to Fix Too Many HTTP Requests on Your Web Pages

Every script, stylesheet, font, image, tracking pixel and embed on a page is a separate HTTP request. Our audit counts the requests each crawled page makes and flags the site when too many pages exceed a healthy number. By the end of this guide you will have found what each page loads, removed what it doesn't need, combined or deferred the rest, and confirmed lower request counts across the site.

By Updated ⏱ 1–3 hours🎯 Intermediate● Low impactTechnical
Illustration: Too many HTTP requests fix guide
TECHNICAL · FIX GUIDE Too many HTTP requests IMPACTEFFORT TIME1–3 hours LEVELIntermediate

Why it matters

Request count is not a direct ranking factor. It does slow pages down, especially on mobile connections, where each extra connection, third-party domain and render-blocking file adds latency. That delay shows up in Largest Contentful Paint and Interaction to Next Paint, which are part of Core Web Vitals.

Bloated pages also take longer for crawlers and AI fetchers to render. Every third-party request is another domain that receives your visitors' data and another script that could be compromised. Cutting requests usually improves speed, privacy and security together.

✕Beforehttps://example.com/ makes 148requests to 23 domains: 4 Google Fontsfiles, 19 plugin CSS/JS files, 3 chat✓Afterhttps://example.com/ makes 38 requeststo 4 domains: 1 bundled CSS file, 2deferred JS bundles, 2 self-hosted

What you need

Admin access to your CMS, theme files or codebase
Chrome DevTools (or another browser's network panel)
Access to your tag manager (e.g. Google Tag Manager), if you use one
A staging site or backup so you can roll back changes

Step-by-step fix

1

Measure requests on your heaviest templates

Open your homepage, a product or service page and a blog post in Chrome. Press F12, go to the Network tab, tick Disable cache and reload. The status bar at the bottom shows the total request count.

Sort by Domain or Type to see where the requests come from, and write down the total for each template so you can compare later.

  • Fix templates, not single URLs. One theme change fixes hundreds of pages.
  • Right-click any column header and enable Domain if it is hidden.
Pro tip: Type -domain:example.com into the Network filter box to show only third-party requests. These are usually the easiest to cut.
2

Remove unused plugins, apps and tags

Go through the list of domains and files and ask of each one: is this feature still used on this page? Typical waste includes:

  • Old A/B testing scripts
  • Duplicate analytics, such as GA4 loaded by both a plugin and Tag Manager
  • Social share widgets
  • Slider libraries loaded on pages without a slider
  • Leftover code from uninstalled Shopify apps

Deactivate and delete unused plugins or apps. In Google Tag Manager, pause tags that no longer serve a purpose and publish the container.

Pro tip: Some plugins load their assets on every page even when used on one. WordPress tools like Asset CleanUp or Perfmatters can unload a plugin's CSS/JS per page or post type.
3

Bundle and minify CSS and JavaScript

Combine many small stylesheets and scripts into a few files.

  • If you have a build step, use Vite, esbuild or webpack.
  • If you don't, use a CMS optimization plugin.

With HTTP/2 or HTTP/3, a few medium bundles work better than one huge file or 30 tiny ones. A good split is one bundle for site-wide code and one per heavy template. Load non-critical scripts with defer so they don't block rendering.

html
<!-- Before: 6 separate files -->
<!-- After: -->
<link rel="stylesheet" href="/assets/site.min.css">
<script src="/assets/site.min.js" defer></script>
Pro tip: Turn on bundling options one at a time, then click through key pages and forms after each change. Combined JavaScript is the most common cause of broken menus and checkouts.
4

Self-host fonts and cut font files

Loading Google Fonts or Adobe Fonts from their servers adds a stylesheet request and a connection to another domain, plus one file per weight.

  • Download the WOFF2 files using Fontsource or google-webfonts-helper.
  • Upload them to your own domain.
  • Limit yourself to the weights you actually use, ideally 2.
  • If the font offers a variable font, use it: one file covers every weight.

Then delete the old fonts.googleapis.com link from your theme.

html
@font-face {
  font-family: "Inter";
  src: url("/fonts/inter-var-latin.woff2") format("woff2");
  font-weight: 100 900;
  font-style: normal;
  font-display: swap;
}
Pro tip: Preload only the font used above the fold: <link rel="preload" href="/fonts/inter-var-latin.woff2" as="font" type="font/woff2" crossorigin>.
5

Lazy-load images and replace icon files

Images below the fold should not load until the visitor scrolls. Add loading="lazy" to them, but not to the hero or logo, because that delays Largest Contentful Paint.

Icons are another source of requests. Replace dozens of separate PNG icons or a large icon-font kit with inline SVG or a single SVG sprite.

html
<img src="/img/team.webp" width="800" height="533" alt="Example Co team" loading="lazy" decoding="async">

<svg width="20" height="20" aria-hidden="true"><use href="/icons/sprite.svg#cart"></use></svg>
Pro tip: Always set width and height on lazy images so the layout doesn't jump while they load.
6

Defer heavy embeds until the visitor interacts

A single YouTube iframe can trigger 20+ requests, and chat widgets and maps are similar. Replace them with a lightweight placeholder, called a facade, that loads the real embed only on click.

  • For YouTube, use the lite-youtube-embed pattern below.
  • For chat, load the widget script after the first scroll or click, or a few seconds after page load.
html
<button class="yt" data-id="VIDEO_ID" style="background:url(/img/video-thumb.webp) center/cover;aspect-ratio:16/9;width:100%" aria-label="Play video: Example Co product tour"></button>
<script>
document.querySelectorAll('.yt').forEach(b => b.addEventListener('click', () => {
  b.outerHTML = `<iframe src="https://www.youtube-nocookie.com/embed/${b.dataset.id}?autoplay=1" allow="autoplay; encrypted-media" allowfullscreen style="aspect-ratio:16/9;width:100%;border:0"></iframe>`;
}));
</script>
Pro tip: Save the video thumbnail to your own server so the placeholder doesn't need a request to YouTube either.
7

Re-test and compare request counts

Clear any page cache, CDN cache and plugin cache. Then reload the same templates in DevTools with Disable cache ticked and compare the totals with your notes from step 1. Run Lighthouse (DevTools > Lighthouse > Analyze page load) and check that nothing broke and that LCP and Total Blocking Time didn't get worse.

Finally, re-run our audit so it re-crawls every page and recalculates the share of pages that are over the limit.

Pro tip: Also test a logged-out mobile view. Some plugins and personalization scripts only load for anonymous visitors.

Platform-specific notes

WordPress

Use Perfmatters or Asset CleanUp to unload plugin assets per page. Use WP Rocket or Autoptimize for CSS/JS minify and delay. For fonts, use OMGF (Optimize My Google Fonts), or the built-in Font Library in block themes (Appearance > Editor > Styles > Typography), which stores fonts locally. Block themes also load block CSS only for blocks present on the page.

Shopify

Uninstalled apps often leave snippets behind. Check Online Store > Themes > ⋯ > Edit code, and look for leftover snippets and render tags in theme.liquid. Prefer app embeds you can toggle off in the theme editor under App embeds. Shopify fonts chosen in Theme settings > Typography are already served from Shopify's CDN, so avoid adding separate Google Fonts links.

Next.js

next/font self-hosts Google and local fonts automatically at build time, with no requests to Google. Load third-party scripts with next/script strategy="lazyOnload" or "worker", and use @next/third-parties for YouTube and Google Tag Manager. Use next/image, which lazy-loads by default; set priority (or preload in newer versions) only on the hero image.

Webflow

Enable Site settings > Publishing > Advanced publishing options > Minify HTML, CSS and JS. Upload custom fonts under Site settings > Fonts instead of pasting Google Fonts links into custom code. Audit scripts in Site settings > Custom code and in page-level custom code.

Cloudflare

Cloudflare Zaraz can load analytics and marketing tags server-side, which removes many third-party browser requests. Turn on HTTP/3 under Speed > Optimization (Protocol Optimization). Do not look for Auto Minify: it was retired in 2024, so minify in your build or CMS instead.

Check that it worked

✅ How to verify

  • In Chrome DevTools > Network, with Disable cache ticked, the request total for each main template is clearly lower than your step-1 baseline, and fewer third-party domains appear.
  • WebPageTest (webpagetest.org) shows a lower request count and fewer connections in the waterfall for the first view.
  • Lighthouse shows no new console errors and no worse LCP or Total Blocking Time after the changes.
  • Re-running our audit shows fewer pages flagged, or none, for too many HTTP requests.

⚠️ Common mistakes

  • Fixing only the homepage while blog, product and category templates still load every plugin's assets. The check looks at the share of all crawled pages.
  • Combining all JavaScript into one giant render-blocking file, which cuts requests but makes the page slower to become usable.
  • Adding loading="lazy" to the hero image or logo, which delays Largest Contentful Paint.
  • Self-hosting fonts but leaving the old fonts.googleapis.com link in the theme, so both sets of fonts load.

Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.

Check my site free

FAQ

How many HTTP requests should a web page have?

There is no official limit. A typical content page that loads in under about 50 requests is in good shape, and many pages hit 100+ because of third-party tags and embeds. Look at the trend and where requests come from rather than chasing an exact number. Third-party and render-blocking requests matter most.

Does HTTP/2 make the number of requests irrelevant?

No. HTTP/2 and HTTP/3 send many files over one connection, which makes each request cheaper, but every file still costs header overhead, browser processing and often a cache lookup. Third-party requests also need their own connections to other domains. Fewer, well-sized files are still faster.

Is it legal and safe to self-host Google Fonts?

Yes. Google Fonts are released under open licences such as the SIL Open Font License, which allow self-hosting. Self-hosting also avoids sending visitor IP addresses to Google, which some EU courts have treated as a GDPR issue. For commercial fonts, check your licence terms first.

Will reducing HTTP requests improve my Google rankings?

Not directly, because request count is not a ranking signal. It usually improves Core Web Vitals and user experience, which are page experience factors. It also makes your pages faster for crawlers to render.