Performance guide
How to Improve Server Response Time (TTFB)
In short
Time To First Byte is how long the server takes to start replying. Most slow s come down to distance and missing caching, so host close to your visitors and turn on server-side page caching.
TTFB measures the gap between a browser requesting a page and receiving the first byte back. Google flags anything over ~800ms; for a good experience aim well under 200ms for your main audience.
What causes a slow TTFB
- Overloaded or low-spec shared hosting.
- A server far from your visitors (e.g. US hosting for UK customers).
- No caching, so every page is rebuilt from the database on each request.
- Heavy, unoptimised code or database queries.
1. Host close to your audience
Network latency is physics. If your customers are in the UK, host in the UK. UK-to-UK round trips are single-digit milliseconds, versus 80ms+ to the US, before the server even does any work. This is the easiest big win for a UK business.
2. Cache aggressively
Server-side page caching ( Cache, Varnish, or full-page caching) means the server returns a ready-made page instead of building one. For a cached page the server skips PHP and the database entirely.
3. Use a fast stack
Modern PHP, a tuned database, and a web server like LiteSpeed respond far faster than an unconfigured, outdated setup. Object caching (Redis/Memcached) speeds up dynamic pages.
4. Put a CDN in front
A CDN with edge caching can answer many requests without touching your origin server at all, flattening TTFB worldwide and absorbing spikes.
5. Measure it
Check TTFB in your browser's Network tab, or with WebPageTest/PageSpeed Insights. Test from where your visitors are.
Fast UK servers, low TTFB
Host on UK LiteSpeed servers with caching built in for a fast response from the first byte.
See hosting plansQuestions
What is a good TTFB?
Under 200ms is good; under 800ms is acceptable. Above that, Google and visitors notice the delay.
Does a CDN fix a slow server?
It helps for cached/static content, but a slow origin still affects uncached and dynamic requests. Fix the host and caching first.
Why does location matter so much?
Data travels at a finite speed. The further the server, the longer every request takes before any processing. A round trip from the UK to the US east coast takes around 70 to 80ms.