Before your website loads a single image or line of text, your server has to respond. The time between a visitor’s browser requesting your page and the server starting to send back data is called Time to First Byte — TTFB. It is the first thing that happens, and if it is slow, everything that follows is slow too.
What causes a slow TTFB
- Slow hosting infrastructure — The single biggest factor. Underpowered shared hosting means the server is slow to respond under any load
- No server-side caching — Without caching, WordPress has to build the page from scratch on every request, querying the database each time
- Outdated PHP version — Older PHP processes WordPress requests more slowly
- Heavy plugins running on every page — Plugins that execute database queries or external API calls on load will delay the server response
- Geographic distance — A server far from your visitors adds latency before a single byte is sent
What is a good TTFB?
Google considers a TTFB under 800 milliseconds acceptable, with under 200ms being ideal. Most well-configured managed WordPress hosting setups comfortably achieve this. Many shared hosting setups do not.
Why it matters beyond speed
TTFB is one of the factors Google measures as part of Core Web Vitals. A slow server response pushes up your Largest Contentful Paint (LCP) score — one of the key signals used in search rankings. Fixing TTFB at the hosting level is often the highest-impact single change you can make to improve both speed and SEO.
If your site feels slow to load and you are not sure why, TTFB is a good place to start. A website checkup will identify whether your server response time is the bottleneck. Read more about performance setup or explore the full hosting knowledge base.
Interested in fast, managed WordPress hosting? View our hosting plans →