Time to First Byte — how long the browser waits before your server sends the first chunk of a page — sets the ceiling for how fast your WordPress site can possibly feel. A slow TTFB drags down every other metric. Here’s how to fix it for real.
What TTFB Actually Measures
TTFB is the gap between a request leaving the browser and the first byte of the response arriving. It covers DNS lookup, connection setup, and crucially, the time your server spends building the page. On WordPress, that build time is usually where the problem lives.
The Biggest Culprits
Slow Server Response
Cheap shared hosting is the most common cause of poor TTFB. When dozens of sites share resources, your page generation waits in line. Upgrading to quality managed WordPress hosting often cuts TTFB dramatically with no other changes.
Uncached Page Generation
Without caching, WordPress rebuilds every page from scratch on each request — running PHP, querying the database, assembling output. A good caching layer serves a pre-built page instantly, slashing TTFB.
Fixes That Move the Needle
- Enable full-page caching — serve static HTML instead of regenerating pages.
- Add object caching — cache database query results so repeated queries are instant.
- Use a CDN — serve cached pages from a location near the visitor.
- Upgrade PHP — newer PHP versions are significantly faster.
Optimize the Database
A bloated database slows every page build. Clean out post revisions, expired transients, and spam, and add indexes where queries are slow. On large sites, a single inefficient query in a theme or plugin can wreck TTFB — profile your queries to find the offender.
Trim Heavy Plugins
Every plugin that runs on the front end adds to page-build time. Audit your plugins, deactivate what you don’t need, and replace heavy ones with lighter alternatives. Sometimes removing a single poorly built plugin transforms your TTFB.
Measure and Verify
Use a performance tool to measure TTFB before and after each change so you know what actually helped. Aim to keep TTFB well under half a second; under 200 milliseconds is excellent. Test from the regions where your real visitors are.
Final Thoughts
Reducing WordPress TTFB comes down to fast hosting, aggressive caching, a lean database, and trimmed plugins. Tackle hosting and caching first for the biggest wins, then refine from there. Lower your TTFB and every visitor feels the difference instantly.
Key Takeaways
- Focus on fundamentals over trends — consistency beats novelty.
- Measure before and after every change so you know what worked.
- Make focused, one-at-a-time improvements you can verify and reverse.
- Turn your process into a repeatable checklist for every project.
Frequently Asked Questions
What is a good TTFB for WordPress?
Aim for well under half a second; under 200 milliseconds is excellent. High TTFB usually points to slow hosting or missing caching.
Does caching reduce TTFB?
Significantly. Full-page caching serves pre-built HTML instead of regenerating pages on every request, which is often the single biggest TTFB improvement.
Can hosting affect TTFB?
Absolutely. Cheap shared hosting is the most common cause of slow TTFB. Quality managed WordPress hosting often cuts it dramatically on its own.