The WordPress-bashing in 2026 is louder than ever. Most of it is justified — most WordPress sites are slow, insecure, plugin-bloated and joyless to maintain. And yet, on a meaningful number of our engagements, WordPress remains the right answer. Here's the honest comparison.
Scale 1: marketing site, < 50 pages, one or two editors.
Best pick: Webflow. Editing UX is genuinely good. Performance is fine. Pricing is moderate. There is a reason this segment has migrated en masse to Webflow over the last four years.
Second pick: Custom Astro / Next.js with a headless CMS. Higher up-front cost; lower ongoing. Better performance ceiling. Only worth it if you have engineering capacity in-house.
WordPress here: Probably wrong. The editing UX is not as good as Webflow, the performance ceiling is lower, and the maintenance overhead doesn't pay back at this scale.
Scale 2: content-heavy marketing site, 100–500 pages, 3–6 editors, an active content programme.
Best pick: WordPress. Editing UX with Gutenberg in 2026 is genuinely good. Block patterns, custom blocks, and a well-built theme give content teams a fast path to ship without designer involvement. Plugin ecosystem solves 80% of content-team requests without custom code. The right hosting (WP Engine, Kinsta) handles performance.
Second pick: Headless WordPress + Next.js. Best performance ceiling. More expensive to build and maintain. Worth it when the editing team is large and the performance budget is aggressive.
Webflow here: Editing breaks down past 100 pages. The CMS Collections model isn't designed for editorial workflows. We don't recommend Webflow at this scale.
Scale 3: 500+ pages, multi-region, multi-language, complex commerce or auth flows.
Best pick: Custom Next.js + headless CMS (often headless WordPress, Sanity, or Contentful). The performance, scalability and architectural flexibility justify the engineering cost.
Second pick: Hosted enterprise platforms. Sitecore, Adobe Experience Manager — only when explicit enterprise constraints demand them. Most teams that pick these regret it within 18 months.
Vanilla WordPress here: Falls over. Hits performance and architectural limits. Headless WordPress is fine; vanilla is not.
The pattern.
Most agencies pick the platform they always pick, then justify it. We pick against the operating scale and the in-house team. WordPress wins in the middle band — which is, conveniently, the band where the highest share of marketing sites live.
The platform that wins is the one your content team can ship on without calling you. WordPress wins that test more often than the discourse suggests.
What about Shopify, Drupal, Craft, Statamic, etc.?
Shopify wins when commerce is the front door. Drupal we recommend for specific public-sector and editorial use cases. Craft and Statamic win when the team is small, technical and opinionated; they don't scale past one or two well-aligned engineers in our experience. None of them displace WordPress in the mid-band.
If you're currently picking a platform for a new build, the question to answer first is the editing team's capacity. The performance, scalability and design questions follow from that — not the other way around.