External resource count
Counts external CSS, JS, image, and font files.
Pourquoi est-ce important ?
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.
Comment le corriger ?
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.
Ce check note de 0 à 100. Sous 50 c’est un échec, 50 à 89 un avertissement, 90 ou plus c’est bon. Après chaque crawl vous voyez la note par page dans le rapport, avec une courte explication.
Questions fréquentes
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.
Exemple
Copiez le code ci-dessous et adaptez le nom de domaine, la marque et le contenu à votre 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>