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 about the server taking too long to respond.

You compressed every image, removed the slider and switched to a lighter theme, yet your speed report still shows a red warning about the server taking too long to respond. That warning means the browser is waiting before it receives a single byte of your page, and nothing you do to images or scripts can fix that wait. To get a genuinely fast site, you have to reduce server response time at the source.
The good news is that on most small websites the cause is one of four or five common problems, and the fixes are cheaper and simpler than people expect. Here is how to measure it, what a good number looks like, and what to fix first.
What server response time actually measures
Server response time is usually measured as Time to First Byte, or TTFB. It is the time between the browser asking for your page and the first piece of the reply arriving. It includes:
- The DNS lookup to find your server.
- The connection and security handshake.
- The time your server spends building the page, which on a site like WordPress means running PHP and querying the database.
- The travel time back to the visitor.
The third item is usually the biggest and the one you control most. A dynamic page that is built from scratch on every visit might take 800 ms to 2 seconds on cheap shared hosting. The same page served from a cache can arrive in under 200 ms.
How to measure your TTFB
Test more than once, and test from more than one place, because a single result can be misleading.
- PageSpeed Insights: run your home page and look for "Reduce initial server response time" under diagnostics. It flags pages where the server takes more than about 600 ms. If the report itself looks overwhelming, read our guide on reading a PageSpeed Insights report without panicking.
- Browser developer tools: open the Network tab, reload the page, click the first document request and look at the "Waiting for server response" figure in the Timing panel.
- Command line: if you are comfortable with a terminal, use curl with its time_starttransfer timing variable against your home page. Run it five times and average the results.
Test while logged out, in a private window. Logged in users often bypass the cache, which makes the site look slower than visitors experience it.
What counts as a good result
| TTFB | Verdict | What to do |
|---|---|---|
| Under 200 ms | Excellent | Nothing, look elsewhere for speed gains |
| 200 to 600 ms | Fine for most small sites | Check caching is on for every page |
| 600 to 1,200 ms | Slow | Work through the fixes below in order |
| Over 1,200 ms | A real problem | Caching first, then consider your host |
Five ways to reduce server response time
Work through these in order. Each one is cheaper and quicker than the one after it.
1. Turn on full page caching
This is the single biggest fix for most small sites. Page caching saves a finished copy of each page as a static file, so the server can send it instantly instead of rebuilding it with PHP and database queries every time. On WordPress, a free caching plugin or the caching built into many hosts can cut TTFB from over a second to around 100 to 300 ms. Pair it with browser caching on your website so returning visitors load even less.
2. Update to a current PHP version
Each major PHP release has brought real speed improvements. Sites still running PHP 7.4 often get noticeably faster on PHP 8.2 or 8.3, with no other changes. Test on a staging copy first, as our guide to updating PHP safely on a small website explains.
3. Remove slow plugins
Every active plugin can add code that runs on each request. Deactivate plugins one at a time on a staging site and retest TTFB. Related posts widgets, visitor statistics and social share counters are frequent offenders. I have seen a single stats plugin add 400 ms by itself. Keep a short list of each plugin and the time it adds, so you can make an honest call about which ones earn their place.
4. Clean the database
Old post revisions, expired temporary data and spam comments make queries slower. Limit revisions to around 5 per post, clear spam and trash monthly, and remove tables left behind by plugins you deleted. Back up first.
5. Put the server close to your visitors
If your audience is in Australia and your server is in Texas, every request crosses the Pacific twice. Choose a data centre in the same region as most of your readers, or use a CDN that can cache full pages near them.
Why upgrading your hosting plan is not the first fix
When TTFB is slow, the usual advice is to move to a more expensive host. Hosting companies are happy to agree. Sometimes it is the right answer, but often it is the most expensive way to fix a problem that caching would have solved for free.
A site with no page cache on a 30 dollar a month plan will often be slower than a well cached site on a 5 dollar plan, because the expensive server is still building every page from scratch. Upgrading hardware makes slow code run a little faster. Caching means the slow code barely runs at all. Turn on caching, update PHP and trim plugins first. If TTFB is still above 600 ms on cached pages after that, then the host genuinely is the bottleneck, and paying more makes sense.
Signs your host really is the problem
- Cached pages, which should be fast, still take over 500 ms.
- TTFB swings wildly between tests, from 300 ms to 3 seconds, which suggests an overcrowded shared server.
- Your control panel shows you regularly hitting CPU or memory limits.
- Support suggests the answer is always a pricier plan, but cannot explain what is slow.
If two or more of these apply, moving to a better shared host or a small managed plan is worth the cost. Take a full backup and measure TTFB before and after so you know the move actually helped.
Frequently asked questions
What is a good server response time?
Under 200 ms is excellent, and anything under 600 ms is fine for most small websites. PageSpeed Insights warns when the server takes longer than about 600 ms. Above one second, visitors start to notice the delay.
Does a CDN reduce server response time?
A CDN reduces travel time by serving files from a location near the visitor. It only helps TTFB for the HTML page itself if it is set to cache full pages. Otherwise it speeds up images and scripts but not the first response.
Why is my TTFB slow even with caching?
Check that you are testing while logged out, as logged in users often skip the cache. Some pages, such as carts and search results, are excluded from caching. If cached pages are still slow, the hosting server is likely overloaded.
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 Set Up Browser Caching on a Small Website
Your PageSpeed report keeps flagging "Serve static assets with an efficient cache policy", and every returning visitor...