Web Design

WordPress Is Losing Market Share. That Does Not Mean You Should Leave It.

WordPress is a smaller share of the web than it was. For a business whose marketing team needs to edit the site, leaving it can cost more than staying. Here is the real trade, including the plugins, PHP, and updates WordPress still requires.

November 18, 2026 · 22 min read · DRVN Media

A laptop on a desk showing a content editor beside a notebook and a coffee cup

WordPress runs less of the web than it did a few years ago. That is a real trend, and it gets used as a reason to rebuild. Sometimes the rebuild is right. Often it is not, especially when the people who need the site day to day are a marketing team, not a developer.

This is the trade. WordPress is heavier than a static site. It has plugins, a database, PHP, and a stack of updates that do not take care of themselves. It is also the thing a marketer can log into on a Tuesday and change a headline, add a landing page, or publish a post without filing a ticket. Those two facts are the whole decision.

We build on more than one stack. A lead-generation site does not have to be WordPress. A site a marketing team has to live in often should be. The rest of this post is how to tell which one you have, and what staying actually costs.

If you want the design side of a site that ranks and converts, that is website design best practices. If you want the ongoing work a WordPress site needs, that is DRVN Web Care.

What “losing market share” actually means

WordPress still powers a large share of the public web. The share has been drifting down. Newer sites are more often built on hosted builders, on static generators, or on a platform the company already pays for. Some of that is real competition. Some of it is the long tail of abandoned sites and one-page experiments that were never going to stay on WordPress anyway.

A declining share is not the same as a dying product. It is a signal that the default has more rivals. For a business choosing a platform in 2026, the useful question is not “is WordPress the biggest.” It is “does this platform fit the people who have to use it, and can we keep it safe.”

The articles that treat the share number as a verdict skip that question. A marketing team does not care what percentage of the internet runs on a given stack. They care whether they can ship a campaign page this week.

Who actually touches the site

Before you pick a platform, write down who edits the site in a normal month.

If the answer is a developer, or an agency, and the edits are rare, you have options. A static site, a headless build, a custom front end. Fast, simple to host, little to update. We build those. They are a good fit when the site is a set of pages that change when a project changes, not when a campaign does.

If the answer is a marketing coordinator, a content person, or an owner who posts the weekly special, the calculus changes. They need a login, a visual editor, reusable blocks, and a way to add a page without breaking the layout. WordPress still does that better than most of the alternatives a small team will actually learn.

This is the part the rebuild pitches leave out. The new stack is faster. It is also a black box to the person who used to update the hours, add a provider, or duplicate last month’s landing page. The speed gain is real. The bottleneck moves from the server to the calendar of whoever can now make the change.

Not sure the stack fits the team? Tell us who edits the site and what they change. We'll say whether to stay or move.

Get a Project Quote →

What a marketing team actually needs

A marketing team does not need a theme. They need a few specific things.

They need to change copy without a deploy. A headline, a price, a bio, an announcement. If that requires a pull request, it will not happen on the day it matters.

They need to add a page. A campaign, a new service, a location, a post. The page should look like the rest of the site without them designing it. Blocks, or a small set of templates, do that. A blank canvas does not.

They need images they can swap. A new photo of the crew, a new provider headshot, a menu. Upload, crop, done.

They need forms they can point at. A quote form, a booking link, a download. Not a new integration every time.

They need to see what they changed. A preview. A draft. A way to undo.

WordPress, set up with a tight set of blocks and a role that cannot install plugins, covers this. So do a few hosted builders. A custom static site covers it only if you also build them an editor, which is a second project. That second project is often where the “simpler stack” stops being simpler. If the real need is an internal tool rather than a marketing site, that is custom software, and it should be scoped as software, not as a website.

The cost of leaving

Leaving WordPress has a real cost that does not show up in a performance score.

Content has to move. Pages, posts, images, redirects. A sloppy migration drops URLs that already rank. A careful one maps every URL and keeps the links. That is part of a redesign when we do one, and it is the part that protects the search equity you already have. Local SEO starts with the site. Throwing away the URLs throws away some of that.

The team has to relearn the editor. The first month is slow. The person who knew the old shortcuts is now waiting on someone else.

Plugins you relied on have to be replaced. Forms, SEO fields, redirects, a booking embed, a review widget. Some have equivalents. Some were doing a job you now have to build.

The marketing site and the ads have to be repointed. Landing page URLs, pixels, call tracking. Miss one and a campaign reports zero for a week.

None of this is a reason to stay forever. It is a reason to move when the benefit is larger than this cost, not because a chart said the share went down.

What staying actually requires

This is the part people skip when they defend WordPress, and it is the part that makes a neglected WordPress site a liability.

