Download websites that use Colibri WP

About Colibri WP

A theme is the closest thing a website has to a signature of whoever assembled it. Platforms are chosen by hosting, plugins are chosen by need, but the theme is picked by a person looking at a screenshot and deciding it looks like the business they are trying to build.

Colibri WP attracts a very specific version of that person. Extend Themes publishes it under the GPL v2, written in PHP and available since 2019, and its selling point was a live front end editor that let someone lay out a page visually without buying a separate page builder. The pitch targets an owner assembling their own site rather than an agency delivering one, and the population reflects that. Small service businesses, local trades, consultants, single location restaurants, early stage projects that needed a presence before they needed a strategy.

The version data is where the population starts to differentiate itself. We currently see 121 distinct version strings in production, with 1.0.390 the value reported by the largest number of installations. A free theme that ships frequently and updates automatically should not produce a spread that wide. The spread appears because automatic updates get disabled, because hosting environments block them, and above all because sites go quiet. Nobody logs in, nothing updates, and the version string freezes at whatever was current on the last day anyone cared.

Dormancy is the commercially interesting reading. A site several releases behind on a theme that updates itself is usually not a site with a considered upgrade policy. A site several releases behind is usually a site nobody has opened in a long time, which makes it a redesign lead for an agency, a churn risk for its host, an unmaintained surface for a security researcher and a live target for anyone selling a replacement. The version string is a proxy for attention, and attention is what you are really trying to segment.

Geography adds a second filter rather than a story. Germany accounts for 3,100 of the installations we observe and the .com zone leads the domain split, a combination that usually indicates a theme spread through hosting recommendations and local tutorial content rather than through international marketing.

None of this can be answered one domain at a time. A lookup tells you which theme a single site runs. The useful question is the inverse: give me every site in this country, on this theme, on this version or older, that also runs no ecommerce plugin and no analytics tag. Answering that needs the whole population as a file, with the version, the country, the TLD and every other fingerprint on the same row, which is what the export is.

Two limits are worth stating. Theme detection depends on asset paths and generator markers, so a heavily optimised site that bundles, renames or proxies its stylesheets can drop out of the count entirely. And the version we publish is the one declared in the theme header, which a customised child theme can freeze at a value that no longer describes the code actually running. Both errors push the same way, toward undercounting the tidier end of the estate.