Performance

Page weight

Checks the total HTML response size (aim for <500 KB).

¿Por qué importa esto?

A heavy page takes longer to load, especially on mobile connections. Google's Core Web Vitals are negatively affected by large page weights. Every extra kilobyte delays the Largest Contentful Paint (LCP).

¿Cómo se soluciona?

Minify HTML, CSS and JavaScript. Remove unused CSS classes and JavaScript. Load scripts asynchronously. Use lazy loading for images. Consider a Content Delivery Network (CDN).

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

Checks the total HTML response size (aim for <500 KB).

A heavy page takes longer to load, especially on mobile connections. Google's Core Web Vitals are negatively affected by large page weights. Every extra kilobyte delays the Largest Contentful Paint (LCP).

Minify HTML, CSS and JavaScript. Remove unused CSS classes and JavaScript. Load scripts asynchronously. Use lazy loading for images. Consider a Content Delivery Network (CDN).

Ejemplo

Copie el código de abajo y adapte el dominio, la marca y el contenido a su situación.

# Vite automatically minifies CSS and JS in production builds
yarn build  # or: npm run build

# TailwindCSS: remove unused classes (tailwind.config.js)
module.exports = {
    content: [
        './resources/**/*.blade.php',
        './resources/**/*.js',
    ],
}

# Lazy loading for images
<img src="product.webp" loading="lazy" width="800" height="600" alt="...">

# Remove unused plugins and scripts from package.json
Empezar gratis