WordPress is software. It runs on PHP. It uses a database. It is extended by plugins and a theme. Every one of those has versions, and versions have security fixes.

Core updates. WordPress itself ships updates. Most are safe to apply. Some need a look, especially when a major version changes the editor or a function a plugin depends on.

PHP updates. The server runs a version of PHP. Old PHP is a security problem and, eventually, a compatibility problem. Hosts drop old versions. A site that has not moved PHP in years will one day refuse to boot, usually on a Friday.

Plugin updates. This is where WordPress sites get hurt. A plugin that is abandoned, a plugin that breaks on update, a plugin you no longer need but never removed. Every plugin is code that runs on your site. Fewer is safer. Updated is safer than pinned to a version from 2021.

Theme updates. A theme from a marketplace has its own release cycle. A custom theme has whatever you built. Either way, the theme is code.

Backups. Before an update, and on a schedule. Offsite. A backup on the same server as the site is not a backup when the server goes.

Uptime and malware. A WordPress site that is not watched will eventually have a problem. A scan, a lock on the login, and someone who notices when it is down. This is the work in DRVN Web Care: core, PHP, plugins, monitoring, weekly offsite backups, malware scanning and removal, and a set number of hours for the changes you ask for.

Staying on WordPress is reasonable. Staying on WordPress with no one responsible for updates is how sites get compromised. The platform is not the risk. The unowned stack is.

Want the updates handled? Web Care covers core, plugins, PHP, backups, and monitoring. You do not have to touch the site.

Get a Project Quote →

Plugins are a feature and a liability

The plugin directory is why marketing teams like WordPress. Forms, SEO, redirects, sliders, booking, membership, a landing page builder. Almost anything has a plugin.

It is also why WordPress sites get slow and why they get broken into. A site with 40 plugins has 40 update schedules and 40 possible conflicts. A site with 8, chosen on purpose, is a different machine.

The rule we use: install a plugin when it does a job you would otherwise have to build, and when it is maintained. Remove the ones you are not using. Do not install a plugin to do something the theme or a block already does. Do not install two plugins that do the same job.

A page builder on top of a theme on top of a builder is how you get a site no one can edit and no one can speed up. Pick one way to lay out a page. Teach the team that way. Stop.

If a plugin is abandoned, replace it before you need the feature on a deadline. An abandoned plugin is a future security note.

PHP, the database, and the host

WordPress is not a file you upload and forget. It is an application.

PHP is the language it runs on. The version matters. A current, supported version is the baseline. When a host forces an upgrade, the site should already be compatible. That means plugins and the theme are current enough to run on it. Finding that out the week of the cutoff is how launches slip.

The database holds the content. It needs backups. It needs to not be exposed. It is the reason a WordPress site is more moving parts than a folder of HTML.

The host matters more than the theme. A cheap shared host with no staging and no backups will make every update a gamble. A host with staging, automatic backups, and a current PHP version makes the maintenance boring, which is what you want. We do not resell hosting as the product. We do make sure the site we maintain is somewhere the maintenance is possible.

When you should leave

There are good reasons to move off WordPress.

The site is a simple set of pages, the team does not edit it, and you want it fast and hard to break. A static build is a better fit. Less to update. Less to attack.

The site has become a pile of plugins that fight each other, and the cost of unwinding it is close to the cost of a clean build. Sometimes a rebuild is the cheaper cleanup.

You need something WordPress is bad at. A logged-in product, a complex app, a workflow that is really software. Build the software. Do not stretch the CMS until it is neither a good site nor a good app. That line is custom software versus off the shelf.

The current site is compromised and the theme and plugins are beyond a clean restore. A new build, with the content moved and the URLs redirected, is often faster than a forensic cleanup.

None of these is “WordPress lost two points of market share.” That is not a reason. The reason is the fit, the maintenance, or the mess.

When you should stay

Stay when the marketing team is in the site every week and the current setup, cleaned up, can keep serving them.

Stay when the content is large and the URLs rank. A move is a project. Staying and fixing the slow template, the extra plugins, and the update habit is often the better project.

Stay when the alternative is a builder the team will outgrow in a year, or a custom stack no one on the team can touch. You have traded one dependency for a sharper one.

Stay when you can name the person, or the plan, that owns updates. If that name is Web Care, the site can stay WordPress and the team can stay in the editor. If that name is no one, do not stay. Fix the ownership first.

A cleanup before you decide

If you are unsure, do not rebuild yet. Clean the current site and see what you have.

Remove plugins you do not use. Update the ones you do. Update core. Check PHP. Measure the homepage on a phone. Look at who has an admin login and remove the ones who left. Turn on a backup if you do not have one. Put a real staging step in front of updates.

