Performance

Page weight

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

Pourquoi est-ce important ?

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).

Comment le corriger ?

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).

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

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).

Exemple

Copiez le code ci-dessous et adaptez le nom de domaine, la marque et le contenu à votre situation.

# 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
Essai gratuit