Performance

Cache headers

Checks Cache-Control, ETag and Expires response headers.

Pourquoi est-ce important ?

Good cache headers ensure browsers store static files and don't need to re-download them on every visit. This dramatically speeds up returning visitors and reduces server load.

Comment le corriger ?

Set Cache-Control: max-age=31536000 for static files (CSS, JS, images). Use ETag for dynamic pages. Add Vary: Accept-Encoding for compressed responses.

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 Cache-Control, ETag and Expires response headers.

Good cache headers ensure browsers store static files and don't need to re-download them on every visit. This dramatically speeds up returning visitors and reduces server load.

Set Cache-Control: max-age=31536000 for static files (CSS, JS, images). Use ETag for dynamic pages. Add Vary: Accept-Encoding for compressed responses.

Exemple

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

# Nginx: cache headers for static files
location ~* \.(css|js|woff2|png|jpg|webp|avif|ico)$ {
    expires 1y;
    add_header Cache-Control "public, max-age=31536000, immutable";
}

# HTML pages: no caching (or short TTL)
location ~* \.html$ {
    add_header Cache-Control "no-cache, must-revalidate";
}

# Apache .htaccess
<FilesMatch "\.(css|js|woff2|png|jpg|webp)$">
    Header set Cache-Control "public, max-age=31536000, immutable"
</FilesMatch>
Essai gratuit