Then ask the marketing team what they could not do last month. If the answer is “nothing, it was fine,” you have a maintenance problem, not a platform problem. If the answer is a list of things the editor cannot do, you have a design problem. That might be a conversion fix or a rebuild. It is still not automatically a new platform.

A free website audit will show the speed, the first screen, and the obvious leaks. It will not inventory your plugins. If you want that, say so and we will look.

Want a straight answer on the stack? Tell us the site, who edits it, and what is breaking. We'll tell you whether to clean it or replace it.

Get a Project Quote →

How we build when WordPress is the right call

When we build on WordPress, we build it like a product with a small surface, not like a theme with everything turned on.

A small set of blocks. The ones the team will use. Not a library of 80. The homepage, the service pages, a landing page pattern, a post. That is usually enough. The structure follows what a lead-generation site actually needs: one action, a clear first screen, pages for the services that should rank.

Roles. A marketer can edit and publish. They cannot install plugins or edit code. That one setting prevents most of the “someone added a plugin and the site broke” stories.

SEO fields and a clean title pattern. Internal links in the content, the way we describe in the design best practices post. The platform does not do this for you. The build does.

Performance. Images sized correctly. No builder on top of a builder. Caching that does not break the editor. A WordPress site can be fast. Most are not, because of what was added, not because of WordPress.

Forms that go somewhere a person reads. The same lead path as the rest of our sites.

Then a plan for the updates. If we are not on a care plan, we still leave the site in a state where updates are possible: current PHP, current plugins, a backup, a note on what is installed and why.

How we build when it is not

When WordPress is the wrong call, we say so. A static or custom front end, with the pages the business needs and a path for the few edits that happen. If the team later needs an editor, we add one on purpose. We do not start with the heaviest option because it is familiar.

The design standards do not change with the stack. The first screen, the service pages, the internal links, the phone number that matches the Google Business Profile. Platform is a means. The job of the site is the point. That job is usually a call or a form, which is what a website design project is scoped around.

The maintenance calendar, if you stay

If you keep WordPress, someone owns this list.

Weekly: a look at uptime and a backup you could actually restore. A scan, or a host that scans.

Monthly: plugin and theme updates on staging, then production. Core updates when they are out. A check that the forms still send and the homepage still loads fast.

Quarterly: PHP version against what the host will support next. A review of plugins you can remove. A look at admin users.

When something breaks: a person who can roll back, not a thread of guesses.

That is a small amount of work and it is the difference between a WordPress site that runs for years and one that becomes an incident. It is also exactly what a care plan is for. The hours in the plan cover the changes the team asks for. The updates and the monitoring are the baseline.

A word on page builders and “easy”

Easy for a marketer and easy to maintain are not the same.

A builder that lets anyone drop anything anywhere will be used that way. Six months later the homepage is a collage and the person who set it up has left. The next person cannot tell what is safe to change.

Constrain the editor. A few patterns. A locked header and footer. Freedom inside the blocks that are meant to change. This feels stricter on day one and it is what makes the site editable on day 300.

If the team wants total freedom, they will get a site no one can keep fast or on brand. Have that conversation before you install the builder, not after.

Security, without the scare

WordPress is a common target because it is common. A site with current core, current plugins, a real admin password, limited users, and a backup is not an easy target. A site with an abandoned form plugin and an admin called admin is.

You do not need a lecture. You need the updates to happen and the logins to be real. Two-factor on the admin accounts. No shared password in a spreadsheet. A backup that has been restored once, so you know it works.

If a site is already compromised, do not just update and hope. Clean it or rebuild it. A leftover backdoor survives an update. This is a job for someone who has done it, and it is in scope for Web Care when the site is one we can actually clean.

What we will not tell you

We will not tell you to leave WordPress because a chart moved. We will not tell you to stay because we prefer it. We will not add a pile of plugins to make a demo look busy. We will not leave a site on an old PHP version because updating is inconvenient.

We will ask who edits the site, what they change, and what the stack costs to keep. Then we will recommend the smaller option that fits.

Ready for a recommendation? Send the URL and who on your team touches it. We'll come back with stay, clean up, or rebuild, and a range.

Get a Project Quote →

A short way to decide

Answer these.

Does a non-developer need to edit the site every week? If yes, lean toward a CMS they can learn, and WordPress is still the safest bet for a small team.

Is the current WordPress site a mess of plugins and an old PHP version? Clean it before you judge it. A messy WordPress site is not evidence against WordPress.

Do you have someone who will own updates? If no, do not stay, and do not move to another stack you will also neglect. Name the owner. A care plan is a valid owner.

Are you trying to build an application inside a marketing site? Stop. Split them. The site can be WordPress or not. The app should be software.

Is the only argument for moving a market-share headline? Stay, or move for a real reason.

The point

