The Kadence Theme

Kadence is a light theme with builders bolted on where they matter. Rather than a large options panel or a full page builder, it gives you drag-and-drop header and footer construction, a sensible design system, and a separate block library for page layout.

That separation is the useful thing to understand, because the theme and the blocks have different lock-in profiles.

Free versus Pro

The free version is not a trial. It is a complete, usable theme, and a large share of Kadence sites never need more. Pro is worth it when you need the theme itself to control conditional layouts — a different header on landing pages, an announcement bar for logged-in customers, a custom archive layout for one post type.

Decide which side of that line you are on before buying, the same way the Astra theme presents the same choice.

The header and footer builders

This is Kadence's distinguishing feature and the reason people choose it over lighter alternatives. Building a header by dragging elements into a grid — desktop and mobile configured separately — solves the single most common reason people reach for a page builder in the first place.

Two consequences:

• It reduces the case for a page builder. If the header was your reason, you may not need one — the wider decision is in choosing a page builder.
• It is a theme option, so it does not travel. Switching themes means rebuilding the header, which is normal but worth knowing before you spend an afternoon on it.

Where the dependency actually is

The theme itself is comparatively portable. The blocks are not, and that distinction is the whole lock-in story.

Ordinary block content survives. Paragraphs, headings, images and core blocks are standard WordPress content stored as HTML in the post — see what is a block in WordPress. Switch themes and they render fine.

Kadence Blocks do not. A page built with the library's row layout, tabs, accordions or advanced buttons loses those blocks if the plugin is removed. You keep the text; you lose the structure. This is far milder than shortcode-based lock-in — you are not left with bracket text — but it is a dependency.

Theme options do not travel, including header, footer, colours and typography.

The practical habit: use core blocks where they are sufficient, and reach for the library where it genuinely earns its place. That keeps most of the site portable at no cost in capability.

Performance

Kadence's reputation is for being light, and the design supports it — conditional asset loading, no bundled slider or icon library loaded wholesale, and a design system expressed in a small amount of CSS.

Treat it as a good baseline rather than a result. What still decides your numbers is image handling, hosting, and caching. A Kadence site with unoptimised photographs on cheap shared hosting is a slow site. Measure a real page as described in how to speed up a WordPress site.

Starter templates

Kadence ships importable designs, and they behave like every starter template: they import content, and they may install plugins.

Import on a new site before you have written anything, or on a staging copy first. Importing onto a site with existing content creates pages you then have to find and delete — the general caution is in templates versus themes.

Who it suits

A good fit for:

• Sites that want header and footer control without adopting a page builder.
• Anyone staying with the block editor but needing more layout blocks than core provides.
• Small business and brochure sites where performance matters and budget is finite.
• Builders who want a design system rather than a per-page styling free-for-all.

A poor fit for:

• Teams committed to full site editing, where a block theme is the more consistent choice.
• Projects needing pixel-level control across many bespoke layouts, where a builder is honestly the tool.
• Anyone who wants zero dependencies, for whom a default theme plus custom CSS is lighter still.

Common mistakes

• Using library blocks for everything, including layouts core handles, which converts portable content into dependent content for nothing.
• Buying Pro before hitting a free limit. Find the limit first.
• Importing a starter template onto a live site.
• Assuming the header travels to the next theme.
• Treating "lightweight" as a performance guarantee rather than a starting point.

Before you commit

Install the free version on staging, build your real header and one real page with your own content, and check it on a phone. Then deactivate the blocks plugin and look at what that page becomes — that is the dependency you are accepting, and it is a smaller one than most themes in this category ask for.