What is a widget?

The count is the symptom; the criteria are two. Speed, tested before and after every addition, because the loading budget has to be defended and a visibly lower mobile score means the widget is paying for itself in lost conversions. And purpose, where each one must answer which business action it serves, so decoration leaves. In practice healthy sites carry two to four with a clear function, while collections of eight or more accumulated over years usually need a clear-out removing about half.

Yes, and this is among the most common compliance gaps: many widgets — maps, fonts, video, social feeds, chat — transfer data to third parties, including outside the EU, from the moment the page loads and before any consent is given, and European case law has penalised exactly that pattern. The standard remedies are consent-gated loading, where the component appears after acceptance or on a click, self-hosted variants where they exist, and correct declaration in the privacy policy.

Think of it as a trajectory. A free widget is the correct start, validating the need without investment, but a function that has become central to the business — the bookings bringing most of your customers, the chat carrying sales — deserves re-evaluation, because free components come without guarantees of availability, support or continuity, with somebody else’s branding and with your customer data inside their system. The practical threshold is when the answer to what a week without this function would cost becomes a number that hurts.