Why WordPress, still
WordPress runs more than 43% of the web (per W3Techs), and that's the reason I build on it rather than something newer: whoever takes over a site after me can almost always find a developer who already knows the stack. A
WordPress developer
isn't optional for every site, but the moment you need something the page builder doesn't do, you're paying someone to either hack around the limit or rebuild.
Where page builders stop being enough
A
theme
handles the look. A plugin like
WooCommerce
or ACF Pro handles a job the theme doesn't. Most sites never need more than that. The ones that come to me usually need a custom checkout flow, a booking system, or a layout the builder's grid can't produce, and at that point a
custom build
ends up cheaper than the hours spent fighting the plugin.
Speed is usually the same three problems
When a site scores badly on
Core Web Vitals,
it's almost always the same pattern: an unoptimised hero image, a page builder loading its own CSS and JS on top of the theme's, and a plugin running on every page whether it's needed or not. On the
performance jobs
I take on, fixing those three usually gets a site from the 30s or 40s into the 90s.
What hiring a freelancer actually changes
An agency adds a project manager and a sales process between you and whoever writes the code. A
freelance WordPress developer
removes that layer, for better or worse: fewer people to loop in, but also fewer people to catch something if I'm unavailable. For most single-site projects that trade is worth it.
When you
hire me directly,
you're talking to the person who'll actually build the site, with a fixed price agreed before I start. Agencies use me the same way as a
white-label partner:
I build under NDA and never contact their client.