Download websites that use Kadence WP Kadence

About Kadence WP Kadence

Age is usually a complication in a WordPress theme's install base, because sites that arrived early arrived with different habits and never lost them. The theme dates from 2019, which places its entire adoption curve after the block editor became the default way to build a WordPress page. Nothing in the population predates that shift, so the sites carrying it were built by people who accepted blocks rather than by people who merely tolerated them, and the install base is self-selected in a way an older theme's never is.

Self-selection is worth more than the raw count. A theme published by Kadence WP under GPL v2 and written in PHP is free to install and sells extras behind it, which is the standard shape of WordPress commerce, but the builder it attracts is specific: someone assembling performance-conscious sites through a design system of global colours, typography and header controls rather than someone hand-editing template files. Agencies standardise on themes like that, and standardisation shows up in the data as clusters of near-identical builds across a client roster.

As of September 2026 we detect the theme on 291,871 sites. 127,542 of them resolve to United States and the domain mix concentrates in .com, a distribution saying more about where the publisher's marketing overlaps the English-speaking WordPress freelance market than about the software itself.

Version detail is available here, which is not true of every theme. We hold 211 distinct version strings across the population and the sites cluster on 1.5.2. A theme version is readable because WordPress appends it to the stylesheet request written into the page, which also means the figure inherits whatever the site's caching and optimisation layers do to that request. Sites behind aggressive asset optimisation can lose the string entirely and are recorded without a version rather than guessed at.

Theme version lag reads differently from plugin lag, and the difference is the useful part. Plugins update themselves quietly in the background, while a theme update is the one WordPress owners postpone, because customisation collects inside the theme and an update is the event that breaks a layout in front of a client. A group of sites sitting well behind the current release is therefore a group nobody is actively maintaining, which makes it a lead list for maintenance, security and redesign businesses and a migration list for competing themes and hosts. Working out which sites those are means holding every domain in the set at once. Checking a domain answers whether one named site runs the theme, and that is a different question from the one anybody buys a dataset to answer.