Time To First Byte (TTFB)
Measures how fast the server returns the first byte (aim for <200ms).
Why does this matter?
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.
How to fix it?
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.
This check scores from 0 to 100. Below 50 is a fail, 50 to 89 is a warning, 90 or above is good. After each crawl you see the score per page in your report, with a short note on what we found.
Frequently asked questions
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.
Example
Copy the code below and adapt the domain name, brand name and content to your 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