Who this is for
Owners and small teams whose WordPress site or WooCommerce store is live and matters to the business, and who have run out of plugins to try: a theme that loads slowly because of the page builder under it, a checkout that fails for some payment methods, a product import that takes the site down, a hack that keeps coming back.
I have built WordPress sites since my freelance years and this site is one of them: a theme written without a page builder or an SEO plugin, with four languages, structured data and a contact form in the theme itself. WooCommerce stores get the same engineering I apply to Magento: read the request path, fix at the source, keep a staging copy.
Typical situations
- The site scores red on Core Web Vitals and the page builder is the reason, but rebuilding the theme feels too big.
- WooCommerce orders fail for one payment method, or stock goes negative after a busy day.
- A product import or a sync with an ERP or a marketplace duplicates products or silently drops prices.
- Thirty plugins, three of them abandoned, and nobody knows which one is slowing the site down.
- The site was hacked, cleaned by a plugin, and infected again a month later.
- A multilingual setup where translations, hreflang and the sitemap no longer agree.
What I deliver
- Custom themes without a page builder: block-based, fast, with the design in CSS and the structured data, sitemap and meta tags in the theme rather than in plugins.
- WooCommerce checkout, payment and shipping work: gateway integrations, Stripe, order status flows and webhook receivers that cope with duplicates and retries.
- Imports and syncs with ERPs, marketplaces and feeds that validate before writing and log every run.
- Performance along the request path: caching, PHP-FPM, database queries, images, fonts and the plugins that fire on every page, measured before and after.
- Security cleanup after an incident: finding the entry point, removing backdoors and rogue users, hardening, and a backup and restore routine that is tested.
- Custom plugins when the directory has nothing that fits, written to survive core and WooCommerce updates.
How it goes
Read the site as a request sees it. Plugins, theme, queries, caching, the server and the logs. The first output is a list of causes with evidence, ordered by impact, and a note on which plugins carry weight and which can go.
Fix at the source on a staging copy. Theme and plugin changes go into version control and are tested on a copy with real content before release, with a rollback path.
Release, then write it down. Monitoring on during the release; afterwards a short document on what changed, what to watch and the update routine going forward.