The short answer

To choose a WordPress theme for a business website, pick the lightest theme that renders your design without a pile of add-ons, confirm it works natively with the block editor, check that it has shipped updates in the last 90 days, load its demo through a speed test before you pay, and read the support forum instead of the sales page. In practice, a lean theme paired with one page builder or the block editor beats a heavy multipurpose theme with 40 pre-built demos almost every time.

Most guides tell you to browse Appearance > Themes > Add New and filter by industry. That advice picks a look. It does not protect you from the theme that quietly adds 1.8 MB of JavaScript to every page and locks your content into shortcodes you cannot remove. This guide is written for the second problem, because that is the one that costs money 18 months later.

The real decision: lightweight theme plus builder, or heavy multipurpose theme

Before you compare individual themes, decide which of these two paths you are on. Everything else follows from it.

Criteria	Lightweight theme + block editor or one builder	Heavy multipurpose theme (all-in-one)
Typical front-end weight	50 to 300 KB of theme assets	700 KB to 2.5 MB, often before images
Setup speed	Slower at first, you build the layout	Very fast, import a demo and replace text
Lock-in risk	Low to medium, content stays portable	High, custom post types and shortcodes belong to the theme
Long term maintenance	Fewer moving parts, fewer conflicts	Bundled plugins update on the theme author’s schedule
Core Web Vitals headroom	Good, you control what loads	Tight, optimisation becomes damage control
Best for	Lead generation sites, service businesses, sites that will grow	Short-lived campaign sites, tight budgets, no developer available

Multipurpose themes are not evil. They are optimised for a different buyer: someone who needs a site live on Friday and will not touch it again. If your website is a commercial asset that has to rank, convert and survive a redesign, the trade is a bad one. Every demo you do not use still ships in the theme folder, and its stylesheet is often enqueued site-wide.

11 checks before you buy a WordPress theme

1. Measure the demo page weight yourself

Open the theme’s live demo, then run it through a speed tool such as PageSpeed Insights, GTmetrix or WebPageTest. Ignore the score, read the numbers underneath.

• Total page weight: under 1 MB for a homepage with a few images is healthy. Over 3 MB is a warning.
• Number of requests: under 50 is comfortable. Over 90 on a demo page means the theme loads assets it does not need.
• JavaScript payload: this is the one that hurts. Over 500 KB of JS on a brochure page is a structural problem, not something a caching plugin fixes.

Remember that theme demos are hosted on tuned servers with premium CDNs. Your production site will be slower than the demo, not faster.

Quick manual test

Open the demo, press F12, go to the Network tab, tick “Disable cache” and reload. Sort by size. If you see three icon font files, two slider libraries and a 400 KB animation script on a page with no animation, the theme loads everything unconditionally.

2. Confirm real block editor compatibility

In 2026 there are three categories, and the marketing copy blurs them:

1. Block themes (full site editing): headers, footers and templates are edited with blocks. Best long term alignment with WordPress core.
2. Classic themes with good block support: they register editor styles, support wide and full alignment, and do not fight the editor. Perfectly fine.
3. Classic themes with a shortcode page builder bolted on: the block editor is technically present but every demo page is built with proprietary elements. Avoid unless you accept the lock-in.

Test it: on the demo, look at whether content pages could plausibly be rebuilt as blocks. On the theme’s documentation, search for the words editor-styles, align-wide, block patterns and theme.json. A theme that ships a theme.json file has been maintained for the modern editor.

3. Check how the theme handles SEO fundamentals

A theme cannot do your SEO, but it can absolutely damage it. What matters:

• Heading hierarchy: one H1 per page, logical H2 and H3 order. Inspect the demo and check that the site tagline or a widget is not sitting in an H1, and that section titles are not all H4 for styling reasons.
• No duplicate meta tags: if the theme injects its own title tag or description while you run an SEO plugin, you get conflicts. Good themes leave this to plugins.
• Clean semantic markup: header, nav, main, article, footer elements rather than nested divs only.
• Image handling: responsive srcset, width and height attributes, lazy loading on below-the-fold images, and the option to disable lazy loading on the LCP image.
• Schema: some themes hardcode outdated or invalid structured data. Run the demo through Google’s Rich Results Test. Invalid schema from a theme is a hassle to remove.
• Breadcrumbs: nice to have, but check they can be turned off if your SEO plugin handles them.

