Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
High WordPress TTFB is usually an origin-response problem: the browser is waiting for a server, PHP, database, cache, or upstream service to begin sending HTML. Measure cache hits and misses first, then enable correctly purged full-page caching, configure CDN HTML caching where appropriate, add persistent object caching for database-heavy requests, profile slow code and queries, and only then reassess hosting capacity.
Image compression, JavaScript deferral, and other front-end optimizations can improve later rendering stages, but they cannot make a slow WordPress origin send its first byte sooner.
What TTFB measures in WordPress
Time to first byte (TTFB) is the elapsed time between a browser starting an HTTP request and receiving the first byte of the response. For a normal WordPress page, that interval can include DNS and connection setup, the trip to the server or CDN edge, web-server handling, PHP execution, database queries, plugin and theme hooks, external API calls, and the time required to retrieve or generate the page.
TTFB is a server-response measure, not a complete page-speed score. Once the first byte arrives, the browser still has to download the rest of the HTML, discover stylesheets and scripts, render the page, and load images. Compressing images or deferring JavaScript addresses those later phases. It does not fix PHP that spends 1.5 seconds building the response.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
WordPress identifies several contributors to response time:
- Network infrastructure and the physical distance between visitor and origin.
- Server hardware, CPU contention, memory pressure, PHP worker limits, and web-server configuration.
- Database operations, including repeated option and metadata lookups.
- PHP processing in WordPress core, themes, plugins, and custom code.
- Synchronous calls to payment, search, analytics, shipping, identity, or other external APIs.
- Whether a request is served from a full-page cache, an object cache, a CDN edge, or the origin stack.
The correct fix depends on which of those paths handled the request. A cache hit, an uncached anonymous page, and a logged-in dashboard request are different performance cases.
Measure before changing settings
Do not infer TTFB from a synthetic performance grade alone. Establish a repeatable baseline for the same URL, from representative visitor regions, and for both cached and uncached conditions.
Build a useful baseline
- Select representative URLs. Test the home page, a typical article or product page, a search or archive page, and one known dynamic route. Include the regions that generate most of your traffic; an origin in one continent can behave very differently for visitors on another.
- Record a normal anonymous request. Use a private browser session or an equivalent request without administrator cookies. Save the measured TTFB, total response time, status code, redirect chain, and response headers.
- Record a cache-busting request. Add a harmless, unique query string only if your cache rules treat it as a miss, or use the testing method supplied by your host. Label this result clearly as an origin or cache-miss measurement. Do not compare it directly with a cache hit as though they were the same workload.
- Repeat each test. Run several requests at each location and use the median rather than a single outlier. Note the time of day and whether traffic was unusually high.
- Inspect server timing and headers. Look for cache-status headers, age values, purge markers, redirects, and timing fields exposed by the web server, reverse proxy, or CDN. A response that says “miss” is evidence that the request reached a slower path.
- Separate connection setup from application time. Some tools include DNS lookup, TCP or QUIC connection, and TLS negotiation in their displayed timing. Record those components separately when available so that you do not tune PHP for a problem caused by routing or connection establishment.
Keep the baseline and rerun the same URLs after every material change. A better overall page score does not prove that TTFB improved; measure the response phase directly.
Find out whether the delay is at the edge or origin
A CDN edge can respond quickly when it has a fresh HTML object. If the edge has no HTML copy, it still waits for the origin and then forwards the response. An edge miss therefore carries the origin round trip plus any PHP and database work.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
Signals of an edge or full-page cache hit
- A cache-status header identifies a hit, or an age header increases between requests.
- The first request is slower and subsequent anonymous requests from the same location are substantially faster.
- Origin access logs show no PHP application request for the hit.
- Response headers remain consistent after a page is revisited without cookies.
Signals of an origin bottleneck
- Cache-busting requests and cache misses have high TTFB even when the visitor is near the origin.
- Every request is marked as a miss, bypass, or pass-through because HTML is not cached.
- Server CPU, PHP workers, database connections, or I/O are saturated while slow requests arrive.
- Dynamic routes remain slow after static assets are served from an edge.
Check more than one geography. A nearby edge hit can hide a distant-origin problem, while a miss in a region without an edge connection exposes the true origin latency.
Recommended Free Tools
Enable and verify full-page caching first
For anonymous pages, full-page caching is normally the highest-impact intervention. The cache stores the generated HTML and serves it without running Apache or another web server, PHP, WordPress, and the database for every request. A WordPress caching plugin can create static files, while a reverse proxy such as Varnish can serve a prebuilt response in front of the application.
Choose the cache layer
Use the reverse-proxy or managed cache supplied by your host when it is available and documented. Otherwise use one reputable full-page-cache plugin that integrates with the web server or CDN. Avoid stacking several plugins that each rewrite page-cache, compression, minification, or purge rules; overlapping layers make it difficult to know which cache served a response.
Set safe cache exclusions
Do not cache responses whose HTML varies by user, session, cart, or permission. Typical exclusions include:
- Cart, checkout, payment, and order-confirmation pages.
- Account, login, registration, password-reset, and profile pages.
- WordPress administration screens and preview URLs.
- Membership, subscription, or personalized dashboards.
- Any route that sets a session cookie or embeds user-specific data.
Some sites can cache a public shell and load personalized fragments separately. That design requires careful fragment-cache rules; otherwise a user-specific name, balance, or cart count can be frozen and shown to another visitor.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Verify that a hit bypasses PHP
- Publish a test page and request it anonymously twice from the same location.
- Inspect the first and second responses for cache status and age headers.
- Compare TTFB for the second request with the cache-busting baseline.
- Check origin logs or application metrics to confirm that the hit did not start a PHP request.
- Log in and confirm that the page follows the intended bypass rule rather than displaying an anonymous cached copy.
Test purge behavior before relying on the cache
When an article, menu, widget, product, or taxonomy term changes, the relevant cached objects must be purged. Test publishing, updating, deleting, and changing a navigation item. Verify that the changed content appears for an anonymous visitor without manually clearing every cache. Coordinated purge behavior matters as much as hit speed: a fast stale page is still incorrect.
Configure a CDN for the actual TTFB problem
A CDN lowers geographic latency when it can answer from an edge near the visitor. It does not automatically lower WordPress TTFB merely by caching CSS, JavaScript, and images. If HTML is forwarded to the origin on every request, the expensive server path remains.
When edge HTML caching is appropriate
Edge-cache anonymous HTML when the page is identical for a broad audience and your business rules permit it. News articles, documentation, marketing pages, and public archives often fit. Logged-in dashboards, carts, checkout flows, and pages with location- or account-specific content generally require bypasses or carefully designed fragments.
CDN checks that affect TTFB
- HTML cache coverage: confirm that the CDN stores and serves the document response, not only static assets.
- Hit status: inspect the CDN’s hit, miss, bypass, and stale indicators for the exact URL.
- Cookie rules: ensure that an unnecessary WordPress or analytics cookie is not forcing every request to bypass HTML caching.
- Query-string policy: decide which parameters identify a distinct page and which should be ignored for cache keys.
- Purge propagation: update content and verify that all relevant edges receive the purge.
- Origin shield and revalidation: reduce duplicate fetches when many edges request the same uncached object at once.
- Geographic behavior: test an edge hit and an edge miss from the regions that matter to your audience.
Do not promise a fixed millisecond reduction. The benefit depends on hit rate, edge placement, object freshness, origin distance, and the portion of traffic that can be cached.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Add persistent object caching for database-heavy requests
Full-page caching avoids most application work for anonymous hits, but dynamic requests and cache misses still execute WordPress. Persistent object caching keeps frequently used database results, such as options and metadata, between requests. A service commonly backed by Redis or a comparable cache server can reduce repeated database trips.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
WordPress documentation notes that extra database trips slow server response times such as TTFB and can overwhelm a database during traffic spikes. Persistent object caching addresses repeated reads; it does not replace full-page caching for public HTML.
Implement it safely
- Ask the host which persistent object-cache service and WordPress integration it supports.
- Enable the service in staging first and confirm that the extension, credentials, network policy, and memory allocation are correct.
- Install or activate one object-cache integration, not several competing drop-ins.
- Check hit rate, miss rate, evictions, memory use, connection errors, and key expiration behavior.
- Exercise logins, content updates, search, and any custom data writes; verify that updates invalidate or replace stale objects.
- Repeat the dynamic-route TTFB tests and compare database query counts and time.
Low hit rates, constant evictions, or connection failures mean the object cache is not providing a reliable benefit. Increasing cache size without understanding key churn can hide an application problem rather than solve it.
Profile PHP, plugins, themes, and external calls
After cache layers are correct, investigate requests that must run PHP. Profile a cache miss and a representative dynamic route in staging or during a controlled maintenance window.
Look for slow hooks and plugin work
Application profiling can identify actions and filters that consume disproportionate time. Common causes include rebuilding large lists on every request, scanning files, generating remote previews, loading extensive administrative code on the front end, or running analytics and marketing integrations synchronously. Disable a confirmed offender in staging, retest the identical URL, and then replace or reconfigure it if the improvement is repeatable.
Inspect database queries and autoloaded options
Record query count, total query time, duplicate queries, missing indexes, and queries that return far more rows than the page needs. WordPress core performance work has specifically addressed slow database responses and very large autoloaded options. Review the options table for obsolete settings and oversized values that load on every request. Remove data only after identifying the owning plugin and confirming that it is no longer required; deleting an active plugin’s settings can break a site.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Control synchronous third-party requests
A remote API call in the request path adds the provider’s network and processing time to your TTFB. Set strict timeouts, cache responses when freshness permits, and move nonessential work to a background job or scheduled task. A failed endpoint should degrade gracefully instead of holding every page open until a long socket timeout expires.
Check theme and custom-code behavior
Review expensive template loops, repeated calls for the same object, uncached remote lookups, and queries inside loops. Fetch only the fields needed for the response, reuse values within a request, and avoid rebuilding menus or recommendation sets separately for each component.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsImprove the origin when uncached PHP is still slow
If profiling shows that application work is reasonable but the origin remains slow, inspect capacity and placement rather than adding more front-end optimization.
- CPU allocation: sustained contention increases PHP execution and database wait time.
- PHP workers: too few workers create a queue even when each individual request is fast. Too many can exhaust memory and make the database less stable.
- OPcache: ensure PHP bytecode caching is enabled, has adequate memory, and is not constantly invalidating files.
- Database resources: check CPU, memory, storage latency, connection limits, slow-query logs, and buffer allocation.
- Web-server queueing: examine upstream wait time, keep-alive behavior, and worker saturation.
- Geographic placement: move the origin closer to the main audience or use edge HTML caching when moving it is impractical.
Moving from constrained shared hosting can reduce origin time, but validate the result with repeatable cache-miss tests. A provider’s generic benchmark does not represent your theme, plugins, database, traffic pattern, or geographic mix.
A practical end-to-end fix sequence
Use this order to avoid masking one bottleneck with another:
- Measure. Capture median TTFB for normal anonymous, cache-busting, dynamic, and representative regional requests.
- Map the request path. Determine whether each result came from a CDN edge, reverse proxy, page cache, PHP, or a redirect.
- Enable full-page caching. Cache public HTML, exclude personalized routes, and verify that hits bypass PHP.
- Test purge correctness. Publish and update content, then confirm fresh anonymous responses at the edge and origin.
- Configure CDN HTML caching. Add edge caching only where content variation and cookie rules allow it; verify hit status by geography.
- Add persistent object caching. Use the host-supported service for database-heavy dynamic requests and monitor hit rate and evictions.
- Profile misses and dynamic routes. Fix slow hooks, queries, autoloaded options, and synchronous remote calls one at a time.
- Reassess hosting capacity. Compare CPU, PHP workers, OPcache, database resources, and origin location using the same tests.
- Document bypasses and ownership. Record which layer owns HTML caching, object caching, compression, redirects, and purge calls so future changes do not create conflicting rules.
How to interpret common symptoms
| Symptom | Likely cause | Next check |
|---|---|---|
| Anonymous repeat requests are fast, but first visits are slow | Low edge or page-cache hit rate, or expensive origin generation | Inspect hit/miss headers, cache TTL, purge frequency, and cache-miss TTFB. |
| Every HTML request is a CDN miss | HTML caching is disabled, bypassed by cookies, or excluded by rules | Review document caching, cookie bypasses, query-string keys, and route exclusions. |
| Static assets are fast but HTML is slow | CDN is serving assets while forwarding documents to WordPress | Enable eligible edge HTML caching or optimize the origin path. |
| Logged-in pages remain slow after public pages improve | Personalized requests bypass full-page cache | Profile PHP, database queries, object-cache hit rate, and external calls on the dynamic route. |
| Content remains stale after publishing | Purge does not reach one or more cache layers | Trace purge events from WordPress to reverse proxy and each CDN region. |
| TTFB rises during traffic spikes | PHP workers, database connections, CPU, or memory are saturated | Correlate request queues with resource graphs and slow-query logs. |
| Only one region reports high TTFB | Origin distance, routing, or an edge miss in that geography | Compare edge status and connection timing by region. |
| Object-cache hit rate is low | Short expirations, frequent evictions, poor key reuse, or an integration problem | Check memory limits, eviction counters, key lifetime, and connection errors. |
Compare solutions by behavior, not labels
When evaluating a host, CDN, cache plugin, reverse proxy, or object-cache service, compare the properties that determine your request path:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
| Decision area | Questions to answer |
|---|---|
| Cache coverage | Can it cache complete HTML, or only CSS, JavaScript, and images? Which routes are excluded? |
| Hit and purge correctness | How are hits exposed? How quickly do publishes, updates, and deletes purge every layer? |
| Personalization | How are login cookies, carts, previews, and user-specific fragments bypassed? |
| Geographic reach | Where are edge locations, and what happens on a miss in each major visitor region? |
| Origin capacity | What CPU, memory, PHP worker, OPcache, and database resources are actually allocated? |
| Object caching | Is a persistent object cache supported, and can you monitor hit rate, memory, and evictions? |
| Compatibility | Does it work with your WordPress version, web server, ecommerce or membership flows, and deployment process? |
| Operating cost | Include recurring cache, CDN, hosting, monitoring, and support costs rather than comparing a single advertised tier. |
What not to do
- Do not treat a lower largest-contentful-paint score as proof that TTFB improved.
- Do not install several optimization plugins with overlapping page-cache and purge functions.
- Do not cache carts, account pages, previews, or user-specific markup simply to raise the hit rate.
- Do not purge every layer manually as a permanent publishing workflow; fix the invalidation path.
- Do not add Redis or another object cache as a substitute for diagnosing a slow query or an uncached public page.
- Do not disable a plugin in production without checking its data ownership, scheduled jobs, and integrations.
- Do not accept a provider’s benchmark as evidence for your site without repeatable measurements from your important regions.
- Do not promise a universal TTFB threshold or a fixed millisecond gain. The WordPress 6.6 performance-improvements work reported a 10 ms, or 14%, median TTFB decline in its own 2024 testing; that result is a core test finding, not a guarantee for an individual installation.
Final verification checklist
- Normal anonymous requests show a documented cache-hit status where intended.
- Cache misses and dynamic routes have separate baselines and owners.
- HTML caching excludes every personalized or state-changing route.
- Publishing and updating content purge the correct page, archive, and edge objects.
- CDN tests cover the main visitor regions, including an edge miss.
- Persistent object-cache hit rate, memory, evictions, and errors are monitored.
- Slow PHP hooks, queries, autoloaded options, and remote calls have been measured before being changed.
- CPU, PHP workers, OPcache, database resources, and queueing remain below saturation under representative traffic.
- Post-change tests use the same URLs, regions, cookies, and cache state as the baseline.
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.
