Why it shows up in your week
Image audits look green. The page still feels empty for seconds on first load from another country. The HTML itself was late. That wait is TTFB.
In plain language
A CDN or edge cache often cuts TTFB for anonymous page views. Logged-in or highly personalised HTML may still hit the origin.
WordPress TTFB problems often come from uncached dynamic pages, heavy plugins on every request, or hosting far from buyers.
Redirect chains (HTTP→HTTPS→www→page) add round trips before the first byte of real content.
Measure from regions your buyers use, not only from your office.
Fixing TTFB does not replace image and script work. It unblocks them.
Facts worth keeping
- Measures
- Time until first byte of the document response
- Not a CWV
- Influences LCP; LCP/INP/CLS are the Core Web Vitals
- Common fixes
- Edge cache, closer hosting, fewer redirects, leaner origin PHP
- WordPress angle
- Uncached dynamic pages and heavy plugins on every request
- Measure where
- Buyer regions and mobile networks, not only lab localhost
Not the same as
- LCPLCP includes rendering the main content. TTFB is only until the first byte arrives.
- API latencySimilar idea for XHR/fetch calls. Document TTFB is about the HTML request.
- DNS-only timeDNS is one part of TTFB. Connection, TLS, and server work also count.
Where it bites
TTFB hurts when a site looks optimised in image audits but still feels empty for seconds on first load, especially on mobile networks far from the origin.
Campaign traffic from another city exposes hosting and cache choices the office Wi-Fi never revealed.
What to check
- What is document TTFB on key templates from real user regions?
- Are cacheable pages actually hitting the edge?
- Which plugins or queries run on every uncached request?
- How many redirects happen before the final HTML?
- Is hosting geographically sane for your buyers?
Common questions
What is TTFB?
Time to First Byte is the time until the browser receives the first byte of the document response after starting the request.
Is TTFB a Core Web Vital?
No. LCP, INP, and CLS are the Core Web Vitals. TTFB still matters because slow document responses delay LCP.
What should you fix first for TTFB?
Check edge caching for anonymous pages, hosting region, TLS and redirects, and origin work that runs before HTML is sent.
Why is WordPress TTFB sometimes high?
Uncached dynamic pages, heavy plugins, slow DB queries, and distant hosting are common causes.
Does a CDN always fix TTFB?
For cacheable anonymous HTML, often yes. Personalised or cart pages may still need origin performance work.