WordPress Engineering
Hi, I'm Loz. I build WordPress and WooCommerce sites engineered for high performance and long-term stability.
WordPress is great. It's an easy way to get a site online and get your shop or message out into the world by picking a theme and stacking plugins until it does the job.
The problem is that when you build a site that way, you often end up with something that feels like wading through mud: slow, fragile, and heavy.
I take a different approach. I use WordPress as a familiar foundation for managing your content, but I abstract the frontend—meaning I separate the "engine" from the "bodywork"—to build sites that are lean, stable, and engineered to perform.
Let's talk
Start a projectMy approach to performance
WordPress was originally designed for blogging. It has since evolved into a powerhouse capable of running massive stores, but its foundation remains rooted in that original simplicity.
This creates a gap: the functionality is there, but performance is an after-thought. This is why so many sites feel heavy.
To bridge the gap between a blog and a store, people rely on general-purpose tools—specifically off-the-shelf themes and "all-in-one" plugins.
These are designed to work for everyone, which usually means they add a massive amount of unnecessary code and noise for the few features you actually need.
The "All-in-One" Theme
Off-the-shelf themes are often the biggest source of overhead. They ship with hundreds of layouts, styles, and functions designed to cater to every possible user.
Even if you only use a fraction of those features, the browser still has to load the weight of the rest. It's like buying a whole warehouse just to store a single box.
The Plugin Stack
A similar issue happens with plugins. Many are built to handle a thousand different edge cases rather than just the one specific task you need.
When you stack these together, you create a tangle of competing scripts that all try to run at once, creating a bottleneck that makes the site—and the shopping experience—feel like a chore.
My philosophy is simple: the best solution is the one that does exactly what is required and nothing more. I replace general-purpose noise with surgical, purpose-built code, ensuring your site operates with intention rather than just stacking tools until it "works."
How we can solve this
The Technical Cleanup
If you have an existing site that feels sluggish, I can perform a technical cleanup. I strip out redundant styles and scripts, tune the database, and resolve the bottlenecks that are dragging it down. This not only improves the user experience but ensures your site meets the technical criteria search engines look for.
The Engineered Build
For new projects or complete rebuilds, I treat the site as a software project rather than a configuration task. This means moving away from visual, drag-and-drop editors and instead focusing on a structured codebase.
I use Bedrock for project management and Twig for templating. This separation of logic and presentation ensures the site is maintainable and allows me to keep the frontend slick and focused only on what is necessary.
I use Advanced Custom Fields (ACF) to build a precise editing interface. This gives you a familiar way to manage your content in the dashboard, while ensuring the frontend is engineered for performance.
The Decoupled Architecture
For projects with the highest performance requirements, I separate the frontend entirely. I keep WordPress and WooCommerce for the backend management, but I build the actual user experience using the same methods I used to build this website. This transforms the site into a high-performance application that pulls data from WordPress in the background, ensuring the interface remains responsive and snappy.
High-performance search
Standard WordPress search works for small sites, but it struggles as soon as you have thousands of products. At that scale, the default search can feel clunky and lacks the precision needed to handle a large volume of data efficiently.
I can implement advanced search infrastructure using purpose-built services like Typesense. This provides a super-quick "search-as-you-type" experience—where results update instantly as the user searches.
It removes the frustration of a slow search and ensures your customers find exactly what they're looking for, without the wait.
This is TypeSense
Try searching for a , or in the search field below to see how quick your site search could be
How I work
I follow a structured process to ensure the final product is exactly what the business needs. But more importantly, I approach every project as an engineering task, not a configuration task. In practice, this means I'd rather write ten lines of code than use a plugin that adds thousands more. This ensures your site remains stable and maintainable for years to come.
- Discussion
- We start by talking through the project in detail to nail down exactly what problem we are solving and what the requirements are.
- Proposal
- Based on those conversations, I write up a clear proposal outlining the scope and the approach.
- Design
- If approved, I move into the design phase. I start with wireframes and then move into high-fidelity designs, so we both have a precise visual map of the product before any code is written.
- The Build
- Once the designs are signed off, I begin the build using the technology stack that is the ideal fit for the project. This is the most intensive phase, typically taking up about three-quarters of the total project timeline.
- Testing
- Before going live, I let you and a small selection of your team loose on the system to test it and make sure it operates exactly as expected in a real-world scenario.
- Support
- I provide continued support to ensure the project delivers everything promised in the original scope, followed by any agreed maintenance plan to keep the system stable.
I'm ready when you are
Your site should be a tool that works for you, not a source of frustration. If you're looking for a more professional, high-performance approach to WordPress, drop me a message and let's see if I can help.