Kinsta Performance: Benchmarks, Latency & Limits 2026
Kinsta runs WordPress on Google Cloud C2/C3D containers, 12 vCPU each, behind a 300+ PoP CDN. Concurrency is capped by PHP threads, 2 to 16, on a 99.9% SLA.
Kinsta Performance verdict
Kinsta runs every WordPress site on Google Cloud's compute-optimized C2 and newer C3D machines, in isolated LXC containers of 12 vCPU and 8 GB each.
Free Cloudflare Edge Caching fronts them across 300+ PoPs. Plans meter by bandwidth and sites, and PHP threads, 2 to 16, cap concurrency, so thread headroom matters more than raw traffic.
Size by PHP threads, not just bandwidth. A busy dynamic site, WooCommerce or membership, needs the thread headroom of WP 20 or a single-site tier, while a brochure site is fine on 2 threads. Add Redis if the database is the bottleneck. Treat the Review Signal Top-Tier record as a reliability signal rather than current latency, since it predates the C3D machines, and benchmark your own theme before launch.
- The independent Review Signal numbers, 85ms blitz, 340ms sustained, 0.02% errors, are 2016 to 2019 vintage. Kinsta stopped entering in 2020, so they predate the C3D machines and are not current latency.
- Concurrency is bounded by PHP threads, 2 to 16 by plan, not vCPU, so a thread-starved plan queues requests even when bandwidth is spare. New plans bill by bandwidth, not visits, and the visits-named tiers map to the same price ladder.
- Redis object cache and hourly backups are paid add-ons, not included.
- Hosted on
- Google Cloud
- Container
- 12 vCPU / 8 GB
- Edge cache PoPs
- 300+
- Uptime SLA
- 99.9%
- Indep. test errors
- 0.02%
This page covers how fast Kinsta runs and what limits it. Region coverage and pricing live on their own pages.
Size your Kinsta plan by traffic and sites
4 PHP threads set the concurrency ceiling; traffic or bandwidth above the plan is billed as overage, not a forced upgrade, so size by threads first.
Computed from Kinsta's published visit caps and PHP-thread tiers. Kinsta bills by visits or bandwidth; PHP threads are the concurrency ceiling and traffic over the plan is overage. Verify against your own traffic.
Measured response under load
| Measurement | Load | Result | Source |
|---|---|---|---|
| Avg response (Blitz) | 1-5,000 users, 60s | 85 ms | Review Signal 2016 |
| Response spread (Blitz) | 1-5,000 users, 60s | 83-87 ms | Review Signal 2016 |
| Avg response (LoadStorm) | 500-10,000 users, 30 min | 340 ms | Review Signal 2016 |
| Peak response (LoadStorm) | 500-10,000 users, 30 min | 15,014 ms | Review Signal 2016 |
| Cached-HTML TTFB | Edge Caching (Cloudflare) | >50% faster | Kinsta |
| Edge cache reach | Static + dynamic HTML | 300+ PoPs | Kinsta |
Throughput and concurrency model
| Dimension | Value | Notes |
|---|---|---|
| PHP threads (entry) | 2 threads | Single 20GB and WP 2; threads cap concurrent PHP requests |
| PHP threads (top single-site) | 16 threads | Single 3.15M plan; 14 on the 2.5M tier |
| Container resources | 12 vCPU / 8 GB | Each site runs in its own isolated LXC container |
| Sustained throughput | 730 req/s | Independent 2016 enterprise load test; 1,041 peak |
| Requests served in test | 1.31M / 0.02% errors | 1,314,178 requests, 274 errors over 30 min |
| Object cache | Redis (add-on) | Persistent object cache for DB-heavy throughput, $100/site/mo |
Plan ceilings
| Plan | Sites | Bandwidth | Storage | PHP threads |
|---|---|---|---|---|
| Single 20GB | 1 | 20 GB | 10 GB | 2 |
| WP 2 | 2 | 40 GB | 20 GB | 2 |
| WP 5 | 5 | 65 GB | 30 GB | 4 |
| WP 10 | 10 | 125 GB | 40 GB | 4 |
| WP 20 | 20 | 250 GB | 50 GB | 6 |
| WP 40 | 40 | 500 GB | 60 GB | 6 |
Kinsta reliability and architecture
- The standard SLA guarantees 99.9% uptime, with Enterprise plans eligible for 99.99% when stated in the Order Form; service credits apply once downtime exceeds the threshold
- Kinsta runs exclusively on Google Cloud Platform, the only managed-WordPress host to do so, using compute-optimized C2 and newer C3D virtual machines on the Premium Tier network
- The C3D machines (AMD EPYC with Intel IPUs) deliver about 20 to 50% better response time and 46.8% more uncached pages served per second than the previous C2 generation
- Each WordPress site runs in its own isolated LXC software container on an LXD-managed host, so a neighbouring site cannot consume another's resources
- Kinsta checks every site's uptime 720 times a day and self-heals failed containers automatically
- The stack is Linux, Nginx, PHP 7.4 to 8.5 and MariaDB, with a server-level full-page cache plus free Cloudflare Edge Caching on every plan
Kinsta benchmark results, independently measured
- Review Signal (reviewsignal.com), an independent third-party load-testing benchmark, awarded Kinsta Top Tier status in 2014, 2015, 2016, 2018 and 2019, one of only two companies to place Top Tier on every plan tier it tested
- In the 2016 enterprise LoadStorm test (500 to 10,000 concurrent users) Kinsta served 1,314,178 requests with only 274 errors, a 0.02% error rate
- Independent uptime monitors in the same 2016 test recorded 99.98% (StatusCake) and 100% (UptimeRobot) over the run
- In the 2019 benchmark Kinsta posted 100% uptime and zero errors across every price tier from entry to enterprise
- Kinsta has not entered Review Signal's benchmark since 2020, so this independent data predates the current C3D machine generation and should be read as a historical reliability signal
Kinsta Performance FAQ
How does Kinsta handle performance and caching?
Every site runs in an isolated LXC container on Google Cloud compute-optimized C2 or C3D machines, 12 vCPU and 8 GB. Caching is layered. A server-level Nginx full-page cache sits first, then free Cloudflare Edge Caching serves cached HTML from 300+ PoPs, cutting TTFB by over 50%. The Cloudflare CDN handles static assets with HTTP/3 and Brotli, and an optional Redis object cache is an add-on.
What limits concurrency on Kinsta, bandwidth or PHP threads?
PHP threads. Each plan includes a fixed number: 2 on Single and WP 2, 4 on WP 5 and 10, 6 on WP 20 and 40, up to 16 on the largest single-site tier. Threads cap how many PHP requests run at once, and bandwidth and storage are separate ceilings. A dynamic site can saturate its threads long before it hits its bandwidth, so thread headroom is the number to size by.
How fast is Kinsta in independent tests?
The independent Review Signal benchmark measured an 85ms average response under a 1 to 5,000 user blitz. It ran 340ms under a sustained 500 to 10,000 user LoadStorm run, with a 0.02% error rate and 99.98 to 100% uptime in the 2016 enterprise test. Kinsta was rated Top Tier every year it entered, 2014 to 2019. It has not entered since 2020, so these predate the current C3D machines.
What uptime SLA does Kinsta guarantee?
The standard contractual SLA is 99.9% uptime, and Enterprise plans can carry 99.99% when specified in the Order Form. Service credits apply once monthly downtime exceeds the threshold, about 43 minutes for 99.9% or 4 minutes for 99.99%. Kinsta checks every site 720 times a day and self-heals failed containers.
Does Kinsta bill by visits or bandwidth?
Current plans bill by monthly bandwidth and number of sites, from Single at 20GB through WP 40 at 500 GB and 40 sites. The older visits-named tiers still exist and map to the same price ladder, but the headline meter is now bandwidth. CDN bandwidth, 125 to 1,500 GB, is a separate included allowance.
Are Redis and hourly backups included?
No. The Redis persistent object cache is a paid add-on at $100 per site a month for database-heavy sites. Hourly backups are add-ons too, $20 per site a month for 6-hour and $100 per site a month for hourly. Daily backups and free Cloudflare Edge Caching are included on every plan.
Sources & verification
| Source | What was checked | Last checked |
|---|---|---|
| Kinsta Official | Official product page | July 10, 2026 |
| Kinsta Blog What You Should Know | Blog What You Should Know | July 10, 2026 |
| Kinsta Changelog Google C3d Machines | Changelog Google C3d Machines | July 10, 2026 |
| Kinsta Cloudflare Integration | Cloudflare Integration | July 10, 2026 |
| Kinsta Pricing | Pricing and plans | July 10, 2026 |
| Kinsta Service Level Agreement | Service Level Agreement | July 10, 2026 |
| Kinsta Wordpress Hosting Php | Wordpress Hosting Php | July 10, 2026 |
Every fact on this Kinsta page is tied to a named source and a verification date. Freshness-sensitive figures trace to the sources above; verify against the vendor before relying on them.
Explore Kinsta
Every page on Kinsta in one place, you are on performance.