How to Fix a Slow Time to First Byte
Cut server response time so everything else on the page can start sooner.
Time to First Byte measures how long your server takes to send the first byte of a response. Everything else waits on it, so a slow TTFB caps Largest Contentful Paint no matter how well the front end is built. Under 800 milliseconds is the target; above 1.8 seconds it is the page's main problem.
Why It Matters
TTFB is the floor under every other timing metric. A 1.5-second server response means LCP cannot be better than 1.5 seconds however small the images are — so front-end optimisation on a slow server is wasted effort.
How to Fix
Find out where the time goes
Cache what does not change per user
Fix the slow queries
Put a CDN in front
Code Fix
bashcurl -w 'connect: %{time_connect}s ttfb: %{time_starttransfer}s\n' -o /dev/null -s https://example.com
connect: 0.180s ttfb: 1.940scurl -w 'connect: %{time_connect}s ttfb: %{time_starttransfer}s\n' -o /dev/null -s https://example.com
connect: 0.020s ttfb: 0.140sPlatform-Specific Instructions
A page cache plugin plus object caching removes most PHP and MySQL work per request. Shared hosting is frequently the real limit.
Prefer static generation or ISR over server rendering for pages that are not per-user, and check that data fetches during render are not crossing the public internet to reach your own API.
Fixed that one.
Now find the rest.
A free audit ranks every issue on your site by the score points it costs — and links each one straight to its guide.
Run a free audit