External resource count
Counts external CSS, JS, image, and font files.
Why does this matter?
Each external resource requires a separate HTTP request. With HTTP/1.1, browsers can only handle 6 requests per domain simultaneously. Many files = longer load time, especially on mobile.
How to fix it?
Bundle CSS and JS files. Remove unused plugins and scripts. Use a CDN for common libraries. Load fonts via font-display: swap. Limit the number of external domains you load resources from.
This check scores from 0 to 100. Below 50 is a fail, 50 to 89 is a warning, 90 or above is good. After each crawl you see the score per page in your report, with a short note on what we found.
Frequently asked questions
Counts external CSS, JS, image, and font files.
Each external resource requires a separate HTTP request. With HTTP/1.1, browsers can only handle 6 requests per domain simultaneously. Many files = longer load time, especially on mobile.
Bundle CSS and JS files. Remove unused plugins and scripts. Use a CDN for common libraries. Load fonts via font-display: swap. Limit the number of external domains you load resources from.
Example
Copy the code below and adapt the domain name, brand name and content to your situation.
<!-- Everything bundled: 1 CSS file + 1 JS file --> <link rel="stylesheet" href="/build/assets/app-abc123.css"> <script src="/build/assets/app-def456.js" defer></script> <!-- Fonts via CDN with preconnect --> <link rel="preconnect" href="https://fonts.bunny.net"> <link href="https://fonts.bunny.net/css?family=inter:400,600,700" rel="stylesheet"> <!-- External scripts loaded asynchronously --> <script src="https://www.googletagmanager.com/gtag/js" async></script>