Keeping a WordPress site light and easy to edit

WordPress gets blamed for a lot of slow, confusing websites. Fair enough, there are plenty of them. But in our experience the problem is rarely WordPress itself. It’s what gets piled on top: a theme that tries to do everything, a dozen plugins for small jobs and an editing screen nobody on the team understands.

A WordPress site can be light, fast and easy for a small team to update. It just takes some restraint when it’s built.

Where the weight comes from

Multipurpose themes

Many popular themes are built to be sold to everyone, so they include sliders, animations, icon libraries, several font sets and layout options for every kind of business. Much of that code loads on every page, whether your site uses it or not. Visitors pay for it in loading time, and every extra request uses a little more energy.

Plugin piles

Plugins are one of WordPress’s strengths, but each one is code someone has to trust, update and check for conflicts. It’s common to find sites with separate plugins for things the theme already does, or for small jobs a few lines of code could handle. Some add scripts and stylesheets to every page, even when they’re only needed on one.

Editing that’s easy to break

Some page builders give editors so many controls that changing a heading means wading through spacing, animation and colour settings. It’s easy to nudge something out of place, and over time the site drifts away from its design. A site that’s hard to edit tends to stop being edited.

Builders that help, used well

Visual site builders like Oxygen, Breakdance and Bricks take a different approach from the big multipurpose themes. They let a developer design the site directly, using a shared set of classes and styles, and they generally output fairly lean HTML and CSS. You build only what the site needs, rather than switching off what it doesn’t.

We use builders like these because they let us design something specific to each client while keeping the code tidy. But a builder isn’t automatically light. It’s still possible to build a heavy page with any of them, with oversized images, too many fonts and effects nobody asked for. The tool helps; the discipline still has to come from whoever’s building.

They’re not the right choice for every site, either. If your team wants to design new page layouts themselves, regularly, a builder-led site needs more care in how editing is set up. And a very simple site may be perfectly well served by a lightweight block theme and the standard editor.

How we keep sites light

• Set a page-weight budget at the start and check new pages against it.
• Use system fonts or one well-chosen web font family, with only the weights we need.
• Size and compress images properly, and lazy-load those below the fold.
• Load scripts only on the pages that need them, such as a map on the contact page or a form on the enquiry page.
• Question every plugin: does it do a real job, is it well maintained, and could the theme or a small snippet do the same?
• Use a reusable set of classes and colour variables so the design stays consistent as the site grows.

None of this is exotic. It’s mostly about saying no to things that seemed harmless one at a time.

How we keep sites easy to edit

Lightweight and easy to edit go together. A few principles we follow:

• Separate design from content. Layout lives in templates and components; editors change text, images and lists without touching spacing or styling.
• Use the standard WordPress editor for everyday writing, such as news posts and case studies, so editors get a familiar, simple screen.
• Use structured fields for repeated content, like team members or events, so each one is entered the same way and displays consistently.
• Keep the admin tidy. Hide menus and options editors don’t need, and give them a short guide written for their site, not WordPress in general.

Good accessibility comes from the same habits. Consistent headings, proper alt text fields and templates that produce semantic markup make it much harder for an editor to accidentally create a page that a screen reader user can’t navigate.

Our rule of thumb

If you’re looking at an existing WordPress site, three quick questions tell you a lot:

• How many plugins are active, and does anyone know what each one does?
• Does a simple page, like your contact page, load quickly on a phone with mobile data?
• Can the person who updates the site change a paragraph without help or fear of breaking something?

If the answers are “lots”, “not really” and “no”, there’s usually a lighter, calmer version of your site waiting to be built.

Where to start

You don’t always need a rebuild. Sometimes removing a few plugins, fixing images and tidying the editing screens makes a big difference. If you’d like to know whether your site needs a tune-up or a fresh start, read our earlier notes on choosing a CMS and setting a page-weight budget, look at our websites and content management work, or tell us what you’re working on.