What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
To reduce WordPress TTFB, first find out which requests are slow and whether they are cache hits or misses. For public pages, verify full-page caching before changing hosting; for dynamic requests, investigate database work, PHP execution, plugins, and server capacity. A CDN or higher hosting plan helps only when it addresses the slow part of the request path.
What WordPress TTFB measures—and what it does not
Time to first byte (TTFB) is the elapsed time until a browser receives the first byte of a response. It is not simply a PHP execution timer: connection and network delays, edge or proxy behavior, and origin-server work can all affect the measurement. A low displayed TTFB can also be misleading when Early Hints are involved; Google’s TTFB guidance cautions that Early Hints can make the displayed metric look faster without speeding the underlying server work.
Use field data to understand what real visitors experience, then use a lab test or server-side timing to investigate a specific request. Compare the same URL under equivalent conditions: a cache hit is not comparable to a cache miss, and an anonymous page is not comparable to a logged-in request. Record the test location, time, request type, and cache status so that a change can be judged against a meaningful baseline.
How to test WordPress server response time
- Choose representative URLs. Test a public article, a page with dynamic widgets, and—if your site has accounts or commerce—a logged-in or shopping flow.
- Repeat the same requests. Keep the URL, visitor state, and test location consistent. Repeat measurements rather than treating one unusually fast or slow request as representative.
- Inspect the browser request. Use browser developer tools or a performance service to review the request waterfall and the browser-side TTFB.
- Check server and cache signals. Where available, inspect
Server-Timing, hosting telemetry, and cache-status headers or logs. Confirm whether each response was served from a page cache, CDN edge, or origin. - Compare field and lab results. Field data describes visitor experience across real conditions; a controlled lab trace helps investigate a particular request path. Google recommends using both to understand performance and diagnose causes.
Keep separate records for public cache hits, public cache misses, and personalized requests. That distinction helps show whether the main opportunity is to serve more public pages from cache or to make dynamic generation less expensive.
Recommended Free Tools
#1 Best Overall
Check full-page caching first for public pages
A full-page cache can serve a previously generated HTML response without repeating WordPress, PHP, and database work for every anonymous visit. WordPress’s Optimization handbook and Cache handbook describe caching as a way to reduce repeated processing. Depending on the setup, a plugin, host, reverse proxy, or server-level cache may provide the page cache.
Do not assume a cache plugin is working just because it is installed. Test an anonymous request and confirm that the intended public URL is actually a cache hit. Check both the first request after a purge and a subsequent request, since they follow different paths. Also verify that publishing or updating content clears the relevant cached pages rather than leaving stale HTML visible.
Set cache lifetime and invalidation to match how often content changes. Prefer selective purges when possible, rather than flushing every cached page for a small update. Shared full-page caching must not serve one visitor’s private or personalized content to another: keep cart, checkout, and profile pages dynamic, and generally exclude logged-in users when their content varies by account.
Use object caching for repeated database work
Persistent object caching is useful when requests still need to run WordPress but repeatedly retrieve the same database-backed data. WordPress explains that avoiding repeat database trips can improve response times, including TTFB, and help under traffic spikes. The Optimization handbook notes that extra database trips can slow server response and overwhelm a database during load.
Object caching is not a substitute for full-page caching: it can reduce repeated work during dynamic or authenticated requests, but WordPress still has to generate the response. Use it when measurements or query behavior point to repeated database retrieval as a bottleneck—not solely because Redis is popular. WordPress lists Redis, Memcached, APC, and filesystem caching as possible engines; the appropriate choice depends on the application and whether the cache is faster than regenerating the data. Your host must provide or support a cache server and compatible integration.
Make sure PHP OPcache is enabled and correctly managed
OPcache stores compiled PHP bytecode so PHP does not need to repeatedly read and compile the same scripts. It addresses PHP compilation work, not page delivery or repeated database queries, and is especially relevant for dynamic or authenticated traffic that cannot benefit fully from a full-page cache. WordPress’s Cache handbook and AWS’s WordPress caching guidance describe opcode caching as a performance measure.
Rank #3
Ask your host or inspect the PHP configuration to verify OPcache is active for web requests and has adequate capacity. Deployment handling matters: if timestamp validation is disabled or code deployments do not invalidate the cache, visitors may receive old compiled scripts. Ensure the deployment process purges or restarts OPcache when required. Do not copy a sample configuration without checking how your host manages PHP.
AWS reported average TTFB of 759 ms without OPcache and 22 ms with OPcache in one specific WordPress homepage deployment using files on Amazon EFS; the post says it ran 250 samples per test. Those results demonstrate that setup only and are not a general benchmark or promised improvement for other WordPress sites. See the AWS test description for its context.
Free tools Windows power users keep installed
One-click scans. No signup required.
Find expensive plugins and application work
Plugin count by itself does not establish why a site is slow. WordPress recommends removing unnecessary plugins and selectively disabling plugins to measure whether one has a significant impact. Do that on staging or during a controlled maintenance window where possible; disabling functionality on a live store or membership site can disrupt visitors. If testing identifies a costly plugin, review its settings and documentation, ask its support team, or consider an alternative that provides the required features.
For slow dynamic requests, investigate slow database queries, external service calls, expensive page generation, and resource pressure. Avoid adding layers of caching until you understand what data may safely be reused and how fresh or personalized it must remain. If the cause is still unclear, request request-level timing from your host or developer rather than guessing.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Use a CDN only when it improves the path being measured
A CDN can serve static files near visitors and may cache eligible HTML at the edge. WordPress recommends pairing a CDN with a WordPress caching strategy in its Optimization handbook. AWS describes CloudFront as routing requests to an appropriate edge location and immediately delivering content already cached there in its CloudFront introduction.
Check whether the slow URL is an edge-cache hit or an origin fetch, and test from locations relevant to your visitors. A CDN without full-page edge caching may still need to fetch HTML from the origin before responding, potentially adding latency rather than reducing it. Keep private or personalized content out of shared edge caches, and verify purge behavior when content changes.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Best Value
- Offer contains ONLY 2 titles regardless of the order quantity placed for this listing. Set of volumes may vary. Ordering in multiples will not change the volume received. Image is meant to display the type of book you will be receiving only.
- BRAIN TEASING. Perfect Puzzle Book for all ages to learn. Enjoy puzzles, maze, word search, or crosswords! This puzzle book is ideal for people on the go and will provide hours of entertainment.
- FUN & CHALLENGING. Exercise your brains long-term memory, working memory, executive functioning, attention to detail, multitasking, and processing speed. Perfect gifting item for those who love word search puzzles!
- RELAX, RECHARGE, & REFOCUS. The word find puzzle book offers an enjoyable challenge for all, from beginners to experts. Ideal for learning, practicing, and having fun time for various users.
- OFFICIALLY LICENSED. High-resolution printing. Perfect for family activities, classroom learning, or travel. Provide an engaging, educational experience with every page, making it both fun and meaningful.
When a hosting change is justified
Review hosting capacity after you have checked caching and application behavior, especially if uncached requests remain slow and telemetry indicates CPU, memory, storage, processing, or server-configuration constraints. WordPress lists these as performance considerations in its Optimization handbook. AWS likewise advises sizing a server for the workload and notes that plugins, themes, and databases affect resource needs in its WordPress on AWS guidance.
A larger plan can provide needed resources, but it will not automatically fix an inefficient query, an uncacheable page, or a slow external call. The right choice depends on traffic, site features, workload, visitor geography, cacheability, and the hosting stack. There is no universal TTFB target or guaranteed improvement from moving hosts.
Choose the layer that matches the slow request
| Option | Work it can skip or reduce | Best fit | Key checks |
|---|---|---|---|
| Full-page cache | Repeated WordPress, PHP, and database work for a cached HTML response | Public pages that do not vary by visitor | Confirm hit status, purge behavior, freshness, and exclusions for personalized pages. |
| Persistent object cache | Repeated retrieval of cached objects or data from the database | Dynamic or authenticated requests with repeated database work | Confirm host support, integration, cache behavior, and that reuse is safe and useful. |
| PHP OPcache | Repeated PHP file reading and compilation | PHP-generated requests, especially where full-page caching is less effective | Verify it is active for web requests, sized adequately, and invalidated correctly at deployment. |
| CDN or edge cache | Distance to cached content; with eligible HTML edge caching, some origin work | Visitors far from the origin and content that can be safely cached | Measure edge hits versus origin fetches by location; verify cache rules and purges. |
| Hosting adjustment | Resource or configuration constraints, if those are the measured bottleneck | Slow uncached requests with evidence of insufficient capacity or unsuitable configuration | Review telemetry and workload; a plan upgrade alone does not fix application bottlenecks. |
Judge changes on the same URLs and request conditions used for the baseline. Track cache-hit rate and miss behavior separately; an improvement to anonymous page delivery can coexist with slow logged-in requests.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
