What TTFB is and why PageSpeed flags it as a problem
When a visitor types your website’s address, their browser sends the server a request. The server assembles the page (an online store loads products from the database, for example) and starts sending it back. The time from the request to the first received byte is TTFB.
PageSpeed Insights (Google’s free website speed tool) shows it as the recommendation Reduce initial server response time. And it flags it for good reason. Until the first byte arrives, the browser can do nothing at all. No image, no text, just a white screen. High server response time therefore slows down everything else, including LCP (Largest Contentful Paint, the time it takes for the largest element of the page to appear), which Google uses when evaluating websites.
In other words: TTFB is the foundation the entire speed of a website stands on. You can have the lightest theme in the world, but if the server takes two seconds to answer, the visitor stares at a blank page for two seconds.
What TTFB value is acceptable
The rough thresholds look like this:
| TTFB | Rating |
|---|---|
| under 200 ms | excellent, the site responds instantly |
| 200-500 ms | good, normal for quality hosting |
| 500-800 ms | borderline, worth investigating |
| over 800 ms | a problem, visitors feel the wait |
Google recommends keeping server response under 800 ms; a fast website aims under 200 ms. For perspective: 200 ms is the blink of an eye, 800 ms is already a noticeable pause. A static page (a finished file the server just sends out) can answer within a few tens of milliseconds. An online store or a WordPress site that assembles each page from a database needs more, but should still fit within a few hundred milliseconds.
Always measure several times and at different times of day. A single value means nothing; an overloaded server fluctuates. And measure specific subpages too, not just the homepage. A product detail or the cart tends to be slower.
Where to measure TTFB for free
You do not need to install or pay for anything:
| Tool | Where to find TTFB |
|---|---|
| PageSpeed Insights (pagespeed.web.dev) | recommendation Reduce initial server response time |
| GTmetrix (gtmetrix.com) | Performance tab, TTFB item |
| WebPageTest (webpagetest.org) | first row of the waterfall, can test from Europe |
| Chrome (F12 key) | Network panel, Waiting for server response on the page entry |
The easiest start: open pagespeed.web.dev, paste your website address and wait for the result. If server response shows up among the recommendations, read on.
The most common causes of high server response time
High TTFB almost always points to the server and the hosting, not to images or the theme. The usual culprits:
- Overloaded shared hosting. Hundreds of websites run on one server and all share the same resources (like an apartment block with one boiler; when everyone showers in the morning, the water runs lukewarm). Your website then waits in a queue.
- Missing server cache. A cache is a stored, ready-made copy of a page that the server sends instantly instead of building it again and again. Without it, the server generates the same page for every single visitor.
- Old PHP version. PHP is the language WordPress and most ecommerce platforms run on. Newer versions process the same page much faster, and old versions are losing security support.
- Slow database and too many plugins. Every plugin (an add-on extending the website’s features) can add more database queries. On WordPress, server response time often grows exactly with the number of active plugins.
- Server distance. Data travels physically; every kilometre costs time. A website for European customers hosted across the ocean has a higher response time before the server even starts working.
How to lower TTFB: tweaks, or a faster server
Some of it you can handle yourself on your current hosting. Turn on caching (for WordPress a proven plugin is enough; many hosts also cache at server level, ask support). Ask your host for a current PHP version; it is usually one click in the control panel. Go through your plugins and disable the ones you do not use. Measure again after every change.
If you have done all this and TTFB stays high, you have hit your hosting’s ceiling. No plugin will speed up an overloaded shared server, because the problem is not your website but who you share it with. Then it makes sense to move to faster hosting or a managed server. Do not fear the move: we migrate without downtime, and with our hosting plans it is free. The website keeps running on the old server until the new one is tested; visitors notice nothing.
Why a server in a Prague datacenter helps
You cannot cheat distance. When the server sits in Prague and your customers are in Central Europe, data travels in a few milliseconds. Our hosting runs in a Prague TIER III datacenter (a certification guaranteeing redundant power and cooling, i.e. operation even when one component fails). Plans start at CZK 550/month and admins respond within hours. And if you already have your own server and simply nobody looks after it, we will take over its management at CZK 1,500/hour.
Checklist: what to do right now
- Measure your TTFB for free at pagespeed.web.dev. Paste your website address and find the recommendation Reduce initial server response time.
- Verify the value with a second tool (gtmetrix.com or webpagetest.org with a European test location) and repeat the measurement in the morning, afternoon and evening.
- Besides the homepage, measure a product detail and the cart; they tend to be the slowest.
- Turn on caching. For WordPress a proven cache plugin; ask your host’s support about server-side caching.
- Check the PHP version in the hosting control panel and switch to the newest supported one.
- Disable plugins you do not use and measure again.
- Ask your host where the server physically runs. You want a server close to your customers.
- If TTFB is still above 800 ms after these steps, the problem is the hosting, not your website. The solution is a faster server.
High TTFB? We will measure what causes it
Send us your website address and within a few days you will get a free audit report: server response time, findings and a proposed fix. No obligation.