4. Read the changelog, not the release date

Marketplaces show a “last updated” date. That date can mean a typo fix. Open the actual changelog and look for:

• Updates within the last 3 months, and a consistent rhythm over the last 2 years.
• Entries mentioning compatibility with the current WordPress version.
• Security fixes that were shipped quickly, which is a good sign, not a bad one.
• No 9 month silence followed by a single “WordPress 6.x compatibility” line.

On WordPress.org, also check the “Active installations” trend and whether the developer answers in the support forum. A theme with 40,000 installs and an abandoned support tab is a liability.

5. Inspect what the demo import actually installs

This is the check almost nobody performs, and it is where multipurpose themes hide their weight. Before buying, find the documentation page listing required and recommended plugins.

Warning signs:

• More than 3 required plugins to make the demo look like the demo.
• Bundled premium plugins (sliders, mega menus, portfolio managers) that only update through the theme. When the theme licence lapses, those plugins stop receiving security updates.
• A demo import that creates dozens of pages, sample products, sliders and custom post types you then have to delete one by one.
• Options panels with 300 settings stored in a single serialised database row.

Rule of thumb: if removing the theme would break your content, the theme is doing too much. A theme should control presentation. Functionality belongs in plugins you chose.

6. Judge support quality from the public forum

Do not read the testimonials. Read the last 20 support threads.

• What is the median response time? Under 24 hours on business days is good.
• Are answers substantive, or copy-paste requests for admin credentials?
• Are there repeat complaints about the same bug across versions?
• How does the author respond to a critical review? Tone tells you what year three will feel like.

Also check what support includes. On most marketplaces, support covers bugs and basic usage for 6 or 12 months, not customisation. Renewal cost matters for a business site.

7. Test accessibility early

Accessibility is increasingly a legal and procurement requirement in Europe, and it is very hard to retrofit. On the demo, check:

• Keyboard navigation: can you tab through the menu and see a visible focus outline?
• Colour contrast on buttons and body text.
• Text that resizes without breaking the layout.
• A skip-to-content link.

On WordPress.org, the accessibility-ready tag is a genuine signal because it is reviewed by humans.

8. Look at the code licence and the update path

• GPL-compatible licence, so you or another agency can modify it.
• Child theme support and documentation. If the theme discourages child themes, your customisations will be wiped on update.
• Hooks and filters documented for developers.
• Automatic updates that work without a proprietary dashboard plugin that phones home on every admin page load.

9. Verify mobile behaviour on a real device

Resizing a desktop browser is not a mobile test. Open the demo on a mid-range phone over a normal mobile connection. Watch for layout shift while the page settles, sticky headers that eat a third of the screen, sliders that block scrolling, and menus that need two taps to open. Cumulative Layout Shift problems caused by a theme are usually structural, not something you patch later.

10. Match the theme to your actual content model

List your real page types before browsing: home, service pages, case studies, team, pricing, blog, contact, maybe a shop. Then check that the theme has clean templates for those. An “industry” theme built for restaurants gives you a menu module and a reservation form you will not use, plus a blog template that was an afterthought.

Functionality-based selection beats industry-based selection nearly every time, because the visual identity comes from your colours, typography and photography, not from the theme’s stock imagery.

11. Cost the whole lifecycle, not the sticker price

Cost item	Question to ask
Licence	One-off or annual? Does it cover multiple sites?
Renewal	What happens to updates and bundled plugins if you stop paying?
Builder or add-ons	Is a premium page builder licence required on top?
Setup time	Hours to clean up a demo import versus hours to build clean
Performance work	Will you need paid optimisation to reach acceptable Core Web Vitals?
Exit cost	How much content rework if you change theme in 3 years?

Red flags that a theme will slow your site down later

Any single item below is a caution. Three or more, walk away.

• “50+ pre-built demos” promoted as the headline feature.
• Bundled slider or visual composer plugins that cannot be deactivated without breaking layouts.
• Icon fonts loaded site-wide when the design uses six icons.
• Several Google Fonts families loaded from a remote domain, with no self-hosting option.
• jQuery-dependent effects on a page that has no interactivity.
• Content wrapped in theme shortcodes such as [vc_row], which turns into visible junk the day you switch themes.
• No child theme documentation.
• An options panel that requires its own dashboard plugin.
• Demo homepage above 4 MB or 120 requests.
• Support forum threads older than a week with no reply.
• Sales page that never mentions performance, accessibility or the block editor.

