coded-coffee-noteNo theme gets heavy on purpose. It happens one reasonable choice at a time: a CSS framework because the grid is quicker, jQuery because the slider needs it, a page builder so the client can edit, a broad query because it works. Each one is small. Together they’re the reason the site feels slow and fragile two years later.
A lightweight WordPress theme isn’t one with fewer features. It’s one where every layer has to earn its place, because every layer is paid for by someone: the visitor on a phone, the editor in the dashboard, and whoever maintains the site next.
How a theme gets heavy
Most of the weight comes from the same few layers, and each one was added for a good reason at the time:
| Layer | Why it gets added | What it costs later |
|---|---|---|
| CSS framework | A ready-made grid and components | Styles for every component ship on every page, used or not |
| jQuery | A slider or menu plugin depends on it | An extra library that loads before the scripts that need it |
| Page builder | Editors want control over layout | Extra wrappers and inline styles saved into every page’s content |
| Broad queries | The default arguments just work | Database work the page never uses, repeated on every visit |
| One big bundle | One file is simpler to enqueue | Every page downloads the code for every other page |
None of these is wrong on its own. The problem is that they’re rarely taken out again. jQuery still runs on roughly two-thirds of all websites, according to W3Techs, long after browsers made most of what it did native.
Why visitors pay for it
The web keeps getting heavier. The 2025 Web Almanac found that the median mobile home page grew from 845 KB in July 2015 to 2,362 KB in July 2025. A lot of that weight isn’t doing anything: the 2024 edition found that close to half of the median mobile page’s JavaScript goes unused.
Unused code isn’t free just because it doesn’t run. The phone still downloads it, and still has to parse it before the page can respond. On a developer’s laptop that’s invisible. On a mid-range phone on a patchy connection it’s the difference between a page that answers a tap and one that doesn’t, which is exactly what Core Web Vitals measure.
Why the site owner pays for it
Weight is the cost you can measure. The other costs show up in the maintenance budget:
- Every dependency is something to update. A plugin loads its own copy of a library, an update changes how it behaves, and something that worked yesterday doesn’t today.
- Layout saved in content is hard to change. When a page builder stores styling inside each page, a redesign means editing every page, not the theme.
- Freedom without limits breaks designs. An editor who can set any margin or colour eventually sets one that doesn’t fit, and someone has to fix it.
- Slow queries wait for traffic. A query that’s fine with ten visitors becomes the bottleneck on the day a campaign goes out.
A lean theme doesn’t remove these risks by being clever. It removes them by having less in it that can go wrong.
What lean actually means
Lean doesn’t mean plain. A lightweight theme can have sliders, forms, flexible layouts and editor control. It just gets them with less underneath, by following four habits:
- Write native first. Reach for plain CSS and JavaScript, and add a library only when native genuinely can’t do the job.
- Ask for only what the page shows. Every query should fetch what the template uses and nothing else.
- Give editors choices, not raw values. Let them pick sections and layout options the theme defines, so the stylesheet stays in charge of the design.
- Ship code where it’s used. Each page loads the scripts and styles its own sections need, not the whole site’s.
Each habit has its own recipe. Fast Pages from ACF Flexible Content covers editor choices, Enqueue Only What You Serve covers per-page loading, and Gravity Forms Without jQuery shows native code replacing a library in a real plugin.
Before you ship
- Every library in the theme has a job you can name, and native code couldn’t do it.
- No page loads code that only another page uses.
- Editors can’t save layout or styling that bypasses the stylesheet.
- Front-end queries were checked against what the template actually shows.
- A mobile test is saved from before and after, so the change can be shown.
Every layer is paid for by someone. Make sure it’s earning its place. The house rule