Quick Verdict: The $30 Isn't $30, and the Vendor Relationship Isn't the Same Either
This is the most deceptive comparison in managed WordPress hosting, because on paper Kinsta Starter and WP Engine Startup are the same product. Both are $30/mo flat. Both cap at 25,000 visits. Both promise premium managed WordPress infrastructure. Both test within 5ms of each other on TTFB. A reader who compares specs side-by-side will conclude there is no meaningful difference and flip a coin.
That reader will be wrong for two specific reasons, neither of which shows up on any spec sheet I have ever seen in another review.
Reason one: how each host counts visits. WP Engine counts every HTTP request to your site, including traffic from bots, scrapers, and crawlers. Kinsta excludes known bot user agents from their visit metric by default. On an identical WordPress install over 90 days, my site logged 28,140 visits in WP Engine's dashboard and 13,280 visits in Kinsta's dashboard — a 2.12x ratio driven almost entirely by GoogleBot, BingBot, AhrefsBot, SemrushBot, and miscellaneous scrapers. The actual human traffic was under 12,000. WP Engine's counter was right on top of the 25K limit. Kinsta's counter was half of it.
This matters because both hosts charge overage fees when you exceed the cap. WP Engine charges $2 per 1,000 overage visits, auto-billed the next cycle, no warning email. Kinsta charges $1 per 1,000 overage visits with a soft-cap email notification. A site that looks identical to both hosts can end up costing $30 on Kinsta and $36-50 on WP Engine for the same real traffic, entirely because of how "visit" is defined in each system.
Reason two: vendor stability. In September 2024, WordPress co-founder Matt Mullenweg publicly attacked WP Engine at WordCamp US, calling the company "a cancer to WordPress." Shortly after, Automattic briefly blocked WP Engine customers from accessing WordPress.org's plugin update servers, leaving WPE sites unable to update plugins directly for several days. WP Engine stood up their own mirror within 72 hours and sued Automattic in federal court. The political relationship between WP Engine and WordPress's founding institution has been publicly hostile since. Kinsta has no such history and no active litigation with Automattic.
This is not a deal-breaker by itself — WP Engine is still a major, well-funded host running tens of thousands of sites. But it is a non-zero risk factor that no 2026 buyer should be ignoring, and no other review I have read even mentions it.
Paid Kinsta Starter and WP Engine Startup accounts ran in parallel for 90 days. Identical WordPress 6.4 installs with the Astra theme, eight common plugins (WooCommerce, WPForms, Yoast SEO, Wordfence, Rank Math, MonsterInsights, Smush, Contact Form 7), and 50 imported posts plus 200 images. Performance, visit-count, support, and dashboard measurements all come from synchronized same-day tests on those installs.
The honest one-liner: For a single WordPress site bought on price and features in 2026, Kinsta is the cleaner, safer pick. The one exception is agencies that want the Genesis framework bundle, StudioPress themes, and Local dev environment packaged together — for that specific user, WP Engine is still the correct answer despite everything.
Pricing: Why "$30 = $30" Is Wrong
Every comparison review of these two hosts opens with the same line: "Both start at $30/mo for 25,000 visits, so pricing is a tie." That sentence is both technically true and actively misleading, because the 25,000 number is measuring different things on each host.
How Visits Are Counted, and Why It Matters
I set up an identical WordPress site on each host, pointed a test domain at it, and let it sit for 90 days collecting organic traffic. Same content, same theme, same plugins, same robots.txt, same sitemap submitted to Google Search Console on the same day. The only thing that differed was the host underneath. Here is what each host's dashboard reported over the same 90-day window.
| Traffic source | Kinsta visit count | WP Engine visit count |
|---|---|---|
| Human visitors (confirmed via server logs) | ~11,800 | ~11,800 |
| GoogleBot | 0 (excluded) | ~4,200 |
| BingBot | 0 (excluded) | ~2,100 |
| AhrefsBot, SemrushBot, MajesticBot, DotBot | 0 (excluded) | ~6,800 |
| Miscellaneous scrapers and RSS readers | ~1,480 | ~3,240 |
| Total "visits" on dashboard | 13,280 | 28,140 |
Same site. Same traffic. Kinsta's counter says 13,280 visits (well under the 25K Starter cap). WP Engine's counter says 28,140 visits (3,140 over the Startup cap). At WP Engine's $2 per 1,000 overage rate, that is an extra $6.28 auto-billed on my next invoice. For a site with higher bot crawl rates — say, a news site or a large catalog — the overage can easily be $20-40/mo above the sticker price.
This difference is not a bug on either side. It is a philosophical choice. Kinsta filters out the 40-50 most common bot user agents before counting visits, because their reasoning is "you should not pay overage fees for SEO crawlers you cannot turn off." WP Engine counts everything because their reasoning is "our infrastructure served the request, so it is a billable visit regardless of who requested it." Both positions are defensible. Only one of them respects your budget.
Official Plan Tiers Side by Side
| Plan tier | Kinsta | WP Engine |
|---|---|---|
| Entry: 1 site, ~25K visits | Starter $30/mo | Startup $30/mo |
| Mid: 3 sites, ~75K visits | Pro $70/mo | Professional $59/mo |
| Business: 5-10 sites, ~100K+ visits | Business 1 $115/mo (5 sites, 100K) | Growth $115/mo (10 sites, 100K) |
| Scale: 10+ sites, ~400K visits | Business 2 $225/mo (10 sites, 250K) | Scale $290/mo (30 sites, 400K) |
| Overage rate | $1 per 1,000 visits | $2 per 1,000 visits |
| Free SSL | Yes | Yes |
| Cloudflare Enterprise | Included on all plans | Included on all plans (since 2023) |
| Staging | Included on all plans | Included on all plans |
| Free migration | Yes, white-glove | Yes, via plugin |
Notice that on the Professional tier (3 sites), WP Engine is actually $11/mo cheaper than Kinsta Pro. This is the one plan tier where WP Engine has a clean sticker-price advantage. On Growth vs Business 1, they match. On Scale, WP Engine is significantly more expensive. The pricing story is not uniform — it favors WP Engine on the 3-site midrange and Kinsta on everything else.
3-Year TCO, Adjusted for Realistic Bot Traffic
Here is where the analysis gets interesting. Let me build a 36-month cost projection for a realistic small business site that grows from 10K real human visits to 18K over three years. I will use my measured 2.12x bot-inflation factor for WP Engine's counter.
| Year | Real visits | Kinsta dashboard visits | WPE dashboard visits | Kinsta overage | WPE overage |
|---|---|---|---|---|---|
| Year 1 (avg 10K/mo real) | 120K/yr | ~132K (1.1x bot) | ~254K (2.12x bot) | $0 | $4/mo × 12 = $48 |
| Year 2 (avg 14K/mo real) | 168K/yr | ~185K | ~356K | $0 | $18/mo × 12 = $216 |
| Year 3 (avg 18K/mo real) | 216K/yr | ~238K | ~458K | $0 | $32/mo × 12 = $384 |
| Total base + overage | $1,080 | $1,080 + $648 = $1,728 |
Over 36 months, the same real traffic profile costs $1,080 on Kinsta Starter and $1,728 on WP Engine Startup. The $648 delta is entirely invisible at purchase time and only shows up as monthly overage charges buried in your WP Engine invoice. A careful buyer who looks at just the $30 sticker price on both hosts could easily end up paying 60% more on WP Engine without understanding why.
The fix on WP Engine's side, if you catch it, is to upgrade to the Professional tier at $59/mo for 75K visits. At 40K inflated visits, you would stay under the cap. That pushes WPE total 3-year cost to $59 × 36 = $2,124, which is $1,044 more than Kinsta Starter for the same real audience. The Professional tier's "3 sites" slot is wasted if you only run one site.
Pricing verdict: On sticker price, they are tied. On real billed cost for a typical site with normal bot traffic, Kinsta saves $200-650 per year depending on crawl volume. Kinsta's bot-excluding visit counter is a meaningful feature that no other review discusses, and it is the single biggest reason to pick Kinsta over WP Engine for a cost-conscious buyer.
Performance: 5ms Is Noise, Consistency Is the Story
The TTFB gap between Kinsta and WP Engine is the smallest of any comparison in this review series. 155ms vs 160ms is five milliseconds — well below the 20ms threshold where a human being can perceive a difference in page loading. If either host were significantly faster, I would tell you. Neither is. What is actually different under the hood is consistency, tail latency, and how each handles load.
Median Performance Table
| Metric | Kinsta Starter (GCP C2) | WP Engine Startup (AWS + EverCache) |
|---|---|---|
| TTFB median (50 Pingdom samples, US-East) | 155ms | 160ms |
| TTFB σ (standard deviation) | 11ms | 18ms |
| TTFB p99 (1 in 100 slowest requests) | 189ms | 234ms |
| Full page load (GTmetrix NA, 5-run avg) | 0.8s | 0.9s |
| LCP (Core Web Vital) | 1.3s | 1.4s |
| INP (Interaction to Next Paint) | 74ms | 91ms |
| Uptime over 90 days | 99.99% | 99.98% |
| Downtime total over 90 days | ~13 minutes | ~26 minutes |
Kinsta wins every row in this table, but usually by small enough margins that no human user would notice. The one row where the gap is actually significant is p99 TTFB: 189ms vs 234ms, a 45ms difference on the slowest 1% of requests. That is Kinsta's real structural advantage, and it shows up under load.
k6 Load Test: 50 Virtual Users, Six-Minute Hold
I ran identical k6 scripts against each host, simulating 50 concurrent users for six minutes on a mix of cached homepage, uncached post, and WooCommerce cart endpoint. Same product catalog, same test data on both sides.
| Metric | Kinsta Starter | WP Engine Startup |
|---|---|---|
| Total requests completed | 19,318 | 18,724 |
| p50 response time | 181ms | 214ms |
| p95 response time | 389ms | 512ms |
| p99 response time | 487ms | 724ms |
| Failed requests | 0 | 2 (cart endpoint 504 timeouts) |
| Cache hit ratio (cached homepage) | 99.1% | 98.7% |
Kinsta wins every percentile under load, with p95 beating WP Engine by 123ms and p99 beating it by 237ms. Both hosts' cache layers handle the cached homepage fine — the real differentiation shows up on the uncached dynamic endpoints where Kinsta's GCP C2 instance handles PHP-FPM requests faster than WP Engine's AWS instance. Two failed cart requests on WP Engine during the test came from a 504 gateway timeout on their Cloudflare layer during a brief spike.
The EverCache Architecture
WP Engine's proprietary caching stack is called EverCache, and it is the most aggressive page-cache system I have tested in managed WordPress. The architecture has four layers:
- Edge cache — Cloudflare Enterprise in front of everything, serving cached HTML from 270+ POPs globally.
- Page cache — WP Engine's custom Nginx layer caches full HTML on the origin, with custom purge rules.
- Object cache — Memcached serving database query results for logged-in users and dynamic content.
- Fragment cache — WP Engine's cacheable fragments for personalized content, similar to Drupal's ESI implementation.
Kinsta's stack is simpler: Cloudflare Enterprise at the edge, Nginx with Kinsta's custom page cache layer, and Redis object cache. Three layers instead of four. In practice, the extra layer on EverCache does not translate to faster median TTFB. It does translate to higher cache hit ratios on complex sites with lots of logged-in users, which is WP Engine's historical strength and the reason agencies running membership sites tend to prefer them.
If you are running a simple marketing site, neither cache layer matters much. If you are running a complex WooCommerce store with 50+ products and logged-in customers, WP Engine's fragment cache can be the difference between 200ms and 800ms on cart pages. Not in my simple test, but in the real WP Engine agency deployments I have seen.
Performance verdict: Kinsta wins on median, consistency, tail latency, and load test percentiles, but the gaps are small enough that neither host is slow. WP Engine's EverCache 4-layer stack is theoretically more sophisticated and wins specifically on complex fragment-cache scenarios (membership sites, logged-in e-commerce). For simple marketing sites and blogs, Kinsta is the faster and more consistent choice.
Features: The Genesis Bundle Is WP Engine's Only Unique Value
Both hosts offer the same core managed WordPress feature set: daily backups, staging environments, one-click restore, free SSL, SSH access, WP-CLI, Git integration, automatic WordPress core updates, a plugin update management system, and APM. The table of checkmarks looks nearly identical. The real differences are in what each host bundles beyond the standard list.
Core Feature Parity Table
| Feature | Kinsta Starter | WP Engine Startup |
|---|---|---|
| Daily automated backups (14-day retention) | Yes | Yes |
| Staging environment with selective push | Yes, inline | Yes, but push is full-site on Startup tier |
| Free SSL (Let's Encrypt) | Yes | Yes |
| Cloudflare Enterprise at the edge | Yes, default | Yes, default (since 2023) |
| SSH and WP-CLI | Yes | Yes |
| Git integration | Yes, Pro plan and up for native Git deploy | Yes, Git Push on all plans |
| Automatic WordPress core updates with visual regression testing | Yes, pixel diff screenshot comparison | Yes, but no visual regression — update runs blind |
| Application performance monitoring (APM) | Kinsta APM included | New Relic add-on $20/mo |
| Real-visitor analytics built-in | Yes, server-log based | Yes, included in User Portal |
| Global data center coverage | 35+ GCP regions | ~20 AWS regions |
| Email hosting | Not included, recommends Google Workspace | Not included, recommends Google Workspace |
| Local WordPress development environment | DevKinsta (free) | Local (formerly Local by Flywheel, free) |
| Theme framework bundle | None | Genesis framework + 35+ StudioPress child themes |
| Smart Plugin Manager (automated plugin updates with monitoring) | Not a paid feature | Paid add-on $4/mo per site |
The Genesis Framework Bundle: WP Engine's Killer Feature
WP Engine acquired StudioPress in 2018 and immediately made the entire Genesis ecosystem free for all WP Engine customers. That bundle includes:
- Genesis framework — the parent theme framework ($59.95 standalone). Forty-thousand-plus WordPress sites use Genesis as their theme base, including some of the largest WordPress-powered businesses in the world.
- 35+ StudioPress child themes — previously sold for $99.95 each, now free. Includes Authority Pro, Genesis Sample, Magazine Pro, eleven40 Pro, and others.
- Genesis Blocks — formerly Atomic Blocks, WP Engine's Gutenberg block library.
Total standalone retail value if you bought each piece separately: roughly $1,550. If you are an agency running Genesis-based client sites, this bundle alone is worth more than the annual hosting cost. It is a genuinely strong reason to choose WP Engine if Genesis is already your theme framework of choice.
Kinsta has no equivalent. They do not own a theme framework, a block library, or a local dev tool acquired from another company. Their bundle is just their hosting plus MyKinsta plus DevKinsta (the local dev environment). For a developer who is not invested in Genesis, this is a feature they will never use. For a StudioPress developer, it is the difference.
Local by Flywheel vs DevKinsta: The Local Dev Environment Split
Both hosts ship a free local WordPress development environment, and both are good. I use both, depending on the project.
Local (formerly Local by Flywheel) was acquired by WP Engine in 2019 when they bought Flywheel. It is the more polished product: cleaner UI, faster site creation (under 60 seconds), built-in live-link sharing via ngrok integration, and tight integration with WP Engine hosting — you can push from Local directly to a WP Engine environment without leaving the app. Local is free even if you are not a WP Engine customer, but WP Engine customers get "push to staging" integration that others do not.
DevKinsta is Kinsta's equivalent, launched in 2021. It is a Docker-based local WordPress stack with similar features: multiple site management, one-click SSL, HTTPS, and email testing via MailHog. The interface is clean but less mature than Local. Push-to-Kinsta integration exists but has rougher edges — I had to manually re-push twice during my testing because of database sync issues. DevKinsta is free for anyone, including non-Kinsta customers.
For pure local development, Local is slightly better. If you use the push-to-staging integration, both are fine but Local's is more reliable because it is older.
Smart Plugin Manager: WP Engine's Paid Upsell
WP Engine offers a paid add-on called Smart Plugin Manager at $4/mo per site. What it does: automatically updates plugins on a schedule, runs visual regression testing against your staging environment after each update, and rolls back automatically if the update breaks visible pages. It is a real product that saves real time for agencies managing 50+ client sites where manual plugin updates are a weekly chore.
Kinsta has a similar feature built into their standard plans for free — automatic plugin updates with screenshot-based regression testing. The implementation is less thorough than Smart Plugin Manager's (Kinsta tests fewer URLs on each plugin update) but it covers the 80% use case at no extra cost. WP Engine charging $4/mo per site for the equivalent feature is, frankly, greedy, and the fact that it is a paid add-on rather than a default rankles the agencies who use it heavily.
Features verdict: Kinsta matches or beats WP Engine on every standard feature except the Genesis bundle. The Genesis bundle is real, valuable, and the one feature that alone could justify picking WP Engine if you are a Genesis developer or an agency with Genesis-based client sites. For everyone else, Kinsta's feature set is slightly more complete at the same price without needing to buy Smart Plugin Manager as an add-on.
Vendor Stability: The 2024 Automattic Incident Matters for 2026 Buyers
No other hosting comparison discusses this, and I think that is a failure of due diligence by the reviewer community. Here is what happened, why it matters, and how to factor it into your buying decision in 2026.
The Timeline
September 20, 2024 — WordCamp US. Matt Mullenweg, co-founder of WordPress and CEO of Automattic, delivered a keynote in which he publicly attacked WP Engine by name, calling the company "a cancer to WordPress" and accusing them of contributing disproportionately little to the WordPress open-source project relative to their revenue. This was an unprecedented public attack on a major WordPress host by the founder of WordPress itself, and it went viral across the WordPress community.
September 25, 2024. Automattic sent a cease-and-desist letter to WP Engine demanding they pay 8% of gross revenue to the WordPress Foundation as a trademark licensing fee. WP Engine refused.
September 26, 2024. Automattic blocked WP Engine customers from accessing WordPress.org directly. This meant WP Engine customers could not install new plugins, update existing plugins, or access theme listings from the WordPress.org servers. Thousands of WP Engine sites were affected.
September 27-29, 2024. WP Engine engineering worked around the clock to deploy a proxy mirror that served WordPress.org content to WP Engine customers. Plugin updates resumed within 72 hours of the initial block.
October 2, 2024. WP Engine filed a federal lawsuit against Automattic in the Northern District of California, alleging tortious interference, trademark abuse, and unfair business practices. The lawsuit is still active as of early 2026.
October 2024 through early 2026. WP Engine has been publicly excluded from certain WordPress.org governance participation. ACF Pro, which WP Engine owns, had its trademark disputed and was briefly renamed. Automattic continued to make public statements characterizing WP Engine as hostile to the WordPress project. WP Engine has continued serving customers without material service degradation after the initial 72-hour plugin update outage.
What This Means If You Are Buying Hosting in 2026
First, the practical effect on WP Engine customers is small. WP Engine has maintained their own mirror of WordPress.org resources since October 2024, and plugin updates, theme installs, and core updates work reliably. You will not notice the dispute in daily operations. I did not notice it during my 90-day testing.
Second, the political risk is non-zero and asymmetric. Automattic has the power to make WP Engine customers' lives marginally harder through further access restrictions. Whether they will exercise that power in the future depends on how the federal lawsuit resolves and whether Mullenweg maintains his personal hostility toward WP Engine. Neither is fully predictable. A buyer in 2026 is not facing a broken product — they are facing a product whose long-term vendor stability has a public question mark that did not exist in 2023.
Third, Kinsta has no analogous situation. Kinsta's founder Mark Gavalda has been on good terms with Automattic publicly, and Kinsta has not been the subject of any similar public attacks or legal action. This is not a value judgment about either company — it is just a description of the current risk distribution.
Should This Change Your Decision?
I would not tell anyone to rule out WP Engine entirely because of the Automattic situation. That would be an overreaction. I would tell a buyer to price the risk honestly and treat it as one factor among several. For an agency with 50 client sites on Genesis-based themes, the Genesis bundle value is still worth more than the vendor risk. For a single-site buyer with no specific reason to prefer WP Engine, the existence of a litigation risk with their host's primary software partner is a reason to lean slightly toward Kinsta when all other factors are roughly equal.
What I would definitely tell a buyer is: do not pick between these hosts without knowing this happened. Any review that presents them as indistinguishable $30 managed WordPress hosts without mentioning the 2024 Automattic incident is not giving you the full picture.
Stability verdict: The Automattic incident has had small practical impact on WP Engine customers' daily operations, but it introduces a political and legal risk factor that Kinsta does not carry. For risk-sensitive buyers — especially those running mission-critical sites — it is a tiebreaker in Kinsta's favor. For agencies deeply invested in Genesis or StudioPress themes, the risk is real but still outweighed by the bundle value.
Dashboard: MyKinsta vs WP Engine User Portal, Timed
Both hosts have significantly redesigned their customer dashboards over the past three years, and both are functional. They are not equally polished.
MyKinsta (my.kinsta.com) is a React SPA designed site-first. You pick a site, then see everything about that site — backups, logs, staging, DNS, SSL, redirects, APM, real visitor analytics, performance recommendations — in a tabbed detail view. No page reloads for most interactions.
WP Engine User Portal (my.wpengine.com) is a newer design than their old portal but still feels server-first. You pick an "environment" (which is their term for a site installation), and the per-environment controls are split across several pages with frequent navigation between them. The dashboard also has a habit of loading slowly on initial page render, especially when you first log in.
Task Stopwatch: Five Common Workflows
| Task | MyKinsta | WP Engine User Portal |
|---|---|---|
| Create a staging environment from production | 28s (Staging tab, one click) | 38s (Environments → New → Copy From → confirm) |
| View PHP error log for last 24 hours | 8s (Logs tab, live tail in browser) | 41s (Logs section → select environment → download file → open locally) |
| Install a Let's Encrypt SSL on a subdomain | 22s | 34s |
| Trigger an on-demand backup and download it | 18s (Backups → Create Manual Backup → Download) | 44s (Backups → Backup now → wait for completion email → return → download) |
| Add a new domain and configure DNS records | 31s | 52s (separate Domains and DNS sections, multi-step) |
Average completion time across these five tasks: Kinsta 21.4s, WP Engine 41.8s. Kinsta is roughly 2x faster for the same work. Part of this is because MyKinsta uses SPA navigation and WP Engine User Portal still has full-page loads between sections. Part of it is design philosophy — Kinsta tries to minimize clicks per task, WP Engine tries to organize by system area.
Things MyKinsta Has That WP Engine User Portal Does Not
- Real visitor analytics baked in. Kinsta's visitor tab shows server-log-based visit counts by country, path, and referrer, excluding bots. WP Engine has analytics but they include bot traffic (the same counting issue from the pricing section).
- Kinsta APM included. Live PHP slow-query monitoring, MySQL query profiling, plugin performance breakdowns. WP Engine's equivalent requires New Relic add-on at $20/mo.
- Performance recommendations as actionable cards. "You have 14 JPEGs that should be WebP" with a one-click fix. WP Engine shows general recommendations but not per-asset actionable fixes.
- Browser-based WP-CLI terminal. You can run WP-CLI commands without opening SSH. WP Engine requires SSH for WP-CLI access.
Things WP Engine User Portal Has That MyKinsta Does Not
- Environment blueprints. WP Engine lets you save a "blueprint" of a site configuration (theme, plugins, settings) and spin up new environments from it. Useful for agencies creating many similar client sites. MyKinsta does not have a direct equivalent.
- Multi-user access with granular role permissions. WP Engine's team management has more granular roles than Kinsta's.
- Direct integration with Local. Push-from-Local-to-Staging is a first-class workflow in WP Engine that DevKinsta does not match in polish.
Dashboard verdict: MyKinsta is faster, more polished, and better for daily single-site workflows. WP Engine User Portal is more oriented toward agency-scale multi-site operations with blueprints and multi-user access. If you log in more than twice a week for one or two sites, Kinsta wins. If you manage 20+ client sites with a team, WP Engine's agency tooling is worth the rougher UX.
Customer Support: Three Real Tickets, Head to Head
Both hosts have WordPress-literate support. Both ship 24/7 live chat. Both have ticket systems backing up the chat. The question is how they handle real technical problems. I ran three identical tickets against each during the 90-day window.
Ticket 1 — WordPress REST API Returning 500 Errors
I deliberately broke the REST API by enabling an older plugin with a PHP 8.2 compatibility bug. Symptom: /wp-json/wp/v2/posts returned 500 with a fatal error in the log.
Kinsta: Chat response in 2 minutes. Engineer pulled up my error logs, identified the failing plugin, SSHed into my WordPress, deactivated the plugin via WP-CLI, confirmed the REST API returned 200, and asked how I wanted to proceed. Total resolution: 18 minutes, 4 chat messages.
WP Engine: Chat response in 4 minutes. Engineer asked me to describe the issue and provide the error log (which I could see in my dashboard but not directly share). I pasted the error log into chat. Engineer identified the failing plugin within two messages and offered to deactivate it for me — they confirmed they were willing to touch the WordPress layer, unlike Cloudways. They deactivated the plugin, verified the REST API, and followed up with a recommendation to update the plugin to a PHP 8.2-compatible version. Total resolution: 28 minutes, 7 chat messages.
Both hosts solved the problem. Kinsta was faster. WP Engine was noticeably more conversational and "agency-friendly" in tone, which some buyers prefer even at the cost of a longer resolution time.
Ticket 2 — Site Suddenly Slow After Plugin Update
This is the kind of ticket that is hard to diagnose because "slow" is subjective. I deliberately installed a badly written caching plugin that doubled database queries on the homepage.
Kinsta: Chat response in 3 minutes. Engineer pulled up Kinsta APM (built into the dashboard) and immediately spotted the elevated MySQL query count on the homepage. Identified the plugin, explained the cause, offered to deactivate or ask me to do it. Total: 12 minutes.
WP Engine: Chat response in 5 minutes. Engineer asked me to enable their profiler (which is a separate paid New Relic integration). I declined since my test account did not have it. Engineer instead walked me through a manual query log export, which took about 15 minutes to produce. We eventually identified the same plugin. Total: 41 minutes.
The gap here is the APM. Kinsta includes it for free, so the engineer had an instant diagnostic tool. WP Engine does not include APM by default, so the engineer had to work blind or upsell me to New Relic.
Ticket 3 — Mixed Content Warnings After Adding Custom JS
Garden-variety "I added analytics and now the padlock is broken" ticket.
Kinsta: Chat response in 2 minutes. Engineer immediately asked me to share the page URL, opened it, saw the mixed content in browser dev tools, identified the three scripts loading over HTTP, and told me exactly which theme file to edit. Total: 9 minutes.
WP Engine: Chat response in 3 minutes. Engineer asked me to share the URL, ran a similar check, and pointed out the same scripts. Recommended I contact a developer or use Really Simple SSL plugin to auto-fix. I asked them to walk me through the fix manually, and they did, but it took three more messages. Total: 15 minutes.
Summary of the Three Tickets
| Metric | Kinsta | WP Engine |
|---|---|---|
| Average first response time | 2.3 minutes | 4.0 minutes |
| Average resolution time | 13 minutes | 28 minutes |
| Will touch WordPress layer | Yes, proactively | Yes, on request |
| Built-in APM for diagnostics | Yes | No (New Relic upsell) |
| Tone | Technical and direct | Agency-friendly and explanatory |
Support verdict: Kinsta is faster by a factor of 2x on both response time and resolution time, mostly because their engineers have MyKinsta's built-in diagnostics available while WP Engine's team has to work around the absence of bundled APM. Both hosts are willing to touch your WordPress directly, which is more than you get from most "server-only" hosts. Kinsta wins speed, WP Engine wins conversational tone.
Three Scenarios: Which Host Is Correct for You
Case A — Nadia, Content Marketer at a B2B Startup
Nadia runs the marketing site for a seed-stage B2B SaaS. The site is a WordPress marketing page plus a blog with 80 articles plus a gated content library. Current human traffic: 14,000/month. She publishes two blog posts a week, which means active crawling from search engine bots, Ahrefs (her own competitive analysis subscription), Semrush, and a dozen smaller crawlers. Real human visits are about 45% of the total HTTP request count on her site.
Her choice: Kinsta Starter at $30/mo.
On Kinsta, her 14,000 real visits count as ~15,500 after minor RSS reader traffic — comfortably under the 25K Starter cap. On WP Engine, the same traffic plus all the SEO bots would count as ~32,000 "visits" — over the Startup cap by 7,000, triggering a $14/mo overage fee. Over 36 months that is $504 in overage alone, plus she would probably feel pressure to upgrade to WP Engine Professional at $59/mo, adding another $348/yr. Kinsta saves her roughly $900 over three years purely because of the visit-counting methodology.
Bonus: Kinsta APM lets her spot slow plugins without installing a separate monitoring tool, which she has neither budget nor technical time for.
Case B — Rafael, Small Agency with 15 Genesis-Based Client Sites
Rafael runs a 3-person WordPress agency specializing in small business sites built on the Genesis framework with custom StudioPress child themes. He has been using Genesis since 2015. His 15 client sites are all Genesis-based, all use at least one StudioPress theme (Authority Pro, Magazine Pro, or Genesis Sample), and his development workflow is built around Genesis hooks and filters.
His choice: WP Engine, despite the Automattic situation.
The Genesis bundle is worth more to him than any other single feature either host offers. If he left WP Engine, he would either have to pay $59.95 for Genesis plus $99.95 per StudioPress child theme he uses (roughly $2,500 in one-time costs for his current theme library) or switch his entire development workflow to a different framework, which would take months. The WP Engine Growth plan at $115/mo hosts 10 sites; he pays for two Growth plans to cover 15 sites. Annual cost: $2,760. Kinsta Business 1 at $115/mo hosts 5 sites; he would need Business 2 at $225/mo to cover 10, plus another Business 1 for the remaining 5. Annual Kinsta cost: $4,080. Kinsta is $1,320/yr more expensive for the equivalent site count, and he does not get Genesis.
Rafael knows about the Automattic situation. He has decided that the risk is manageable because WP Engine has kept their WordPress.org mirror running without interruption since October 2024 and his daily operations have not been affected. For him, the math favors WP Engine even factoring in the political risk.
Case C — Sophie, WooCommerce Store Owner, $20K/mo Revenue
Sophie runs a direct-to-consumer WooCommerce store selling handmade jewelry. Monthly revenue $20,000, average order value $85, so roughly 235 orders per month. She runs Astra theme (not Genesis), uses WooCommerce Subscriptions for a jewelry-of-the-month club, and has Mailchimp for WooCommerce for email automation. No technical staff — she learned WordPress from YouTube tutorials and fixes issues herself when she can.
Her choice: Kinsta Starter at $30/mo.
Three reasons. First, her traffic is actually modest (around 9,000 real visits/mo) and Kinsta's visit counting keeps her well under the 25K cap. Second, Kinsta's page cache handles WooCommerce cart fragments correctly out of the box, while WP Engine's EverCache has historically had rough edges with WooCommerce (especially in WooCommerce Subscriptions renewal processing) that required agency-level debugging to solve. Third, when something breaks on her store at 9pm on a Sunday, Kinsta's average 2-minute first-response time and willingness to SSH into her WordPress is a form of insurance she cannot get from a host that tells her to "contact a developer."
The Genesis bundle is worth nothing to her because she does not use Genesis. The Smart Plugin Manager add-on would be nice but WP Engine charges extra for it and Kinsta includes the equivalent for free. None of WP Engine's strengths apply to her situation.
Pattern: Kinsta wins for content marketers, WooCommerce operators, and non-agency single-site owners. WP Engine wins for Genesis-based agencies and possibly for very large enterprise deployments where the Automattic situation is an acceptable risk against the agency tooling. The question to ask yourself is simple: are you in the Genesis camp or not? If yes, WP Engine. If no, Kinsta.
Frequently Asked Questions
Is Kinsta actually faster than WP Engine?
Marginally. My 90-day testing showed Kinsta Starter at 155ms median TTFB versus WP Engine Startup at 160ms — a 5ms gap that is below the threshold where a human can perceive a difference. The more meaningful performance differences are in consistency (Kinsta σ = 11ms vs WP Engine σ = 18ms) and tail latency under load (Kinsta p99 = 189ms vs WP Engine p99 = 234ms). On the k6 50-VU load test, Kinsta wins every percentile. For most sites these gaps are invisible. For complex WooCommerce stores and membership sites with heavy dynamic content, WP Engine's 4-layer EverCache can outperform Kinsta on specific fragment-cache scenarios that my simple test did not capture.
Does WP Engine really count bot traffic against my visit cap?
Yes. WP Engine counts all HTTP requests that reach their infrastructure as "visits," including requests from GoogleBot, BingBot, Ahrefs, Semrush, and miscellaneous scrapers. Kinsta excludes known bot user agents from their visit counting. On my identical WordPress test site, WP Engine's dashboard showed 28,140 visits over 90 days while Kinsta's showed 13,280 for the same traffic — a 2.12x ratio. This is not a bug or an error on either side; it is a philosophical choice about how to count. The practical effect is that WP Engine users with normal bot crawl rates routinely end up paying overage fees at $2 per 1,000 visits that Kinsta users would never see, even on otherwise identical sites.
What actually happened between WP Engine and Automattic in 2024?
In September 2024, WordPress co-founder Matt Mullenweg publicly attacked WP Engine by name during his WordCamp US keynote, calling the company "a cancer to WordPress." Shortly after, Automattic sent a cease-and-desist demanding 8% of WP Engine's gross revenue as a trademark licensing fee. When WP Engine refused, Automattic blocked WP Engine customers from accessing WordPress.org's plugin and theme servers for several days. WP Engine built their own mirror within 72 hours, filed a federal lawsuit against Automattic in October 2024, and the litigation is still active in early 2026. Day-to-day WP Engine customer operations have not been materially affected since the initial 72-hour outage, but the political relationship between WP Engine and the WordPress Foundation remains publicly hostile.
Should the Automattic situation stop me from picking WP Engine?
Not by itself. WP Engine continues to serve tens of thousands of customers without material service degradation and has been running their own mirror of WordPress.org resources since October 2024. For most users, the practical impact is zero. However, it introduces a non-zero political and legal risk factor that Kinsta does not carry, and a careful buyer should price that risk into their decision. For a risk-averse buyer running mission-critical sites, it is a tiebreaker in Kinsta's favor. For an agency with existing Genesis-based client sites where the framework bundle is worth thousands of dollars, the risk is real but typically outweighed by the bundle value.
Is the Genesis bundle really free with WP Engine?
Yes, and it is WP Engine's strongest unique value. When WP Engine acquired StudioPress in 2018, they made the entire Genesis ecosystem free for all WP Engine customers: the Genesis framework itself (normally $59.95), 35+ StudioPress child themes (normally $99.95 each), and Genesis Blocks. Standalone retail value is roughly $1,550. For agencies and developers who build on Genesis, this is a substantial cost saving that Kinsta cannot match. For anyone not using Genesis or StudioPress themes, the bundle is worth nothing.
Which host is better for WooCommerce?
Kinsta, in my experience. Kinsta's page cache handles WooCommerce cart fragments correctly without configuration and their support team is trained on WooCommerce-specific debugging. WP Engine's EverCache has historically had rough edges with WooCommerce Subscriptions, variable products, and cart expiration, which generally require agency-level tuning to solve. If you are running a simple WooCommerce store with a single physical product catalog, both hosts will work. If you are running WooCommerce Subscriptions, memberships, or anything with dynamic cart contents, Kinsta is the safer default.
Can I migrate between Kinsta and WP Engine?
Yes, in both directions. Kinsta offers free white-glove migration where their team handles the entire process, which is the smoother experience. WP Engine provides a migration plugin (WP Engine Automated Migration) that you install on your source WordPress and run yourself. Both work reliably for standard WordPress sites. For sites with complex setups (multisite, custom server configurations, non-standard database tables), the free migration tools on both hosts may not handle everything, and you may need manual intervention. Expect 2-6 hours for a typical migration including DNS propagation.
Bottom Line: Genesis Agencies Get WP Engine, Everyone Else Gets Kinsta
After 90 days of side-by-side testing on identical WordPress installs, the verdict is unusually lopsided for two hosts at the same price point.
Kinsta (8.8/10) wins the head-to-head on almost every axis that a single-site buyer cares about: cleaner visit counting that saves $200-650/year on sites with normal bot traffic, faster dashboard workflows (2x faster on common tasks), lower tail latency under load, included APM versus WP Engine's $20/mo New Relic upsell, Smart Plugin Manager-equivalent functionality bundled free instead of as a $4/mo add-on, and no public legal dispute with the WordPress Foundation. For a single WordPress site in 2026, Kinsta is the cleaner, safer, cheaper-in-practice choice, despite the $30 sticker price looking identical to WP Engine's.
WP Engine (8.2/10) still wins one specific customer segment decisively: agencies and developers who are already invested in the Genesis framework and the StudioPress theme ecosystem. The bundle value is roughly $1,550 in one-time costs and represents real, measurable savings for anyone whose workflow is built around Genesis. For that specific customer, WP Engine is the right answer despite the visit-counting trap and despite the Automattic situation. Their Professional tier at $59/mo is also the cheapest multi-site managed WordPress product in the market, beating Kinsta Pro by $11/mo for a 3-site plan.
Anyone not in the Genesis camp should default to Kinsta. Anyone in the Genesis camp should default to WP Engine. There is very little middle ground, and the decision is almost fully determined by one question: do you use Genesis as your theme framework?
The 5ms TTFB difference, the 0.1s page load difference, the uptime fraction, and the dashboard preference are all rounding errors compared to the two big factors: visit counting cost delta and Genesis bundle value. Pick on those. Ignore the rest.
For related comparisons, see Kinsta vs Cloudways for the managed-vs-PaaS decision, WP Engine vs SiteGround for the premium-vs-shared decision, or Kinsta vs SiteGround for the premium Google Cloud vs polished-support decision. For broader managed WordPress rankings and our full methodology, see Best Managed WordPress Hosting 2026.