Why We Don't Recommend WordPress (And When We Still Would)
StarkLabX ·
WordPress powers 39.3% of websites, yet we rarely recommend it. An honest look at its strengths, plugin and security costs, and when a custom build pays off.
We get asked this a lot, usually halfway through a first call: “Why not just use WordPress?”
It’s a fair question. WordPress is used by 39.3% of all websites and holds a 58.1% share of sites whose CMS is known (W3Techs, 10 November 2026). It’s free, it’s everywhere, and almost every developer has touched it. If we’re going to tell you we’d rather not build your site on it, we owe you a proper explanation, including the parts where WordPress is genuinely the better choice.
So here it is, without the sales gloss.
What WordPress gets right
Let’s start with the good, because there’s a lot of it.
- The ecosystem is enormous. Themes, plugins, tutorials, hosting companies that pre-install it, freelancers in every city. Whatever you need, someone has probably built a plugin for it.
- It’s cheap to start. The software is free. A theme, a few plugins and shared hosting can get a small site online for very little upfront.
- Content editing is familiar. Writing posts, adding pages and uploading images is something most marketing staff can learn in an afternoon. For content-heavy sites, that matters.
- You’re not tied to one vendor. It’s open source. You can move hosts, hire a different developer, or take your content with you.
- Core is in decent shape. Patchstack found only 6 vulnerabilities in WordPress core in 2025, all low priority (Patchstack, State of WordPress Security in 2026). The WordPress team has also put real work into performance, from faster template loading to more selective script loading (Web Almanac 2025, CMS chapter).
When WordPress is the right call
We’ll say it plainly: if any of these describe you, WordPress (or a hosted builder) may be the sensible option.
- You mainly publish articles, news or a blog, and your team needs to post daily without a developer.
- Your budget is very tight and the site is a simple brochure: a few pages, a contact form, a map.
- You already have a WordPress site that works, is fast, and is maintained by someone who patches it every week.
- You need a site live in days, and “good enough” today beats “great” next month.
If that’s you, we’ll tell you so on the call. We’d rather send you away happy than sell you something you don’t need.
Where it goes wrong
The trouble rarely starts on day one. It starts in month six, when the site needs one more feature and the answer is “install another plugin”.
1. Plugin bloat
A typical business WordPress site isn’t really “WordPress”. It’s WordPress plus a page builder, an SEO plugin, a forms plugin, a cache plugin, a security plugin, a slider, a backup tool, and often WooCommerce with its own extensions. Each one is written by a different team, on a different release schedule, with its own CSS and JavaScript.
The HTTP Archive’s 2025 Web Almanac estimates that around 60% of WordPress sites use a page builder, and notes that builders “often generate more complex DOM structures and larger CSS and JavaScript bundles”, with older builders causing “long-term maintenance and lock-in issues” (Web Almanac 2025).
Plugin quality varies a lot, too. An analysis of the full WordPress.org plugin directory found 46.6% of plugins haven’t been updated in more than two years (WPExposure, WordPress Statistics 2026, data as of 18 October 2026).
2. Security and the patching treadmill
This is the big one. Almost all WordPress security problems come from plugins and themes, not core.
From Patchstack’s 2026 report (source):
- 11,334 new vulnerabilities were found in the WordPress ecosystem in 2025, up 42% on 2024.
- 91% were in plugins and 9% in themes.
- 46% didn’t have a fix from the developer by the time they were publicly disclosed.
- For heavily exploited vulnerabilities, the median time to mass exploitation was 5 hours.
Five hours. “I’ll update the plugins this weekend” doesn’t work against those numbers.
To be fair, not every vulnerability is an emergency. Wordfence’s 2024 annual report found that over 68% of the vulnerabilities disclosed in 2024 were low-risk for most site owners, based on the authentication level or user interaction needed to exploit them (Wordfence 2024 Annual WordPress Security Report, PDF). The same report recorded just under one million distinct infected sites in 2024, with roughly 325,000–350,000 infected on any given day — figures from Wordfence’s own telemetry, not a count of every WordPress site. The risk is manageable, but only if someone is actually managing it, every week, for as long as the site exists.
For many small businesses, that weekly work doesn’t happen.
3. Performance is possible, but not the default
WordPress can be fast. Plenty of WordPress sites are. But on average, it’s an uphill fight.
The Web Almanac found 45% of WordPress sites passed Core Web Vitals on mobile in 2025, among the lowest of the major CMSs, while tightly managed platforms like Duda reached 85% (Web Almanac 2025). The HTTP Archive’s Core Web Vitals Technology Report for September 2026 puts WordPress at 48.3% passing on mobile, with only 22.9% of WordPress origins getting a “good” time to first byte on mobile, against 45.9% across all origins (HTTP Archive CWV Technology Report, September 2026).
That slow server response points at hosting and caching, not at the WordPress editor. A heavy plugin stack can make it worse.
4. Maintenance never ends
A WordPress site is a living stack: PHP version, WordPress core, theme, every plugin, and the hosting environment all have to stay compatible. One update can break a checkout or a contact form, and you often find out from a customer. Somebody has to test updates, keep backups, and fix conflicts. That cost doesn’t appear on the original quote.
Custom sites need maintenance too. Frameworks and runtimes also ship urgent fixes — we wrote about October’s patch wave across Next.js, React, PHP and Node.js. The difference is the size of the list you have to keep current.
5. Lock-in, just a different kind
WordPress itself is open, but your site often isn’t. If your layout is built in a premium page builder, moving away means rebuilding it. If your bookings, memberships or pricing logic live inside three premium plugins, you’re tied to those vendors’ licences, renewal fees and decisions.
6. Custom logic and scale hit a ceiling
WordPress was designed as a publishing system. It stretches surprisingly far, but things get awkward when you need:
- custom pricing, quotes or approval workflows
- dashboards, customer portals or staff tools
- integrations with your ERP, POS, courier or payment gateway
- an LMS, booking engine or multi-vendor marketplace that behaves exactly the way your business does
At that point, you’re writing custom code anyway, just inside a framework that wasn’t built for it, and on top of plugins you don’t control.
Why we prefer custom builds
For most websites, web apps and online stores, we build a custom site or app with a clean admin panel for your team, using modern frameworks such as React and Node.js. Here’s what that gets you:
- Only what you need. No plugin stack, no page-builder output. Every feature is one we wrote on purpose and can explain.
- A smaller, known attack surface. There’s no public plugin directory for attackers to scan for. We still patch frameworks and dependencies (see October’s patch wave), but it’s a short list we control, not 20 plugins from 20 vendors.
- Speed you can measure. We keep the front end lean, optimise images and test Core Web Vitals before launch, rather than relying on a stack of cache plugins.
- Logic that fits your business. Bookings, quotes, portals, dashboards and integrations are built as part of the system, not glued on.
- You own it. Code, domain and data are yours, documented, in your own repository.
The honest caveat
A framework doesn’t make a site fast by itself. In the same HTTP Archive data for September 2026, Next.js sites as a group pass Core Web Vitals on mobile less often than WordPress sites (35.7% vs 48.3%), mostly because many of them ship heavy JavaScript to the browser (HTTP Archive CWV Technology Report). Custom isn’t magic. A badly built custom site can be slower and less secure than a well-run WordPress one.
That’s why we don’t sell “custom” as a label. We sell the result: a site that loads fast on a mid-range phone, does exactly what your business needs, and doesn’t need a weekly firefight to stay safe. And we measure it.
So which should you choose?
A quick rule of thumb:
| Your situation | Our suggestion |
|---|---|
| Blog or news site, content team posts daily, small budget | WordPress (well hosted, few plugins, someone patching it) |
| Simple 3–5 page brochure site, tight budget | A hosted builder or a lean custom site |
| Online store with custom pricing, delivery rules or integrations | Custom build |
| Bookings, portals, dashboards, LMS, internal tools | Custom build |
| Existing WordPress site that’s slow, hacked or held together by plugins | Audit first, then fix or rebuild |
Whether you’re a growing business in Colombo or a company in London, Berlin, Austin or Sydney, the question is the same: what will this site cost you to run safely for the next three years, not just to launch?
Thinking about a rebuild?
If your current site is slow, keeps breaking after updates, or has already been hacked, we’re happy to take a look. We’ll tell you honestly whether it’s worth fixing, or whether a rebuild will save you money over time.
StarkLabX builds fast, secure websites, web apps, ecommerce stores, online ordering systems, LMS platforms and custom software, and you own everything we build.
Talk to us: starklabx.com · hello@starklabx.com · WhatsApp +94 76 881 6881
Sources
- W3Techs — Usage statistics and market share of WordPress (10 Nov 2026): https://w3techs.com/technologies/details/cm-Wordpress
- Patchstack — State of WordPress Security in 2026 (updated 25 Feb 2026): https://patchstack.com/whitepaper/state-of-wordpress-security-in-2026/
- Wordfence — 2024 Annual WordPress Security Report (PDF, verified 10 Nov 2026): https://www.wordfence.com/wp-content/uploads/2025/04/2024-Annual-WordPress-Security-Report-by-Wordfence.pdf (public page: https://www.wordfence.com/blog/2025/04/2024-annual-wordpress-security-report-by-wordfence/)
- HTTP Archive — Web Almanac 2025, CMS chapter (published 15 Jan 2026): https://almanac.httparchive.org/en/2025/cms
- HTTP Archive — Core Web Vitals Technology Report, September 2026 data (official Tech Report, verified 10 Nov 2026): https://httparchive.org/reports/cwv-tech
- WPExposure — WordPress Statistics 2026 (plugin directory analysis, data as of 18 Oct 2026): https://wpexposure.com/research/wordpress-statistics/
- StarkLabX — October 2026’s Security Patch Wave: What Next.js, React, PHP and Node.js Fixes Mean for Your Website (published 1 Nov 2026): https://starklabx.com/blog/october-2026-s-security-patch-wave-what-next-js-react-php-and-node-js-fixes-mean-for-your-website