WordPress is the most-blamed and least-understood CMS on the internet
You've heard it from every other agency. WordPress is slow. WordPress is insecure. WordPress is for amateurs. WordPress is "old." WordPress can't do ecommerce. WordPress can't do SEO. WordPress can't compete with Webflow / Squarespace / Shopify / Framer / whatever-the-current-darling is.
I run a $25M+/yr ARR ecommerce business on WordPress. This WordPress site runs the same engineering I ship to clients — Core Web Vitals green, search-engine data built into the site code itself, owner-portable code, no plugin bloat. The 1,683 redirect rules I just migrated through a permalink change on this site — all WordPress. 100+ South Florida client sites I've engineered over 11 years — WordPress.
The reputation isn't nothing — there's a real pattern underneath it. But the pattern isn't "WordPress is bad." The pattern is "WordPress amplifies whatever quality of work you put into it." A senior engineer building a custom WordPress theme produces a site that ranks, converts, performs, and lives 10+ years. A freelancer running 18 plugins on top of a stock theme produces the exact site that earns WordPress its bad reputation.
Both are "WordPress sites." Only one of them is what people are actually talking about when they complain.
What follows is the engineering honesty on this — what WordPress actually is, what gets blamed on it that isn't its fault, and what a properly-engineered WordPress stack looks like in 2026 if you're considering it for your business.
10 questions to ask before you sign for a WordPress build
If you're evaluating WordPress agencies, these are the questions that separate the engineers from the template-stackers. Copy them into your discovery call notes.
-
Are you building me a custom theme, or installing a premium theme?
Why it matters: Custom theme = built for your business. Stock theme = template thousands of others use. Both produce WordPress sites; only one is differentiated.
-
Are you using Elementor / Divi / Beaver Builder, or native Gutenberg?
Why it matters: Page builders are the #1 cause of WordPress performance complaints. Gutenberg + a custom theme produces faster, cleaner, more portable sites.
-
How many active plugins will my site have on launch?
Why it matters: Under 8 = disciplined. 15+ = the reputation. Each plugin is a perf cost + security surface + maintenance burden.
-
Where is my schema markup emitted from — a plugin or the theme?
Why it matters: Theme-coded schema survives plugin disasters + WP updates + format changes. Plugin-emitted is fragile.
-
What hosting are you putting me on, and is the account in MY name?
Why it matters: Managed WordPress (Kinsta / WP Engine / Cloudways) is the minimum bar. Reseller-hosted shared plans cost you 3x retail + lock you in.
-
What PHP version will my site run, and how do I upgrade it later?
Why it matters: PHP 8.2+ is the floor in 2026. Lower means you're running EOL code that won't get security patches.
-
What does my mobile Lighthouse Performance score look like at launch?
Why it matters: 85+ is achievable in WordPress with discipline. Anything below 70 means the build isn't optimized.
-
Where will my code repository live, and can I take it elsewhere if I leave?
Why it matters: Code in your repo at launch = portable. Code in the agency's account = vendor lock.
-
How do you handle updates — do you test on staging first?
Why it matters: Production-direct updates is how sites break. Staging-first is professional practice.
-
Show me 3 WordPress sites you built 3+ years ago that you still maintain.
Why it matters: Track record on the same platform = real WP expertise. Anyone who can’t produce 3 examples is making it up as they go.