INDEPENDENT / WORDPRESS / PRACTICAL
I build websites, but I usually start with the problem behind them.
I’m Mihai Dumitrescu, an independent WordPress and WooCommerce specialist working with businesses and agencies on new websites, existing projects and the technical problems that tend to appear somewhere in between.
I have been working with websites for more than a decade. Over time, that has meant development, performance, SEO, e-commerce, migrations, troubleshooting and quite a lot of figuring out why something that “should work” does not.
What interests me most is not adding more technology. It is making the website more useful.
01
HOW I GOT HERE
More than 10 years working on the parts of websites that actually affect the business.
10+ YEARS
My work has gradually moved across several areas of the web rather than staying inside one narrow job description.
SEO taught me to think about how a website is found. Performance work taught me to look below the visible page. WordPress development made structure and maintainability important. WooCommerce added products, orders, payments, shipping and all the wonderfully inconvenient things that happen when a website starts handling real transactions.
That combination is useful because website problems rarely respect department boundaries.
A slow WooCommerce store may have a development problem, a database problem and a conversion problem at the same time. A local business website may need better structure before any amount of SEO work becomes useful.
I prefer understanding those connections to treating every symptom as a separate service.
02
HOW I WORK
I would rather understand the problem before choosing the tool.
I like WordPress because it can be simple when the project is allowed to remain simple.
I prefer native WordPress and Gutenberg where they are a good fit, and I try to avoid adding layers of plugins, frameworks or custom code unless they solve a real requirement.
That does not mean every site should be minimal. A WooCommerce store with complex product data, shipping integrations and customer workflows is genuinely more complicated than a five-page company website. The implementation should reflect that difference instead of forcing every project into the same stack.
The same applies when I inherit an existing website. I do not assume that rebuilding it is automatically better than understanding what is already there.
03
PERFORMANCE, SEO AND DEVELOPMENT
A website should not need three different explanations for the same problem.
Performance, SEO and development are often sold as separate services, but in practice they overlap constantly.
A huge image is a development and performance problem. Poor page structure can affect usability and search visibility. A badly designed product taxonomy can make a WooCommerce store harder to use, harder to maintain and harder for search engines to understand.
I try to account for those connections while building rather than waiting until the end and attaching an optimisation phase to whatever already exists.
That approach is also why I care about measurable performance, but not performance theatre. A perfect score on an empty page is considerably less interesting than a fast real website doing useful work.
04
INDEPENDENT, NOT ISOLATED
I work directly with businesses and alongside agency teams.
Some projects begin with a business owner who needs a website built or fixed. Others come through an agency that needs additional WordPress capacity for a project or a busy period.
I am comfortable with both.
With direct clients, I can translate technical decisions into practical ones without expecting them to learn WordPress terminology first.
With agencies, I can work inside an existing process, take responsibility for a defined part of the project and remain behind the scenes where white-label support makes sense.
In either case, I value clear communication and being realistic about what can and cannot be delivered.
05
WHAT I CARE ABOUT
Useful over impressive
A website exists to do something. The design and technology should support that job.
Simple where possible
Complexity has a cost long after the initial build. I prefer not to add it without a reason.
Measurable where it matters
Performance, search visibility and technical health are easier to improve when they are measured instead of guessed.
Maintainable after handover
A website should still make sense when somebody else needs to edit it six months later.
06
TESTIMONIAL
A long-term working relationship beats a clever handoff.
“I’ve worked with Mihai for years, and he has a rare ability to make complex things feel simple. He is practical, reliable and always focused on what genuinely helps the business. Over time, he became not only someone I trusted professionally, but also a friend.”
Jess Truman
LET’S WORK TOGETHER
Need someone to build it, improve it or figure out what is going wrong?
Tell me what you are working on.