Time To First Byte (TTFB)
Measures how fast the server returns the first byte (aim for <200ms).
Pourquoi est-ce important ?
TTFB is the time from sending an HTTP request to receiving the first byte of the response. Google considers a TTFB of >600ms as slow. High TTFB is usually a sign of slow server processing, overloaded databases, or lack of caching.
Comment le corriger ?
Enable server-side caching (Redis, Memcached, full-page cache). Optimize database queries executed during page load. Use a CDN to serve static content closer to the user. Upgrade to a better hosting solution if the server is systematically overloaded.
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
Measures how fast the server returns the first byte (aim for <200ms).
TTFB is the time from sending an HTTP request to receiving the first byte of the response. Google considers a TTFB of >600ms as slow. High TTFB is usually a sign of slow server processing, overloaded databases, or lack of caching.
Enable server-side caching (Redis, Memcached, full-page cache). Optimize database queries executed during page load. Use a CDN to serve static content closer to the user. Upgrade to a better hosting solution if the server is systematically overloaded.
Exemple
Copiez le code ci-dessous et adaptez le nom de domaine, la marque et le contenu à votre situation.
# Laravel: enable Redis caching (.env) CACHE_DRIVER=redis SESSION_DRIVER=redis QUEUE_CONNECTION=redis # Nginx: FastCGI page caching fastcgi_cache_path /tmp/nginx_cache levels=1:2 keys_zone=SITE:100m inactive=60m; fastcgi_cache_key "$scheme$request_method$host$request_uri"; fastcgi_cache_valid 200 301 60m; # PHP-FPM tuning (php-fpm.conf) pm = dynamic pm.max_children = 50 pm.start_servers = 10 pm.min_spare_servers = 5