WordPress is a smaller share of the web than it was. That is true and it is not a strategy. The strategy is to match the platform to the people who use it and to the work required to keep it safe.

A marketing team that needs access is a reason to keep a CMS. The plugins, the PHP, and the updates are the cost of that access. Pay the cost, with a person or a plan, or do not take the access. A fast site no one can edit is not a win for a team that has to ship. A WordPress site no one updates is not a win either.

If you want that sorted for a specific site, get a project quote. If you want the design standards either way, start with website design best practices. If you already know you are staying and you want the maintenance handled, start with Web Care.

Landing pages, campaigns, and the Tuesday problem

The reason a marketing team asks for WordPress is rarely the homepage. It is the page they need on a Tuesday.

A promotion. A new hire. A service area you just started covering. A form for a trade show. These are not redesigns. They are pages. On a CMS with a pattern, they take an hour. On a stack where every page is a deploy, they wait for a developer who is on another job.

This is also where landing pages fit. A campaign sometimes deserves its own page with one action and no menu. That page can live on WordPress, built from a locked pattern, or it can be a separate page we build. The point is the same: the team can launch it, or we launch it, without a debate about the platform.

If the team is running ads, the landing page URL has to be stable. Moving platforms in the middle of a campaign, without redirects, is how you pay for clicks that land on a 404. Another reason to move on purpose, not because a share number moved.

Content, posts, and the blog you already have

If the site has a blog, WordPress is doing a job. Posts, categories, drafts, an author, a date. Moving that to a system the team has not used is a training project on top of a migration.

You can move it. We have. The posts come across, the URLs redirect, the internal links get checked. It is work. If the blog is active and the team publishes without help, that work needs a reason bigger than taste.

If the blog is 40 posts from 2019 and no one has logged in since, it is not a reason to stay. Move or prune. A dead blog does not justify a CMS.

Editors, roles, and the person who left

Most WordPress problems that are not security are access.

A former employee is still an admin. A contractor has a login from a project in 2022. The owner uses the same password as their email. An editor account can install plugins because no one changed the role.

Before you debate the platform, fix this. Remove the old users. Give the marketing lead an editor role, not an admin. Put two-factor on the admins. Write down who can install a plugin. It should be a short list.

This is unglamorous and it prevents the incident where a well-meaning person adds a plugin that conflicts with the form handler the week of a launch. Roles are a feature. Use them.

Staging, and why updates go wrong

Updates go wrong when they are applied to the live site with no copy to test on.

A staging site is a copy. You update there. You click the homepage, a service page, and a form. Then you update production. If something breaks, you saw it on staging, or you roll back from the backup you took first.

Hosts that include staging make this easy. A care plan that does not use staging is guessing. We do not guess with updates. The few minutes of checking are the job.

If your host cannot stage, that is a mark against the host, not against WordPress. Change the host before you change the platform.

What “fast enough” means

A WordPress site will not win a contest against a static file. It does not need to. It needs to load fast enough on a phone that a person does not leave, and fast enough that speed is not the reason it loses a ranking.

That is achievable. Correctly sized images. A theme that is not a builder inside a builder. Caching. A host that is not overloaded. We have WordPress sites that feel immediate. We have also seen WordPress sites that take eight seconds because of a slider plugin and uncompressed photos. The second kind is a cleanup, not a verdict.

If you want a number, look at the homepage on a phone, on a normal connection. If it is slow, we can usually say why in a free audit. The why is almost never “because it is WordPress.”

A note on the share charts

The charts will keep moving. A builder will claim the lead in a segment. A new framework will be the default in a community you are not in. None of that changes the Tuesday problem.

Use the charts to know the landscape. Do not use them to schedule a rebuild. Schedule a rebuild when the team cannot do their job, or when the stack cannot be kept safe, or when you are building the wrong kind of thing. Those are stable reasons. The chart is not.

What to do this month

If you have a WordPress site and a marketing team, do these before you take a meeting about a new platform.

List who can log in. Remove anyone who should not. Check the PHP version and the last core update. Count the plugins. Note which have not been updated in a year. Confirm you have a backup that is not on the same server. Ask the person who edits the site what they needed last month and could not do.

If that list is healthy and the editor is fine, stay and put the updates on a plan. If the list is a mess, clean it, then decide. If the editor cannot do the job the team has, then talk about a change, and talk about it as a design and migration project, not as a reaction to a headline.

Get a project quote if you want us to do the list and the recommendation. Web Care if you already know you are staying and you want the PHP, the plugins, and the backups off your plate.

Ready for a fixed quote?

Tell us about the business and what the site needs to do. We'll come back with a scope and a number. No hard sell.

Get a Project Quote →Or start with a free audit
Free auditProject Quote