Slow server response time: finding what makes WordPress slow to respond

Why it matters

Everything waits for the server's first response: the HTML, then the CSS, images and scripts it references. The time until the first byte arrives is called time to first byte, and a slow one pushes back Largest Contentful Paint and everything visitors see. Google's web.dev guidance treats a TTFB of 0.8 seconds or less as good.

A slow server also limits how fast Google can crawl. If responses are slow or time out, Googlebot backs off and crawls fewer pages, which matters on large sites.

Note that this audit's timing covers fetching and loading the page, so it can include more than server time. Measure TTFB on its own to see how much is the server.

Common WordPress causes

• No page caching. Without it, WordPress runs PHP and database queries for every visit. A cached page is served as ready-made HTML in a fraction of the time.
• Heavy or badly written plugins. Plugins that run slow queries on every page, call external APIs while the page renders, or load large amounts of autoloaded options.
• Underpowered or overloaded hosting. Cheap shared hosting, a site that has outgrown its plan, or a server far from your visitors.
• Old PHP versions. Newer PHP versions are substantially faster than old ones.
• Uncacheable pages. Logged-in views, carts and checkout pages in WooCommerce, or pages that vary by cookie, always run uncached.
• A bloated database. Years of revisions, expired transients and leftover plugin tables slow queries down.

How to fix it in WordPress

1. Measure first. In your browser's developer tools Network tab, click the page request and look at the waiting time (TTFB). Test a few times, logged out, since logged-in requests bypass most caches.
2. Turn on full-page caching. Many hosts include it; otherwise use a caching plugin. Cached TTFB should be well under a second.
3. Find slow code. The Query Monitor plugin shows slow database queries, HTTP API calls and which plugin made them. Deactivate suspects one at a time on a staging copy.
4. Update PHP to a currently supported version through your host's control panel, after checking plugin compatibility on staging.
5. Add object caching (Redis or Memcached) if your host offers it; it speeds up uncached pages and wp-admin.
6. Use a CDN for static files and, if your setup allows, for cached HTML, so responses come from near the visitor.
7. Upgrade hosting if a clean, cached site is still slow.

Hydrogen SEO adds no front-end JavaScript, so it does not add to front-end load. The Performance area of its site health score flags host-level issues such as missing compression.

How to check the fix

Rerun the same TTFB measurement from a logged-out browser, several times, and compare. PageSpeed Insights shows lab timings plus real-user data from Chrome when your site has enough traffic, which is the better long-term measure. Rerun the free SEO audit to compare the response time it records.