Liverton Security · 2025
A site the team can update themselves, without waiting on anyone.
Liverton’s WordPress site had grown clunky under layers of plugins, and the team found it hard to keep current. Now they build and publish pages on their own.
The site had become something to wrestle with
Liverton’s marketing site ran on WordPress, and over the years it had picked up layer after layer of plugins. Each one added weight, another thing that could break, and another thing to keep patched. Almost all WordPress security holes are found in plugins, not WordPress itself, and for a security company that’s an awkward thing to be running on.
The result was a site that was slow and awkward to change. A small edit could mean fighting a page builder or calling in help, so things that should have taken minutes did not get done. The team had stopped enjoying using it.
What I built
A headless rebuild in Payload CMS, made to fit how Liverton works. When they needed the site to do something specific, I built it for them directly, instead of bending a plugin into shape or working around what WordPress allows.
- Pages built from blocks
- The team assembles pages from a set of content blocks: hero, text, gallery, call to action. No code, no theme files, no fighting a page builder plugin.
- Preview before it goes live
- Drafts can be previewed exactly as they will look, so the team checks a page before anyone else sees it. No publishing and hoping.
- Set up for search
- Clean markup, fast pages, and proper metadata throughout. The things search engines reward are part of the build, not bolted on through yet another plugin.
- Fast by default
- A headless build with nothing extra bolted on. No plugin stack to slow it down, so pages load quickly and stay that way.
The result
A fast site the team is happy to work in. The changes that used to stall now go live the same day, by the people who need them done.
- WordPress weighed down by plugins
- A lean headless build in Payload CMS
- Slow under layers of add-ons
- Fast by default, nothing extra loaded
- Every edit waited on a developer
- The team publishes on its own
- Hard to keep up to date
- Pages assembled from blocks in minutes
- A plugin stack to keep patched
- Nothing to patch, nothing to exploit
Replacing a WordPress site?
If yours is slow, hard to edit, or buried under plugins, I can tell you what a rebuild would involve.