Download websites that use Slick

About Slick

A carousel that sits unchanged for years is usually a problem. Here it is the point. Copies of the code were dropped into templates once and left alone, still doing the job they were written for on pages built long ago, which makes Slick a poor subject for a roadmap and a very good subject for dating a website.

Released in 2014 under the MIT licence, the plugin solved a problem every brochure site had at the time. Content had to rotate, it had to work under a finger as well as a mouse, and it had to drop into a codebase that already depended on jQuery. Sliders of this generation were adopted by theme authors rather than by site owners, which is why the library appears on sites whose operators have never heard the name.

As of October 2026 we detect the library on 3,182,343 sites, 1,056,207 of them resolving to United States, with .com the common suffix. We also resolve 151 distinct version strings, and 1.8.1 is the reading we record most frequently. A tight concentration on one release, spread thinly across many others, is what a library shipped inside themes looks like from the outside. Most installs never move off the version their template shipped with, so version numbers say little about how carefully a site is maintained.

The dating signal has to come from context instead, and context is exactly what a full technology profile provides. A site carrying this library alongside an old jQuery build, a page builder from the same era and a stylesheet framework of similar vintage is a site whose front end has not been rebuilt in a long time. The same library sitting inside an otherwise modern stack usually means a single legacy template survived a redesign. Distinguishing between those two cases is impossible from a single detection and straightforward from a whole row.

Who needs that distinction? Agencies that sell rebuilds and need a defensible target list rather than cold outreach. Performance vendors whose entire argument is unused client side code loading on every page. Accessibility practitioners, since rotating content and keyboard navigation have never got along and remediation work has to be scoped before it can be quoted. Security teams inventorying ageing front end dependencies, where the question is not whether a specific site is vulnerable but how much of the estate would need touching. Every one of those is a population question.

Detection limits point in one direction only. We identify the library from file signatures and characteristic markup, so any site that concatenates its scripts into one bundle, renames the file, inlines it or loads it conditionally can pass us unnoticed. The count is therefore a floor and not a census, and the sites we miss skew toward the ones with a build pipeline, meaning better maintained sites are underrepresented. The bias is consistent enough that comparisons across countries, suffixes and neighbouring technologies remain sound even where the absolute total does not.

What a downloadable list changes is the direction of the query. Checking one domain tells you what that domain loads, which you could see in the page source anyway. An export tells you how many sites carry the library, in which markets, under which suffixes, and what else runs beside it, which is the only form in which the question can be answered before the answer stops mattering. Sorted by the content management systems detected alongside it, this carousel stops being a widget and becomes a marker for an entire construction vintage, and a vintage is something you can sell to, secure or migrate.