Free tools Windows power users keep installed
One-click scans. No signup required.
WordPress speed is a systems result, not a property of a single plugin or host. Hosting hardware and load, network distance, cache state, PHP and WordPress versions, theme and plugin code, database work, external services, and the number and size of media files all change what a visitor experiences. A defensible benchmark holds those variables constant, measures both server response and Core Web Vitals, and repeats the test under documented cache and geography conditions.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What a WordPress speed benchmark should tell you
A useful benchmark answers two different questions:
As an Amazon Associate I earn from qualifying purchases.
- How quickly does the origin respond? Time to First Byte (TTFB) shows the time before the browser receives the first response bytes. It is strongly influenced by server processing, database queries, PHP execution, network distance and whether a cache can answer the request.
- How quickly does the page become usable and stable? Core Web Vitals describe the visitor-facing result: Largest Contentful Paint (LCP), Interaction to Next Paint (INP) and Cumulative Layout Shift (CLS).
Report both. A low TTFB does not guarantee a fast page if render-blocking scripts delay LCP or interaction code produces a poor INP. Conversely, a cached page can show excellent delivery while the uncached origin remains overloaded and slow to regenerate.
There is no universal industry-wide “average WordPress load time” established by the cited official WordPress material. A single synthetic score cannot identify a winner for every site because workload, visitor location, device, software configuration and cache state differ.
#1 Best Overall
The variables that move WordPress results
Hosting, hardware and shared-server contention
CPU capacity, memory, storage and server configuration determine how quickly the origin can run PHP, query the database and assemble a response. On a shared server, other accounts can consume the same resources, adding contention that appears as variable TTFB from run to run. Compare hosting configurations with the same page and software, and record whether the server is shared or isolated when that information is available.
Throughput under load matters as well as a single visitor’s latency. A page that looks quick in an idle test may queue requests when several uncached pages arrive together. Include a load or concurrency test only when you can keep the workload identical and report the conditions; do not treat a quiet, one-request result as proof of capacity.
Geographic distance and network paths
Physical distance between a visitor and the origin adds network latency. The same WordPress installation can therefore produce different TTFB and rendering results for readers in different regions. State the test location, network profile and device profile for every comparison.
A content delivery network (CDN) can serve static files from an edge location closer to the visitor. That can reduce the distance for images, style sheets, scripts and other cacheable assets, but it does not automatically eliminate origin work for a dynamic HTML response. Measure the CDN with a clearly stated cache state and from more than one geography when your audience is distributed.
Caching layers and invalidation
Caching changes how much work reaches WordPress and how often a request travels to the origin. Common layers include:
- Full-page or edge cache: stores an assembled HTML response so repeat visitors can be served without running the complete WordPress request.
- Static-file cache: keeps assets such as images, CSS and JavaScript ready for delivery.
- Opcode cache: keeps compiled PHP bytecode, reducing repeated compilation work.
- Object cache: stores reusable database results or objects, reducing repeated queries.
- Fragment cache: stores portions of a page when the entire response cannot be cached.
Test cold and warm states separately. A cold request includes regeneration work; a warm request shows the path most repeat visitors may receive. Cache invalidation is part of performance: publishing or expiring content can force regeneration, and an invalidation strategy that clears too broadly can create a burst of uncached requests.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesWordPress execution, database work and external services
WordPress core, the active theme and each plugin contribute PHP code, database queries and sometimes calls to outside services. Plugin count alone is not a valid benchmark. One plugin may do little work while another performs expensive queries, adds front-end scripts or waits on a remote API.
When TTFB is high, inspect the request path for slow database operations, PHP execution and external calls. Test a change to code or configuration in isolation, then repeat the same benchmark. A faster synthetic result is not enough if a feature no longer works or real users still wait on a third-party response.
Rank #3
Images and other media
Image count, dimensions, format and byte size affect transfer time and rendering. WordPress guidance recommends selecting an appropriate format and applying compression. Responsive source selection can prevent a small phone from downloading a desktop-sized image, while lazy loading can defer below-the-fold media that is not immediately needed.
Do not assume that fewer images always means a faster page. The relevant questions are which bytes are fetched for the tested viewport, which resource becomes the LCP element, and whether image decoding or layout changes delay the visible result.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Versions and server configuration
WordPress and PHP releases, database settings, object-cache availability and web-server configuration can change performance. Record the exact versions and settings in a benchmark log. Comparing one host on a newer PHP release with another on an older release measures a mixed configuration, not hosting alone.
Core Web Vitals and server metrics to record
| Metric or record | What it reveals | Why it belongs in a comparison |
|---|---|---|
| TTFB | Time until the first response bytes arrive from the server and network path | Separates origin or delivery delay from browser rendering work |
| LCP | When the largest visible content element finishes rendering | Shows whether the main content arrives promptly |
| INP | How quickly the page responds after user interaction | Exposes JavaScript or main-thread work that a load-only test misses |
| CLS | Unexpected movement of page content during loading | Captures layout stability, often affected by media dimensions and late UI insertion |
| Request count | How many network requests the page makes | Helps identify excess assets and connection overhead |
| Transfer size | Bytes downloaded for the tested page | Shows the payload a visitor’s connection must receive |
| Waterfall bottlenecks | Which requests block or delay later work | Connects a metric change to a specific resource or phase |
| Cache state | Whether the request was cold, warm or served from an edge cache | Prevents unlike delivery paths being presented as an apples-to-apples result |
WordPress 6.6 performance documentation describes Core Web Vitals and Server-Timing data collected from 100 runs. WordPress 6.7 release performance notes also report measurements from 100 runs. Those records illustrate the value of repeated measurements; they are not a universal score for every installation.
How to run a repeatable WordPress benchmark
- Freeze the test page. Choose one URL and keep its content, media, theme, plugin set and logged-in or logged-out state unchanged throughout the comparison. A page with a representative template is more useful than an empty test page.
- Record the software and server profile. Log WordPress and PHP versions, database settings, web-server configuration, object-cache availability, hosting hardware or plan characteristics and CDN settings.
- Define the visitor. Set the test geography, device profile and network conditions. If your audience spans regions, repeat the same test from each important location rather than averaging unlike paths into one number.
- Separate cache conditions. Run a cold-origin case and a warm-cache case. Note whether page, object, opcode and edge caches were populated. After an invalidation, allow the system to reach the stated cold or warm condition before measuring.
- Capture a baseline. Record TTFB, LCP, INP and CLS, plus request count, transfer size and the largest waterfall bottlenecks. Use both a repeatable lab profile and field data when it is available so controlled results can be checked against real visitors.
- Repeat the runs. Do not rely on one sample. WordPress performance reports for versions 6.6 and 6.7 used 100 runs; your report should state its own run count and summarize variation rather than publishing only the fastest result.
- Classify the bottleneck. A high TTFB points toward origin processing, database work, external calls, network distance or a cold cache. A delayed LCP with acceptable TTFB points toward the LCP resource, render-blocking work or media delivery. Poor INP indicates interaction scripting or main-thread contention, while poor CLS indicates unstable layout.
- Change one variable. Test one hosting or server change, cache layer, CDN setting, theme or plugin code change, or media-delivery change at a time. Keep the URL and every other condition fixed.
- Re-run and keep only meaningful improvements. Compare the target metric, the other Core Web Vitals and the visitor-visible result. A change that lowers TTFB but worsens LCP or causes layout shifts is not an overall improvement.
- Document the result. Preserve the date, geography, device, cache state, software versions, run count, configuration change and observed metrics so a later test remains comparable.
How to compare hosts or configurations fairly
Use the same URL, content and software on every candidate. Then compare along these axes:
- TTFB in both cold and warm states: reveals origin processing and cached delivery separately.
- LCP, INP and CLS: shows the user experience beyond server response.
- Repeatability: look for stable results across runs, not just the best sample.
- Throughput under load: tests whether performance holds when concurrent requests increase.
- Cache behavior: verify what is cached, how invalidation works and how quickly content regenerates.
- Geographic consistency: test the locations that matter to your audience.
- Page weight and request pattern: compare transfer size, request count and waterfall dependencies.
- Operational controls: check whether you can configure PHP, database, object cache, web server and CDN behavior well enough to reproduce and troubleshoot the result.
Present the measurements with their conditions. Saying that one configuration is “faster” without naming the geography, device, cache state and software versions hides the variables that produced the result.
Diagnosing common benchmark surprises
A cached page is fast, but publishing makes it slow
This usually indicates that the warm path is efficient while invalidation sends visitors to an uncached origin. Measure immediately after invalidation and after the cache is warm, then examine whether the invalidation scope can be narrowed or regeneration work reduced.
TTFB is acceptable, but LCP is poor
Inspect the LCP resource and the waterfall. Large images, render-blocking CSS or scripts, and late discovery of the main content can delay the visible result after the HTML arrives. Test media format, compression, responsive source selection and loading behavior without changing several variables at once.
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.
One run is excellent and the next is slow
Variable shared-server load, an inconsistent cache state, a remote service or network variation can produce this pattern. Increase the run count, label each run as cold or warm, and report the spread. A median or distribution is more informative than selecting the fastest sample.
Adding a plugin changes little, while another causes a large regression
That is expected: count is not a workload measure. Compare the code, queries, front-end assets and external requests introduced by the specific plugin or theme component. Keep the feature only when its cost is acceptable for the page and audience.
Different regions disagree
Distance to the origin and CDN edge selection can change TTFB and asset delivery. Treat each geography as a separate result, and state whether the HTML itself was edge-cached or only static assets were served nearby.
A practical decision framework
- If cold TTFB is high everywhere: investigate hosting resources, PHP execution, database queries, external calls and server configuration before focusing on front-end polish.
- If warm TTFB is good but cold TTFB is poor: examine page, object and opcode caches, invalidation and regeneration cost.
- If only distant regions are slow: evaluate CDN coverage and origin placement, then retest static and HTML delivery separately.
- If LCP alone is slow: prioritize the LCP element, image bytes, responsive loading and render-blocking resources.
- If INP is slow: profile interaction scripts and main-thread work rather than replacing the host based on TTFB alone.
- If CLS is poor: reserve space for media and inspect late-inserting elements that move existing content.
The most credible WordPress benchmark is therefore a small experiment log, not a leaderboard: a fixed page, controlled variables, repeated cold and warm runs, user-experience metrics, and a record of what changed.
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.
