More insights.
Subscribe to our newsletter.
Deep dives into design thinking, creative process, and the intersection of business and aesthetics.
A WordPress site is only as good as the discipline that went into building it.
If your WordPress site is slow, awkward to edit or forever nagging about updates, someone has probably told you the answer is a rebuild on something newer. It’s fashionable among agencies to knock WordPress as slow and full of security holes. Most of what they’re describing is a build problem, and blaming the platform is easier than owning that.
WordPress does not become slow simply because it is WordPress. A slow WordPress site can reflect problems with hosting, code, images or third-party services. Measure the actual bottleneck before recommending a change of platform.
The theme you start from sets the ceiling
A lot of poor WordPress sites begin with a multipurpose theme, the cheap kind from a marketplace that promises e-commerce, portfolios, forums and bookings all in one. It loads a heap of code on every page, most of it never used. You can optimise around it and still hit a limit, because the foundation is carrying weight it doesn’t need.
A lightweight foundation helps, but custom code alone does not establish quality. Ask the supplier to show how a representative page loads, how the team edits it and how changes are tested before publication.
Every plugin is code someone has to maintain
The quickest fix for almost anything in WordPress is a plugin, whether it’s a contact form or something as small as changing a font. Keep going and the list gets long: plugins start competing for resources and conflicting with each other, and every one is third-party code that needs updating and offers another possible way in.
A plugin and a custom feature both create maintenance responsibilities. Choose the approach that meets the requirement with a clear owner, a support route and a workable update process. A small plugin count is not a substitute for that assessment.
Security is a maintenance job
A WordPress site left on cheap shared hosting, with updates piling up and nobody checking it, is a front door left open, and you can’t blame the house for that.
Looking after it properly starts with managed hosting and a staging copy of the site. We test updates there before they go anywhere near the live one. And if an update breaks something, there has to be a quick way back to the last working version.
Your team should be able to edit without breaking anything
The admin side deserves as much design thought as the front end. A marketing team shouldn’t be wrestling with shortcodes, or knocking a layout out of shape because they pasted in a longer headline. We use structured content blocks: you fill in the headline field and the block handles how it looks on a phone or a wide screen, so people can publish quickly without worrying about the design.
Four questions for whoever builds or runs your WordPress site
Ask these whether an agency is proposing a new WordPress site or already looks after yours:
Why is this theme or foundation suitable for our content and editing needs? Ask for a demonstration using a representative page, rather than treating custom code or a purchased theme as proof of quality.
How do you handle plugin conflicts? The answer should involve a staging site.
How many plugins does the site run, and what does each one do? A good agency can justify every one.
What mobile field data and repeatable lab tests can you show? Ask what was measured, when, under which conditions and what still needs improvement.
For a reference that isn’t an agency’s opinion, WordPress publishes its own performance optimisation handbook. It’s written for developers, but a skim will tell you whether the answers you’re getting are specific or just reassuring. If they’re vague about your current site, fix the build before you pay to replace the platform.
WordPress or Framer: test the work your team needs to do
Start with the tasks, then choose the platform. A visual marketing website, a publishing operation and a site with complex account or booking requirements may need different foundations. The recommendation should follow the content model, connections and people responsible for the site.
Decision | Platform questions |
|---|---|
Editing | WordPress: show the editor roles, content fields and approval process. Framer: show CMS editing, page changes and the publishing process. |
Connections | WordPress: name the plugins or code, their owner and update process. Framer: demonstrate each required connection and its support route. |
Ongoing care | WordPress: identify hosting, backups, updates and recovery responsibility. Framer: identify the platform plan and care for custom code and external tools. |
Handover | WordPress: test content export, access transfer and a recoverable site backup. Framer: test content and site-output export, access transfer and what works after a move. |
Use the same editing trial for both proposals
Ask the person who will maintain the website to add a project, replace an image, edit a service heading and check the result on a phone. Then ask them to correct a mistake. Record which steps they can complete, which need a developer and who can approve or publish a change. A demonstration using your content is more useful than a tour of an empty dashboard.
Agree ownership, recurring costs and an exit plan
Put the domain, project access, content, design assets, licences and external accounts on the handover list. Ask for an actual export and explain what it preserves: published output, structured content and an editable working project are different things. If moving provider is important, test that route before signing off the platform.
Separate the build fee from hosting, platform subscriptions, paid plugins, integration services and ongoing support. Confirm the current plan and limits against the official documentation when the proposal is prepared. State who tests accessibility and performance, who fixes integration failures and who can restore a working version.
WordPress documents routine site maintenance. Framer documents content and site-data portability. Use those primary sources as a starting point, then ask the supplier to demonstrate the proposed arrangement for your project.
Our website design service starts with these delivery decisions. For a technical content brief, review the scope described in the SCS Precision Components case study. Use it to discuss how detailed product information, brand presentation and content ownership would work in your own brief.
Related Brainstorm services and work
WordPress and CMS development · Web design across Ireland · Discuss a WordPress rebuild
Updated 16 October 2026. Dave Curtin, founder and Creative Director of Brainstorm, leads website strategy, brand direction and technical delivery for Brainstorm clients.
A WordPress site is only as good as the discipline that went into building it.
If your WordPress site is slow, awkward to edit or forever nagging about updates, someone has probably told you the answer is a rebuild on something newer. It’s fashionable among agencies to knock WordPress as slow and full of security holes. Most of what they’re describing is a build problem, and blaming the platform is easier than owning that.
WordPress does not become slow simply because it is WordPress. A slow WordPress site can reflect problems with hosting, code, images or third-party services. Measure the actual bottleneck before recommending a change of platform.
The theme you start from sets the ceiling
A lot of poor WordPress sites begin with a multipurpose theme, the cheap kind from a marketplace that promises e-commerce, portfolios, forums and bookings all in one. It loads a heap of code on every page, most of it never used. You can optimise around it and still hit a limit, because the foundation is carrying weight it doesn’t need.
A lightweight foundation helps, but custom code alone does not establish quality. Ask the supplier to show how a representative page loads, how the team edits it and how changes are tested before publication.
Every plugin is code someone has to maintain
The quickest fix for almost anything in WordPress is a plugin, whether it’s a contact form or something as small as changing a font. Keep going and the list gets long: plugins start competing for resources and conflicting with each other, and every one is third-party code that needs updating and offers another possible way in.
A plugin and a custom feature both create maintenance responsibilities. Choose the approach that meets the requirement with a clear owner, a support route and a workable update process. A small plugin count is not a substitute for that assessment.
Security is a maintenance job
A WordPress site left on cheap shared hosting, with updates piling up and nobody checking it, is a front door left open, and you can’t blame the house for that.
Looking after it properly starts with managed hosting and a staging copy of the site. We test updates there before they go anywhere near the live one. And if an update breaks something, there has to be a quick way back to the last working version.
Your team should be able to edit without breaking anything
The admin side deserves as much design thought as the front end. A marketing team shouldn’t be wrestling with shortcodes, or knocking a layout out of shape because they pasted in a longer headline. We use structured content blocks: you fill in the headline field and the block handles how it looks on a phone or a wide screen, so people can publish quickly without worrying about the design.
Four questions for whoever builds or runs your WordPress site
Ask these whether an agency is proposing a new WordPress site or already looks after yours:
Why is this theme or foundation suitable for our content and editing needs? Ask for a demonstration using a representative page, rather than treating custom code or a purchased theme as proof of quality.
How do you handle plugin conflicts? The answer should involve a staging site.
How many plugins does the site run, and what does each one do? A good agency can justify every one.
What mobile field data and repeatable lab tests can you show? Ask what was measured, when, under which conditions and what still needs improvement.
For a reference that isn’t an agency’s opinion, WordPress publishes its own performance optimisation handbook. It’s written for developers, but a skim will tell you whether the answers you’re getting are specific or just reassuring. If they’re vague about your current site, fix the build before you pay to replace the platform.
WordPress or Framer: test the work your team needs to do
Start with the tasks, then choose the platform. A visual marketing website, a publishing operation and a site with complex account or booking requirements may need different foundations. The recommendation should follow the content model, connections and people responsible for the site.
Decision | Platform questions |
|---|---|
Editing | WordPress: show the editor roles, content fields and approval process. Framer: show CMS editing, page changes and the publishing process. |
Connections | WordPress: name the plugins or code, their owner and update process. Framer: demonstrate each required connection and its support route. |
Ongoing care | WordPress: identify hosting, backups, updates and recovery responsibility. Framer: identify the platform plan and care for custom code and external tools. |
Handover | WordPress: test content export, access transfer and a recoverable site backup. Framer: test content and site-output export, access transfer and what works after a move. |
Use the same editing trial for both proposals
Ask the person who will maintain the website to add a project, replace an image, edit a service heading and check the result on a phone. Then ask them to correct a mistake. Record which steps they can complete, which need a developer and who can approve or publish a change. A demonstration using your content is more useful than a tour of an empty dashboard.
Agree ownership, recurring costs and an exit plan
Put the domain, project access, content, design assets, licences and external accounts on the handover list. Ask for an actual export and explain what it preserves: published output, structured content and an editable working project are different things. If moving provider is important, test that route before signing off the platform.
Separate the build fee from hosting, platform subscriptions, paid plugins, integration services and ongoing support. Confirm the current plan and limits against the official documentation when the proposal is prepared. State who tests accessibility and performance, who fixes integration failures and who can restore a working version.
WordPress documents routine site maintenance. Framer documents content and site-data portability. Use those primary sources as a starting point, then ask the supplier to demonstrate the proposed arrangement for your project.
Our website design service starts with these delivery decisions. For a technical content brief, review the scope described in the SCS Precision Components case study. Use it to discuss how detailed product information, brand presentation and content ownership would work in your own brief.
Related Brainstorm services and work
WordPress and CMS development · Web design across Ireland · Discuss a WordPress rebuild
Updated 16 October 2026. Dave Curtin, founder and Creative Director of Brainstorm, leads website strategy, brand direction and technical delivery for Brainstorm clients.