Your server response time is slow, and TTFB is high. Pages take seconds to start loading, and Core Web Vitals suffer. This is one of the most impactful performance issues. This guide explains why server response time is slow and how to fix it.
What server response time is
Server response time (TTFB) is the time between a request and the first byte of the response. It includes:
— network latency;
— server processing;
— database queries;
— application logic;
— caching.
High TTFB delays everything else. Even fast pages feel slow if TTFB is high.
Why TTFB matters
TTFB affects:
— LCP (Largest Contentful Paint);
— perceived speed;
— Core Web Vitals;
— rankings.
If TTFB is high, other optimizations have less impact.
Reason 1: slow database queries
The most common cause. Slow queries delay page generation.
What to check:
— slow query log;
— missing indexes;
— complex joins;
— large tables.
The fix: optimize queries, add indexes, cache results.
Use TTFB checker to measure response time.
Reason 2: no caching
Without caching, every request regenerates the page. This is slow.
What to check:
— is page caching enabled;
— is object caching enabled;
— is CDN used.
The fix: enable page and object caching. Use CDN for static and dynamic content.
Reason 3: slow PHP or application
Slow application code, heavy plugins or inefficient logic delay response.
What to check:
— PHP version;
— plugins and modules;
— application logs.
The fix: update PHP, remove unnecessary plugins, optimize code.
Reason 4: insufficient hosting resources
Limited CPU, RAM or disk I/O slows the server.
What to check:
— CPU usage;
— memory usage;
— disk I/O;
— hosting plan.
The fix: upgrade hosting, optimize resources, use a faster server.
Reason 5: network latency
If the server is far from users, network latency increases TTFB.
What to check:
— server location;
— CDN usage;
— DNS resolution.
The fix: use a CDN, choose a server closer to users, optimize DNS.
How to diagnose slow TTFB
A practical sequence:
— measure TTFB;
— check database queries;
— check caching;
— check application code;
— check hosting resources;
— check network latency.
If TTFB is high, fix the biggest contributor first. For a broader audit, SEO audit can help verify TTFB, caching and performance in one place.
How to fix slow TTFB
Fix steps:
— optimize database queries;
— enable caching;
— update PHP and plugins;
— upgrade hosting if needed;
— use CDN;
— test after changes.
FAQ
Why is server response time slow?
Most often because of slow database queries, no caching, slow application code, limited hosting resources or network latency.
What is a good TTFB?
Under 200 ms is good. 200–500 ms needs improvement. Above 500 ms is slow.
Does TTFB affect SEO?
Yes. TTFB affects Core Web Vitals, which are ranking factors.
Can caching improve TTFB?
Yes. Page and object caching reduce server processing and improve TTFB.
Can CDN reduce TTFB?
Yes. CDN serves content from locations closer to users, reducing latency.
What if TTFB is high only for some pages?
Check those pages for slow queries, heavy plugins or uncached content.
Does hosting affect TTFB?
Yes. Limited resources or slow servers increase TTFB. Upgrade hosting if needed.
How do I measure TTFB?
Use a TTFB checker or browser DevTools. Measure from different locations.
Can database queries cause slow TTFB?
Yes. Slow queries are a common cause. Optimize queries and add indexes.
How often should I check TTFB?
After changes and periodically as part of a performance audit.
