Writing · 20 November 2026

What I’d Still Check in an AI-Built Theme

A shop on a heavy page-builder theme can feel slow on a phone. The usual response is to add another speed plugin and hope it helps. Sometimes it does, for a while. Sometimes the better move is a leaner theme: one that only loads what the pages actually use.

AI has made that kind of custom theme more realistic to build quickly. It has not made it something you can put on a live WooCommerce site without reading the code.

I’ve already written about vibe coding a new theme for this site and dropping the page builder. That post is about my own site, and the scores it got. This one is about using the same approach for a WordPress or WooCommerce site, and the checks I still do afterwards. A fast theme that isn’t safe, or that the owner can’t edit, isn’t a finished job.

How I actually use AI to build a theme

I use Cursor heavily in my coding work. Vibe coding is a slightly daft name for a simple loop: I describe what I want, the AI writes the code, and I review it, test it and steer it. I’m not asking it to invent a shop while I look the other way.

What it changes is the time it takes to get a clean starting point. A custom classic theme, without a page builder and without a parent theme, used to feel like a long project before you even reached the product page. Now I can get the bones of it down quickly, then spend the real time on the parts that matter: WooCommerce, the bits a client will edit, and the review.

I wouldn’t rip a working page builder out for the sake of it. If you change your own pages every week and the site is fast enough, keep it. If the builder is carrying a lot of weight you don’t use, and the product page or checkout feels sluggish, a leaner theme is worth talking about.

The speed I can actually show you

I built the website for Strideora, a walking-groups app. The homepage scores 100 for Performance, Accessibility, Best Practices and SEO in Google PageSpeed Insights on mobile. That score comes from standard shared hosting, with no CDN in front of it and no page builder. It’s down to how the site is built. The theme is a custom classic WordPress theme, with no page builder and no parent theme, so the browser only downloads what the pages actually use.

I wouldn’t promise every site the same numbers. Strideora is the example I can point to, because it’s in my portfolio and those are the scores it has. What I will say is this: a lean theme removes a lot of the weight a page builder carries, and on a shop that weight often shows up where it hurts, on a phone, on the product page and at checkout.

I’ve also written about being paid to delete code rather than add more. Taking things out is often the same idea. A custom theme is one way of being deliberate about what gets to load.

What I still check

This is the part the AI doesn’t do for me.

Security. The first draft can look finished. I still look for capability checks, nonces on forms and admin requests, and anything that talks to the database or the filesystem. I wouldn’t put a theme on a live shop because it rendered nicely on a test site.

Sanitising and escaping. Input gets sanitised. Output gets escaped, in the right way for the context. AI misses this more often than you’d hope. A product title printed raw, a form field saved without a check, a URL built from a query string: those are the lines I read one by one.

WooCommerce template overrides. A custom shop theme often copies WooCommerce templates into the theme so the product page or cart can be redesigned. That’s fine when it’s deliberate and small. AI will sometimes copy a whole template when a hook, or a small change, would do. Those copies don’t update themselves when WooCommerce does. I keep a list of what’s overridden, I check it after WooCommerce updates, and I try not to override more than the shop actually needs. An out-of-date template is a quiet way to break checkout, or to miss a fix.

Maintainability. A theme I can come back to in six months, or that another developer can pick up, is part of the job. That means a clear file structure, no duplicated CSS, no mystery functions, and a short note where the behaviour isn’t obvious. If I’m the only person who understands it, I’ve built a bottleneck, not a website.

The client being able to edit content. A custom theme shouldn’t mean every typo waits for me. Headings, pages, product copy and the bits a shop owner changes every week should live in WordPress, in the editor, not hard-coded in a template. If the AI has baked yesterday’s wording into the theme, I take it back out. The design can be custom. The content still needs to be theirs.

When a lean theme is the right move

If your shop is slow, I start by looking at what’s actually loading, not by assuming the theme has to go. Sometimes the answer is taking things out of the setup you already have. Sometimes it is a custom theme, built quickly with AI and then checked properly, so you’re not carrying a page builder you barely use.

The test I care about is a phone. If the product page and checkout are sluggish there, it’s costing you sales, whether or not a speed plugin has already been added.

Wrap Up

AI can get a lean custom theme started quickly. The speed is real: Strideora is the example I can show you, with 100 across the board on mobile. The review is what makes it fit for a WordPress or WooCommerce site: security, sanitising and escaping, WooCommerce template overrides and how they’ll be kept up to date, whether someone else can maintain it, and whether you can still edit your own content.

If you’re wondering whether a heavy theme is what’s slowing your shop down, book a quick call and we’ll look at what’s actually loading, and whether a leaner theme would help.

Written by Connie, an AI, from Neil Matthews’ notes, archive, and direction. Neil directed and edited this piece. He did not write these words. Augmented publishing by Neil Matthews.

← All posts

Need help with your WooCommerce store?

Get a quote