How to Reduce Time to First Byte on a Small Website
Your images are compressed, your scripts are trimmed, and PageSpeed Insights still tells you the server responded slowly.

Your images are compressed, your scripts are trimmed, and PageSpeed Insights still tells you the server responded slowly. That warning is about time to first byte, the wait between a browser asking for your page and the first scrap of HTML arriving. If you want to reduce time to first byte, most of the fixes sit on the server side, and on a small website a handful of changes usually cut it in half.
I have tuned dozens of small business sites on cheap shared hosting. Below is how to measure the number properly, what a good result looks like, and the fixes in the order I would try them.
What time to first byte measures
Time to first byte, often shortened to TTFB, covers everything that happens before the page can start to render:
- The DNS lookup that turns your domain into an IP address
- The connection and the HTTPS handshake
- The time your server spends building the page, such as running PHP and querying a database
- The trip back across the network to the visitor
Google treats a TTFB of 800 milliseconds or less as good, and anything over 1.8 seconds as poor. For a small site with mostly static content, I aim for under 300 ms for visitors in the same country as the server.
| TTFB | Rating | What it usually means |
|---|---|---|
| Under 300 ms | Excellent | Cached pages or a static site near the visitor |
| 300 to 800 ms | Good | Normal for a dynamic site on decent hosting |
| 800 ms to 1.8 s | Needs work | No page cache, slow plugins or a distant server |
| Over 1.8 s | Poor | Overloaded hosting or a heavy database query |
How to measure it properly
A single test means very little, because TTFB changes from minute to minute. Run at least three tests and take the middle result.
- Browser developer tools. In Chrome, open DevTools, go to the Network tab, reload the page and click the first document request. The Timing tab shows "Waiting for server response", which is your server time.
- PageSpeed Insights. The field data section shows real TTFB from Chrome users, if your site has enough traffic. Our guide on how to read a PageSpeed Insights report without panicking explains where to find it.
- Test from more than one place. Use a tool that tests from several cities. A site hosted in Germany may show 150 ms from Frankfurt and 900 ms from Sydney.
Test both a cached page you have visited before and a fresh one, such as a recent post. The gap between the two tells you how much caching is helping.
Fixes that reduce time to first byte
1. Turn on page caching
This is the biggest win for almost every dynamic site. Without a cache, a WordPress server runs PHP and dozens of database queries for every single visitor. With a page cache, it builds the page once and serves a saved HTML copy afterwards. I regularly see TTFB drop from 1.2 seconds to under 200 ms just from this step. Most hosts include a caching option in their control panel, and well-known caching plugins handle it in a few clicks.
2. Update PHP
Many old sites still run PHP 7.4 or earlier. Moving to PHP 8.2 or newer is often 15 to 30 percent faster for the same code. Check your hosting panel, take a backup, switch versions and test the site. If a plugin breaks, update or replace it.
3. Remove slow plugins and heavy queries
Each plugin adds work before the page is sent. Deactivate plugins you no longer use, and look for ones that run on every page load, such as related post widgets, live visitor counters and some security scanners. A query monitoring plugin can show which ones take the longest.
4. Use a CDN
A content delivery network stores copies of your pages and files in data centres around the world, so a visitor in Sydney gets them from Sydney. Many CDNs have a free plan. For HTML caching at the edge you may need to enable a specific setting, because by default many only cache images and scripts.
5. Fix DNS and HTTPS overhead
A slow DNS provider can add 100 ms or more before anything else happens. Moving DNS to a fast provider, often the same company as your CDN, is a quick fix. Make sure your server supports HTTP/2 or HTTP/3 and TLS 1.3, which need fewer round trips for the secure connection.
Why upgrading your hosting plan is rarely the first fix
The usual advice when TTFB is slow is to buy better hosting. It can help, but it is often the most expensive way to fix a problem that caching would solve for free. A 30 pound a month VPS running an uncached site with 40 plugins will still be slow. A 4 pound shared plan serving cached pages can return HTML in 200 ms.
Upgrade only after you have turned on caching, updated PHP and cleaned up plugins, and only if TTFB is still poor on cached pages. At that point the server itself is the bottleneck, usually because the shared machine is overloaded. Our post on why website speed matters and how to improve it puts server speed in context with the other factors visitors notice.
What TTFB does not fix
A fast first byte only gets the page started. If your HTML then pulls in five large images, three font files and a chat widget, the page will still feel slow. Once the server side is in good shape, turn to the front end. Our guide on how to lazy load images the right way on a small site is a good next step, since images are the heaviest part of most pages.
Keep a simple log of your tests: date, page tested, TTFB from your country and from one distant city. Check it after every big change, such as a new plugin or a theme update. Slow creep is easy to miss without a record. I have watched a site drift from 250 ms to 1.4 seconds over a year, one harmless looking plugin at a time, and nobody noticed until enquiries dropped.
Frequently asked questions
What is a good time to first byte?
Google considers 800 milliseconds or less to be good. For a small, mostly static site, under 300 ms is achievable with page caching and a nearby server or CDN. Anything above 1.8 seconds needs attention.
Does TTFB affect SEO?
TTFB is not a Core Web Vital on its own, but it directly affects Largest Contentful Paint, which is. A slow first byte delays everything that follows. Improving TTFB usually improves LCP and how fast the site feels to real visitors.
Why is my TTFB high even with caching?
The cache may not be serving the page you tested, for example if you were logged in or the page was excluded. It can also be a distant server, slow DNS or an overloaded shared host. Test in a private window, from several locations, and compare a cached page with an uncached one.
More in Performance
Performance
How to Fix a Slow Interaction to Next Paint Score
A client rang me in October because the booking form on her site felt broken on phones. Nothing was broken.
Performance
How to Load Web Fonts Faster on a Small Website
A small business site I looked at last month scored 94 on PageSpeed for desktop and 61 on mobile.
Performance
How to Reduce Server Response Time on a Small Website
You compressed every image, removed the slider and switched to a lighter theme, yet your speed report still shows a red warning...