Download websites that use Loadable-Components

Code splitting is a build-time decision, and most build-time decisions have disappeared by the time a page reaches a browser. Loadable Components is an exception. The library ships a small runtime that pulls JavaScript chunks on demand and keeps server-rendered markup consistent with the code arriving afterwards, and traces of that runtime survive into the delivered page. Detecting the library therefore says something about how a site was assembled rather than about what it publishes.

Presence implies a React application large enough that shipping it as a single bundle stopped being acceptable, and a team that dealt with the problem deliberately. Nothing here is switched on from an admin panel. Someone configured a bundler, changed how components are imported, and in many cases wired the result into server-side rendering so that crawlers and first paint were not sacrificed to the split. Sites carrying the library lean towards product front ends, application dashboards and content platforms with real front-end engineering behind them rather than brochure pages.

As of November 2026 we detect Loadable Components on 64,267 sites. The library is written in JavaScript and published under the MIT license, and it first appeared in 2017, at a point when React's own lazy loading handled server rendering poorly. Age matters for interpretation. A large share of current installs are decisions inherited from that period and carried forward through rounds of dependency updates rather than choices a team would make from scratch today, so the population is partly a record of front-end archaeology and partly a record of current preference.

Geographically the footprint is uneven. 32,192 of the detected sites sit in United States, and domain endings cluster on .com. Concentration of that kind usually reflects where venture-funded product companies and the agencies serving them are based, not where the library is technically useful.

For a researcher the value is not that any single site uses it, since a per-domain lookup already answers that. The value is the population: every site we can see running a React codebase with deliberate bundle management, exported as one file with country, domain suffix and co-detected technologies attached. Companies selling build tooling, edge rendering, front-end monitoring or migration work use a list like that to size a market and to pick targets who will understand the pitch without being educated first. Analysts and recruiters use it to trace which stacks real engineering teams settled on.

One limit belongs on the number. Detection depends on identifiable output surviving the build, and an aggressive minifier, a custom chunk naming scheme or a fully inlined bundle can erase the evidence. The count should be read as a floor rather than a census.