You can optimize images, trim plugins and tune your theme, but if your server takes a long time to answer, every page will still feel slow. The number that captures this is Time to First Byte, or TTFB: the time between a visitor’s browser asking for a page and receiving the first byte of the response.
TTFB is not a Core Web Vital by itself, but it sits underneath LCP. A slow response eats into the 2.5 seconds you have to show the main content. Here is how to measure it and decide whether your hosting is the problem.
What a Good TTFB Looks Like
Google’s guidance treats a TTFB of 0.8 seconds or less as good, and anything over 1.8 seconds as poor. In practice, a well-cached WordPress page on decent hosting should respond in a few hundred milliseconds. Uncached dynamic pages, such as a cart or a logged-in dashboard, will naturally be slower.
How to Measure It
Use more than one method, because a single number can mislead:
- PageSpeed Insights. Look at the diagnostic named Reduce initial server response time, and at the field data for TTFB if it is available.
- Chrome DevTools. Open the Network tab, load your page and click the main document request. The Waiting for server response time is your TTFB.
- WebPageTest. Test from several locations, such as New York, London, Sydney and Frankfurt, to see how location affects the result.
- Your own repeated tests. Load the page several times in a private window and note the range.
Test both a cached request and an uncached one. You can force an uncached load by adding a random query string to the URL, such as ?test=123.
Reading the Results
- Cached fast, uncached slow. Your hosting is acceptable and caching is working, but the application behind it is heavy. Look at plugins, theme code, slow queries and object caching.
- Both slow. The server itself is slow, overloaded or far from your visitors. Hosting is probably the bottleneck.
- Fast at some times, slow at others. This often points to shared resources on a crowded server, or to traffic spikes and background jobs.
- Fast in one region, slow in another. You need a CDN or a server closer to your audience.
What Affects Server Response Time
- Hosting quality and plan. Cheap shared plans put hundreds of sites on one machine, and your site can be affected by its neighbors.
- PHP version. Modern PHP releases are significantly faster than old ones. If your host still runs an outdated version, upgrade after confirming that your plugins and theme are compatible.
- Caching setup. Without page caching, WordPress rebuilds each page, which takes time. See WordPress caching explained.
- Database performance. Slow queries and a bloated options table slow down uncached pages.
- Server location. A server in one country serving visitors on the other side of the world adds latency that no plugin can remove.
- HTTP version and TLS. HTTP/2 or HTTP/3 and modern TLS settings help connections complete faster.
Try the Cheap Fixes First
Before paying for a more expensive plan, check these:
- Turn on full page caching.
- Add a persistent object cache if your site is dynamic.
- Update PHP to a supported, current version.
- Put a CDN in front of the site, ideally with edge caching of static files.
- Remove slow plugins and clean up database bloat.
These steps solve a surprising number of response time problems.
When It Is Time to Upgrade
Consider moving to better hosting when:
- TTFB is still high after caching and optimization.
- Your site slows down badly during traffic peaks or sales.
- You see frequent resource-limit or out-of-memory errors.
- Your host cannot offer a current PHP version, server-level caching, or Redis.
- Your audience is mostly far from your server location and no CDN can fix it.
A good managed WordPress host or a properly configured cloud server does not need to be expensive. What matters is current software, enough resources, server-side caching and a data center near your visitors.
Migrate Carefully
Moving a site is straightforward but easy to get wrong. Back up first, test on the new server before changing DNS, check email delivery, forms and checkout, and keep the old hosting active until the switch is confirmed.
Not sure whether the problem is your host or your site? Request a free audit and I will test your TTFB from several regions and tell you plainly where the time is going. For the full picture of what LCP depends on, read how to improve LCP.
