Which WordPress Theme to Choose? A Programmer’s Perspective (Case Study)
"Which theme do you recommend?"
It’s one of the most common questions I hear. And honestly? There is no single answer.
At MultiTask Creations, I deal with a broad spectrum of IT daily – from creating dedicated applications and coding sites from scratch to advanced data analysis in Power BI. Even though I move freely in the backend and frontend worlds, when a client comes to me for a business website, I very often… advise them against writing it in pure code.
I’ve seen simple business card sites built on complicated technologies (which was a waste of budget) and complex systems “forced” into visual builders.
Today, I’ll show you my approach to selecting technology. No pretending that “one solution fits all.” This is an honest record of what works in my projects – through the eyes of a programmer who chooses the tool for the goal.
Why WordPress at all? (Since I can code)
Before getting to the specifics, a bit about my background so you understand the perspective. My adventure with IT began during my engineering studies. On a daily basis, I combine programming with data analysis. I create sites from scratch in HTML/CSS/JS, build applications, and visualize data for business. I know the “proper,” engineering approach to code.
So why does WordPress occupy such an important place in my company’s offer? I choose it consciously for a specific group of clients. Most small and medium business owners don’t need a dedicated application written in React or Next.js. They need a tool that:
They can edit themselves (change text, add a photo).
Doesn’t require calling a developer for every typo.
Allows them to launch quickly and scale marketing.
As a programmer, I could write them a site in pure code – it would probably be milliseconds faster. But I would make them dependent on me. And I provide solutions that support business, not build a “golden cage.”
That’s why I apply a clear division in my web projects.
My Division: Two Worlds, Two Solutions
In the projects I’ve completed so far (and those I maintain), two main paths have emerged.
Path 1: Simple Business Cards and Corporate Sites
What it is: A site with an offer, “about us,” portfolio gallery, blog, and contact.
My most common choice: Kadence (FREE) + Elementor (FREE).
This is my “daily driver” for smaller commissions. Kadence FREE is, in my opinion, one of the lighter and more sensible themes on the market. The free version is sufficient for 90% of business card sites. It has great default settings and a header/footer builder, so I don’t waste time fighting with configuration.
I choose Elementor FREE out of pragmatism. I could code the layout by hand, but Elementor allows me to “click through” the site structure in a few hours. The client sees the effect immediately, and I can focus on refining the details.
Honestly about the downsides: Elementor in the free version has its flaws. The most annoying one for me is the lack of Global Widgets. If I insert the same banner on 5 subpages and the client asks to change the background color – I have to go into each of those 5 pages and change it manually. In code, I would change one line of CSS. This is the moment where my programmer heart bleeds a little, but… clients love Elementor for the Live Preview. The ability to edit “live” is more important to them than code cleanliness under the hood.
Tip: I sometimes add the Royal Elementor Addons plugin to this set when I need something more non-standard than basic blocks.
Path 2: Complex Projects (Knowledge Bases, Catalogs)
What it is: Sites with a lot of content and a repetitive structure (e.g., product catalog, article database, Custom Post Types).
My choice: Custom Theme + ACF PRO.
I had the opportunity to work on a larger project with a large number of Custom Post Types. There, Elementor would have been a burden. In such a case, I bet on a Custom Theme (a theme written from scratch or a child theme) and the ACF PRO plugin.
Thanks to this, the client doesn’t have to build the page from blocks. They enter the editor, see dedicated fields (e.g., “Product Photo”, “Price”, “Technical Description”), fill them in, and they’re done. Everything displays perfectly evenly where I planned it in the code.
The downside? No Live Preview. The client has to click “Preview” to see the effect. For people used to visual builders (like Elementor), this can be less intuitive at first. However, for such complex services, it is a necessary compromise. We consciously give up “playing with the look” live in favor of stability, speed, and data security. This gives us certainty that the site structure remains intact, regardless of who enters the content.
And when do I give up on WordPress entirely?
One of my projects was a landing page for a technical client. They cared about maximum speed and security, and the page was to be a “one-off” (without planned content changes).
I proposed pure HTML.
Zero plugins to update.
Loading speed unattainable for CMSs.
Peace of mind (no vulnerability to WordPress attacks).
This shows that it’s worth being open-minded. I don’t force WordPress where it’s not needed, just because “everyone does it.”
My "First Aid Kit" (Plugins I test and implement)
As a technical person, I like to know what I’m installing. Here is the set that currently works in my projects:
Images: Converter for Media or Smush. Currently, I’m leaning towards Converter (a Polish solution, great configuration), but I’m still testing both solutions.
Languages: Polylang. Simple, works, doesn’t burden the site like combines such as WPML.
Backup: UpdraftPlus. Essential.
Security: Wordfence + WPS Hide Login. Basic protection against bots.
Forms: WPForms Lite. It is very intuitive for the end client.
SEO: Yoast SEO. A classic that simply gets the job done.
GDPR: Complianz.
What about Cache? In most of my projects (Kadence business cards), I use the free WP Fastest Cache. Minification and Gzip are completely sufficient for the site to run fast. For more complex projects (or when the client has a budget for optimization), I aim for WP Rocket. It gives much more control, but I assume there is no point in using a cannon to kill a fly for a simple business card site.
Summary: How do I make the choice?
I am just building my project base, but I know one thing for sure: there is no ideal stack. There is only a conscious choice of tool for a specific task.
My rule is simple:
If the site is to be a business card, and the client wants the freedom to move every element and see changes live ➔ I choose Elementor.
If the site is to be a catalog, knowledge base, or large service where data structure and stability matter ➔ I choose a Custom Theme.
I chose the middle path – combining the convenience of page builders with the technical awareness of a programmer.
And you? What do you use at the beginning of your journey? Kadence? Elementor? Or maybe you jump into the deep end with your own themes right away? Let me know!
