External resource count
Counts external CSS, JS, image, and font files.
¿Por qué importa esto?
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.
¿Cómo se soluciona?
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.
Este check puntúa de 0 a 100. Bajo 50 es un fallo, 50 a 89 un aviso, 90 o más es bueno. Tras cada crawl ve la nota por página en el informe, con una breve explicación.
Preguntas frecuentes
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.
Ejemplo
Copie el código de abajo y adapte el dominio, la marca y el contenido a su situación.
<!-- 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>