Download websites that use OWL Carousel

About OWL Carousel

Almost nobody chooses a carousel. A slider arrives bundled inside a purchased theme, or inside a page builder module, or in a template that a freelancer adapted years ago, and it stays there long after the marketing team that asked for a rotating banner has been replaced. OWL Carousel is one of those passengers. Finding the library in the JavaScript libraries column of a site profile usually says more about how the site was assembled than about anything its owner consciously wanted.

The resulting population is statistically odd in a way that turns out to be useful. As of September 2026 we detect OWL Carousel on 3,457,578 sites, with 1,256,503 of them resolving to United States and .com the common suffix. A library first released in 2013 under the MIT licence, shipped as a file that anyone can copy into a theme folder, spreads by duplication rather than by installation. Nobody registers, nobody subscribes, and no update channel exists that would tell the maintainers who is running which build.

We publish no version breakdown for this library, and the reason is worth stating rather than hiding. The script is normally served from a concatenated or minified bundle in which the version banner has been stripped, so the honest answer is that the file is present and the release is unknown. Where a fingerprint survives, it survives by accident. Any confident version histogram for a library distributed this way would be describing the sites careless enough to leave the comment in, not the sites that use it.

What the detection does support is inference about the age and construction of the front end. A carousel of this generation implies a jQuery dependency, which implies a build era, which in turn implies a set of decisions about bundling, accessibility and page weight that were reasonable when they were made and are now a liability. Sliders of this kind are a recurring finding in accessibility audits, because rotating content and keyboard navigation rarely coexist happily. They are also a reliable drag on performance budgets, since the library and its stylesheet load on pages where nothing rotates at all.

So the commercial reader here is not somebody shopping for a carousel. The commercial readers are the agency that sells redesigns and wants a defensible list of sites still running a front end from the previous decade, the performance tooling vendor whose pitch starts with unused JavaScript, the accessibility consultancy that needs to size a market before hiring into it, and the security researcher mapping which unmaintained client side dependencies are still being served in bulk. Each of those needs a population, not a verdict on one domain.

That is the difference an export makes. A lookup tool confirms that one site loads the script, which you could have discovered by viewing source. A list tells you how large the estate is, which countries and suffixes it clusters in, which theme and plugin families carry it along, and what else runs on the same pages. Cross referenced against the content management systems detected alongside it, this library stops being a widget and becomes a marker for a whole build vintage.

Read the count as a floor rather than a measurement. Bundling, renaming, lazy loading and inlining all hide the library from us, and we only record what we can identify with reasonable confidence, so the true install base is larger than the figure shown here. The direction of the error is at least consistent, which means comparisons between countries, suffixes and neighbouring technologies stay meaningful even where the absolute number does not.