Static websites: why wealth firms do not need WordPress, and why it is safer
A wealth manager's website changes slowly and must never be the weak point. Here is what a static website is, why it is safer than a typical CMS, and when a CMS still makes sense.
Most wealth managers, family offices and external asset managers do not need a content management system running behind their website. Their pages change a few times a month at most: a new team member, a quarterly letter, an updated notice. Yet many of these websites sit on WordPress or a similar platform, with a database, a login page and a collection of plugins that all need constant attention.
For a firm whose reputation rests on discretion and care, that is an unnecessary exposure. A static website does the same job with far fewer moving parts.
What “static” actually means
A static website is a set of finished files: HTML pages, stylesheets, images and a small amount of JavaScript. They are prepared in advance, then placed on a hosting service that simply hands them to each visitor.
A typical CMS works differently. Every time someone opens a page, software on the server reads from a database, assembles the page and sends it out. That software is always running, always reachable from the internet and always able to accept input.
The difference is not visible to your clients. Both kinds of website can look identical. The difference lies in what an attacker can reach.
The attack surface of a typical CMS
A CMS is a capable piece of software, but its flexibility comes with a long list of things that must stay secure at all times:
- Plugins and themes. Most WordPress sites rely on third-party plugins for forms, galleries, SEO and caching. Each is written by a different developer, updated on a different schedule and occasionally abandoned. Vulnerabilities in plugins are among the most common ways such sites are compromised.
- An admin login on the public internet. The login page is usually at a predictable address, which invites automated password guessing. Strong passwords and two-factor authentication help, but the door is still there.
- A database. Content, user accounts and settings live in a database that the website queries on every request. A flaw that lets an attacker influence those queries can expose or alter data.
- The update burden. The core software, the plugins, the theme and the server’s own language runtime all need updating. Updates sometimes break each other, so they are often postponed, and a postponed update is an open window.
None of this means a CMS is inherently unsafe. It means it needs continuous, competent maintenance, and that a lapse of a few weeks can matter.
What a static website removes
A static website has no database to query, no plugins executing on the server and no admin login exposed to the internet. There is no application on the live site that processes input in order to build pages.
That removes the most common routes attackers use, rather than defending them. What remains is a much smaller list: the hosting account, the domain and its DNS records, any third-party scripts on the page and the small function that handles the contact form. Each of those is still worth protecting carefully, with strong authentication and limited access, but it is a short list that a small team can genuinely keep under control.
Security headers, HTTPS everywhere and a strict limit on third-party scripts complete the picture. No website is beyond attack, and nobody should promise otherwise, but a static site starts from a far stronger position.
Speed, and hosting on a global network
Because the pages are already built, a static website is fast. There is no waiting while a server assembles each page.
Static files are also well suited to hosting on a global content delivery network. Copies of the site are held in data centres around the world, so a prospect in Zurich, London or Singapore receives pages from a location near them. Such networks are built to absorb sudden traffic and typically include protection against denial-of-service attacks.
Speed is not a vanity measure here. A prospect introduced by a client is forming an impression of your firm, and a page that appears instantly on a phone between meetings reflects well on the care you take elsewhere.
How content still gets edited
The usual objection is that a static website is hard to update. In practice there are two straightforward routes:
- Your care team makes the changes. You send a new bio, a revised notice or this quarter’s commentary, the team prepares it, you and your compliance officer approve the wording, and the site is rebuilt and published. For most wealth firms, this is the simplest arrangement and it keeps an approval step in place by design.
- A lightweight editor. Where your own team prefers to publish directly, a simple editing interface can be set up that writes content into the site’s source files. It sits apart from the live website, so editing access does not create a login on the public site, and every change can be reviewed before it goes live.
Either way, there is a clear record of what changed and when, and an earlier version can be restored if needed.
Forms without a server to look after
Contact forms are the one place where a website must accept input. On a static site this is handled by a small server function: a few lines of code that run only when someone submits the form, check it and pass the message on.
That function can include bot protection, such as a privacy-conscious challenge that filters automated submissions without asking visitors to identify traffic lights. It should collect only what is genuinely needed, send it over HTTPS and avoid storing sensitive details in the website itself. Your privacy notice should describe what is collected and why, in wording your data-protection officer or lawyer has approved.
When a CMS still makes sense
To be fair to WordPress and its peers, there are situations where a CMS is the right choice:
- A large editorial team publishing several pieces every day.
- Complex, member-only areas with many user accounts and permissions.
- E-commerce or extensive interactive features built on existing plugins.
- An organisation with an in-house team already maintaining a CMS well.
Few wealth managers or family offices fit those descriptions. If yours does, the answer is a CMS that is maintained properly, with a clear owner for updates and security, rather than a static site forced into a role it does not suit.
A short checklist
If you are reviewing your current website, these questions are a useful start:
- Is there an admin login page reachable from the public internet?
- How many plugins or extensions does the site use, and who updates them?
- When were the core software and plugins last updated?
- How often does your content actually change, and who makes those changes?
- Who approves wording before it is published?
- Where are contact form submissions sent, and are any stored on the website?
- Which third-party scripts load on each page, and are they all still needed?
In closing
For most wealth firms, a website is a place to be understood, not a platform to be administered. A static website gives you a fast, calm presence with a much smaller security burden, while content still changes whenever you need it to. If you would like to see how that might look for your firm, our approach is described under websites for wealth managers.