why wordpress sucks (for the site you actually want)

Let me save you the search. WordPress doesn't suck. It's the wrong tool for the site you actually came here wanting, and the people who build it for a living will not tell you that, because it's the only tool they own. I've shipped on it. I've shipped off it. I'll tell you exactly when each one is right, and I'll start with the part the WordPress shops leave out.

You came here wanting a site that looks like nobody else's. Fast, distinctive, the kind of thing that makes someone stop scrolling and wonder who made it. That's the site WordPress fights you on, at every step, from the first hour to the last.

what actually goes wrong

The page builder is a tax you pay forever. Elementor, Divi, WPBakery — the things that promise you can build anything by dragging boxes. What they actually ship is a page wrapped in forty nested divs, inline styles fighting each other, and a stylesheet so heavy the browser chokes before your content shows up. You wanted custom. You got a template with the serial numbers filed off, and it's slower than both. Anyone who's opened the page source of a builder site knows the specific despair I'm describing.

The plugins are how it breaks. WordPress out of the box does almost nothing distinctive, so every real feature is a plugin — a contact form, a gallery, SEO, caching, the 3D thing you actually wanted. Each one is code from a stranger, updating on its own schedule, and any one of them can break the other twenty. The site that worked Friday is white-screened Monday because a plugin auto-updated and stopped speaking to another plugin. I have watched this happen to people on launch day. It is not rare. It's the normal failure mode.

The plugins are also how it gets hacked. This isn't a vibe, it's the single biggest attack surface on the open web. WordPress runs a huge share of the internet, which makes it the fattest target, and the holes are almost never in WordPress itself — they're in some abandoned plugin a freelancer installed in 2021 and forgot. You inherit the security record of every stranger whose code is running on your site. The fix is "keep everything updated forever," which is a job, which is why people don't, which is why the pharma-spam injection is a genre.

It's slow in a way you pay for twice. Every page is assembled on the fly — database query, plugins run, theme renders, then the visitor gets bytes. So you bolt on a caching plugin to undo the slowness the platform created, and now you've got a caching layer that itself breaks things and needs clearing every time you change anything. You're maintaining a fix for a problem the tool gave you. A modern stack renders the page once, ahead of time, and just serves the file. It's not a little faster. It's a different category, and speed is money — slow sites lose the sale before the sale starts.

It fights you the moment you want something nobody else has. This is the real one. The whole thing is built around posts, pages, and a content model someone else decided. The second you want a real configurator, a custom WebGL moment, an interaction that doesn't fit the blog-shaped hole, you're not building a feature — you're fighting the platform's assumptions, wrapping your custom code in its lifecycle, making the thing it doesn't want to do. You end up paying a specialist to force WordPress to act like it isn't WordPress. At which point: why is it WordPress.

That's the honest indictment. Bloat you can't remove, a security surface you inherit from strangers, a speed problem you pay twice to half-fix, and a platform that resists the exact distinctiveness you're paying for. For a custom, fast, one-of-a-kind site, it's the wrong tool. Not a close call.

now the part that makes the rest true

WordPress is still the right call sometimes, and if I pretended otherwise you should stop trusting this whole page.

Use WordPress when:

• A non-technical team updates it every day. A newsroom, a magazine, a busy blog. People who need to log in, write, hit publish, and never think about code. WordPress's editing setup is genuinely good at this, it's twenty years mature, and your writers already know it or will in an afternoon.
• The layout is standard and that's fine. You don't need to look like nobody else. You need a clean, working site that does the normal thing well. A template that millions have used is a feature here, not an insult — it's battle-tested and it's cheap.
• The budget is tight and the timeline is now. A few hundred dollars and a weekend gets a small business a real, working website. Nothing custom touches that. If the choice is WordPress today or "custom" in three months you can't afford, take WordPress. A live site beats a perfect plan.
• It's content-heavy and content-first. Hundreds of articles, categories, archives, a real publishing operation. WordPress was built for exactly this and it's still one of the best tools on earth for it.

If you're a news site, a daily-updated blog, a small shop that needs to exist by Friday on a shoestring — build it on WordPress and don't let anyone (including me) talk you out of it. You'd be paying for custom work that buys you nothing your visitors will notice.

The line is simple. WordPress is a publishing platform that's been bent into a website builder. When you actually need a publishing platform, it's great. When you need a distinctive, fast, custom site — a brand, a product, a launch, the thing that has to feel like you and load before someone gets bored — bending a publishing platform into that shape is the most expensive way to get a worse result.

Know which one you're building. That's the whole decision. If you're not sure, that's a real question and a short conversation, not a sales call — hello@nightshiftglow.studio. We've shipped both and we'll tell you which one you need, even when it's the one we don't build.