Book a call Free rebuild
Home/Glossary/Performance/Server Response Time

Server Response Time

December 3, 2022 Updated November 16, 2026 2 min read

Performance glossaryServer response time is how long a server spends handling a request before it starts sending the response. It is the server's share of Time to First Byte (TTFB).

Server response time is the time a server spends handling a request before it starts sending the answer back. For a WordPress page, that covers PHP starting up, WordPress loading its core, theme, and plugins, the database queries, and building the HTML. It is the server's share of Time to First Byte (TTFB), which also includes the network time to reach the server and come back.

Because nothing can appear until the HTML starts arriving, a slow server delays every later milestone, including First Contentful Paint and Largest Contentful Paint.

How to measure it

  • PageSpeed Insights and Lighthouse report how long the server took to respond to the main document, and flag it in the "Document request latency" insight when it takes longer than 600 milliseconds.
  • Chrome DevTools: in the Network panel, select the HTML document and open the Timing tab. "Waiting for server response" is roughly the server's time plus one network round trip.
  • Server-Timing headers and application performance monitoring show how the time splits between PHP, database queries, and external calls.
  • Query Monitor, a free WordPress plugin, shows slow database queries, hooks, and HTTP calls for any page viewed while logged in.

Test both a cached page, as a logged-out visitor, and an uncached one, such as a page viewed while logged in. The cached number shows what most visitors get; the uncached number shows how hard WordPress is working.

Common causes of slow responses in WordPress

  • No page caching, so every visit builds the page from scratch.
  • Slow or repeated database queries, often from plugins, large tables without suitable indexes, or bloated autoloaded options.
  • External API calls made while the page is built, such as social feeds, exchange rates, or license checks.
  • An outdated PHP version. WordPress recommends PHP 8.3 or newer, and newer versions generally run the same code faster.
  • Underpowered or overcrowded hosting, or too few PHP workers for the traffic.
  • Heavy WP-Cron jobs triggered by visitor requests.

How to improve it

  1. Turn on full-page caching, at the server or with a plugin. For cached pages, this alone usually brings the response close to the network time.
  2. Add a persistent object cache (Redis or Memcached) to speed up pages that cannot be fully cached, such as carts and member areas.
  3. Use Query Monitor or APM to find the slowest plugin or query, then fix, replace, or remove it.
  4. Upgrade PHP and make sure OPcache is enabled.
  5. Run WP-Cron from a real server cron job instead of on page loads.
  6. Move to better hosting if the server itself is the limit.

A CDN shortens the distance to visitors and can cache HTML at the edge, but it cannot make uncached WordPress pages build any faster.

WP Services

WordPress services at revolutionary pricing.

Productized WordPress services, from builds to care, delivered by Seahawk and tracked in one app. For the WordPress lovers.