Time To First Byte (TTFB)
Measures how fast the server returns the first byte (aim for <200ms).
¿Por qué importa esto?
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.
¿Cómo se soluciona?
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.
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
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.
Ejemplo
Copie el código de abajo y adapte el dominio, la marca y el contenido a su situación.
# 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