A practical 60-minute evaluation workflow

1. Shortlist 3 themes maximum. More than that and you compare aesthetics, not substance.
2. Run each demo through PageSpeed Insights on mobile and note total weight, JS weight and LCP.
3. Open the changelog and confirm updates in the last quarter and a steady two-year history.
4. Read 20 support threads and note the median reply time.
5. List required plugins from the documentation and decide whether you would install each one voluntarily.
6. Check the source of the demo homepage for heading structure and duplicate meta tags.
7. Install on a staging site if a trial or free version exists, import one demo, then check the page weight on your own hosting.
8. Buy, then immediately create a child theme or use the theme’s official customisation method before touching anything.

If you cannot test on staging, at least buy from a marketplace or vendor with a refund window, and do your real testing in the first 48 hours. godaddy.com has covered this at length.

Free or premium?

Free themes from the official WordPress.org directory pass a code review and are a reasonable starting point for a small business site. The trade-off is limited support and, for some, slower feature development. Premium themes buy you documentation, support and design breadth.

The useful distinction is not free versus paid. It is maintained versus abandoned, and focused versus bloated. A well-maintained free theme with a clean theme.json will outperform a neglected premium multipurpose theme every single time. This guide goes deeper on it.

Avoid nulled or “free download” copies of premium themes entirely. They are the most common vector for injected malware on WordPress sites, and the clean-up cost dwarfs the licence you saved.

What we recommend for most business sites

For a corporate or service website that needs to rank and convert, our default is a lean, well-maintained theme with strong block editor support, extended with a small number of chosen plugins, and one builder only if the team genuinely needs it for landing pages. That combination keeps page weight predictable, keeps content portable and keeps the redesign in three years a design job rather than a migration project.

Choose the heavy multipurpose route only when the site is short-lived, the budget is fixed and low, and nobody will maintain it. Make that a conscious decision, not a default.

FAQ

How do I know if a WordPress theme is good?

Check five things: updates within the last three months, a demo homepage under roughly 1 MB, native block editor support, a small list of required plugins, and a support forum where recent questions received real answers. A theme that passes all five is a safe purchase even if it is not the prettiest on your shortlist.

Should I use a page builder or the block editor?

The block editor is the direction WordPress core is going and produces lighter output. Use a page builder if your team needs advanced layout control without code and you accept a degree of lock-in. Do not use both across the same site, and never stack a builder on top of a theme that already includes one.

Does the theme affect SEO?

Indirectly but significantly. It controls page speed, Core Web Vitals, mobile rendering, heading structure and semantic markup. It does not write your titles, descriptions or content, which remains the larger factor. A bad theme puts a ceiling on your technical SEO; a good one simply removes the obstacle.

How many themes should I have installed?

Two: your active theme and one default WordPress theme kept as a fallback for troubleshooting. Delete the rest. Inactive themes still need updating and remain a security surface.

Can I change my WordPress theme later without losing content?

Posts, pages and media stay in the database, so the content survives. What breaks is anything the theme owned: shortcodes, custom post types, sliders, theme options and widget placements. This is exactly why lock-in matters at purchase time.

Is WordPress still a good choice in 2026?

Yes for content-heavy, SEO-driven business sites where you want ownership of your data and no platform rent. The frustration people express online is usually about bloated themes, plugin sprawl and poor hosting rather than WordPress itself. Choosing a lean theme is the single decision that prevents most of it.

What is the most popular WordPress theme?

Popularity shifts, and the default core themes plus a handful of large multipurpose themes always top the install counts. Install numbers tell you about marketing reach, not about whether a theme fits your project. Use the 11 checks above instead of a popularity ranking.

Need a second opinion before you buy?

If you are choosing a theme for a site that has to perform commercially, an hour of review before purchase is cheaper than a rebuild afterwards. The team at itimap.com can audit your shortlist, benchmark the demos on real hosting conditions and tell you which one will still be fast in two years. Choosing and installing a theme is a useful companion to this.