Every hosting company advertises uptime in nines. 99.9% uptime sounds reassuring. It is also the most useless number in the hosting marketing playbook, because almost every host hits it and the small variations rarely matter to a business. The benchmarks that actually decide whether your hosting is good or bad for a Sydney business audience are different, more boring, and almost never discussed in sales conversations.
Here are the five hosting performance numbers worth knowing, target ranges for each, and how to measure them yourself.
1. Time to First Byte (TTFB)
TTFB measures how long the server takes to start responding after a request. It is the most important hosting performance metric because everything else (page render, image load, interaction) waits for the first byte.
Target ranges from Sydney to a Sydney-hosted server: under 200ms is good, 200 to 500ms is okay, over 500ms is poor. Anything over 1 second on uncached pages indicates a real problem.
Measure it with WebPageTest from a Sydney test location, or the Google Search Console Crawl Stats report which shows TTFB averaged across real Googlebot visits.
2. Server response time under load
TTFB tested cold is one number. TTFB when 50 visitors hit the site simultaneously is another. Shared hosting often shows beautiful single-visitor numbers and falls apart at the first hint of concurrent load.
Loader.io or k6 can simulate concurrent traffic against the site. Run a 50-user, 1-minute test and watch what TTFB does. On managed hosting, it usually stays stable. On shared hosting, it climbs sharply as concurrent users increase.
3. Cached vs uncached page load
A cached WordPress page is served from a static cache and loads almost instantly (under 200ms total). An uncached page goes through the full WordPress rendering pipeline (database queries, theme processing, plugin hooks) and loads much slower.
The ratio matters. If cached pages are fast but uncached pages take 4 seconds, the site falls apart for any visitor who hits a page before it has been cached (most first-time visitors). The target is uncached page load under 2 seconds.
4. Disk I/O speed
The speed of the disk underneath WordPress affects every database query and every file read. SSD-based hosting is the floor in 2026. NVMe is faster again and now standard on quality managed hosts.
Most hosting companies do not advertise disk type clearly. A quick way to check: ask the host directly, or run a benchmark plugin like WP Hosting Performance Check, which surfaces underlying disk and memory characteristics.
5. Memory ceiling and PHP version
WordPress’s memory ceiling decides how complex the site can get before pages start failing to render. Modern WordPress with a healthy plugin stack typically wants 256MB of PHP memory minimum. Shared hosts often cap at 128MB or 64MB.
PHP version matters too. PHP 8.3 is dramatically faster than PHP 7.4 (which a surprising number of sites still run). Confirm your host is on PHP 8.2 or higher and that the WordPress version is configured to use it.
Numbers in context
For a typical Australian business WordPress site, here is what good looks like in 2026. TTFB to Sydney audience: under 200ms. Concurrent load stability: TTFB stays under 400ms at 50 simultaneous users. Cached page load: under 1 second total. Uncached page load: under 2 seconds. PHP 8.2 or higher, 256MB memory, NVMe storage.
If your current hosting hits all of these, you are on good infrastructure. If it misses three or more, you are paying for hosting that is actively hurting your site.
Running the audit yourself
WebPageTest, Pingdom, and GTmetrix all offer free Sydney test locations and will give you TTFB and page load numbers for any URL. For deeper benchmarks, install WP Hosting Performance Check and run the full suite once. The whole exercise takes about 30 minutes and gives a clear picture of whether the hosting is fit for purpose.
If the numbers look bad and you are not sure whether the cause is hosting or the site itself, Defyn’s hosting team runs full performance health checks that isolate the variables and tell you exactly what is slow and why. Request a hosting health check if your site has been feeling sluggish but you do not know where the bottleneck lives.
