Iubenda
Iubenda is a compliance product for site owners: it generates the privacy and cookie policy pages a site publishes and it shows the consent banner that asks visitors what they agree to. Most people meet it as the box in the corner of an Italian news site or a European hosting company's homepage. This index detected it on 21 of the 5,294 sites measured, 0.4% of them, which puts it seventh of the nine consent platforms tracked here by number of sites. Twenty-one sites is a small group, and everything below describes those twenty-one and nothing wider.
Early contact on all 21
On every one of the 21 sites, at least one company had been contacted before the consent banner could have been answered. That is the highest share of the nine consent platforms in this index, and the median site in the group had 8 companies arrive inside that window — also the highest before-consent median of the nine.
Those two figures describe the pages, not the product. The crawl counts, per site, how many companies were reached inside the window; it does not identify them, and it does not record where Iubenda's own requests fall.
The comparison set is nine platforms, which is small enough that a rank-one position here means less than the same rank would in a larger field.
The median site: 8 companies, 38 requests
The median site carrying Iubenda contacted 8 companies over 38 requests, 2 of those companies classified as tracking. That company count is second of the nine platforms here; the tracker count is third.
First contact came at a median of 595 ms after the page began loading, and the earliest first contact anywhere in the group was 197 ms. After the consent window closed, the median site added nothing further: the median number of companies appearing after the window is 0. On these sites the third-party contact that was going to happen had, for the median page, already happened.
Twenty-one sites, and what kind of twenty-one
The group is not a cross-section of the web. Italian publishing runs through it — repubblica.it at rank 946, 3bmeteo.com at 1451, libero.it at 2954, register.it at 3513 — alongside European hosting and domain brands: superhosting.bg at 1347, websupport.sk at 2445, loopia.se at 2448, transip.nl at 2932. The rest are developer-facing companies: revenuecat.com at 2158, gameanalytics.com at 2361, elastic.co at 2741, arduino.cc at 3615.
That concentration is worth holding onto when reading the medians. European publishers and hosting companies expect EU visitors and run the kind of commercial stack that comes with them. The medians describe that population.
The spread behind the medians
repubblica.it contacted 11 companies, 10 of them inside the consent window, first contact at 762 ms. libero.it reached 10 companies with all 10 inside the window at 627 ms. arduino.cc, the lightest of these examples, contacted 4 and all 4 fell inside the window, at 355 ms.
The other pattern is a split page. superhosting.bg contacted 6 companies with 3 inside the window; websupport.sk contacted 8 with 5 inside, and was also the latest of these examples to make any contact at all, at 1,529 ms.
Same banner product, two different loading orders. What separates them is what each site chose to load and when it chose to load it, which is a decision made in the site's own tags rather than in the consent tool.
No second banner anywhere in the group
Consent-tool detection on these 21 sites returned Iubenda and nothing else, on all 21. That is unusual enough to state plainly, because a site can carry two banner products at once — a platform's own tag plus an IAB TCF framework string, for instance — and in larger groups the tool counts overlap for that reason. Here they do not.
For anyone auditing a specific page rather than reading a summary, the per-site figures are the useful ones: how many companies, how many before the banner, how early the first request went out. MurmStack reports those three for whatever page you have open.
| Site | Companies | Before consent | First contact |
|---|---|---|---|
| repubblica.it | 11 | 10 | 762 ms |
| superhosting.bg | 6 | 3 | 752 ms |
| 3bmeteo.com | 8 | 8 | 1150 ms |
| revenuecat.com | 5 | 5 | 329 ms |
| gameanalytics.com | 8 | 8 | 516 ms |
| websupport.sk | 8 | 5 | 1529 ms |
| loopia.se | 8 | 8 | 451 ms |
| elastic.co | 7 | 7 | 416 ms |
| transip.nl | 9 | 9 | 470 ms |
| libero.it | 10 | 10 | 627 ms |
| register.it | 9 | 9 | 676 ms |
| arduino.cc | 4 | 4 | 355 ms |
| Tool | Sites |
|---|---|
| Iubenda | 21 |
Questions
What does Iubenda put on a page?
A consent banner and the policy pages it links to. The banner is the visible part; behind it sits the configuration that decides which categories of tag a visitor's answer is supposed to control.
Does the banner appear before anything is contacted?
This index cannot settle that. It records that on all 21 sites some company was contacted before the banner could have been answered, without attributing that contact to any particular party, Iubenda included.
Is 21 sites enough to judge the product?
No. It is enough to describe 21 sites. Iubenda is seventh of nine here by site count, and the platforms above it are measured on hundreds of pages each, so a comparison of medians across the nine is a comparison of very different sample sizes.
Which of the named examples were busiest?
repubblica.it with 11 companies and libero.it with 10, both European news publishers, against 4 on arduino.cc. The median for the group is 8 companies over 38 requests.
How fast did contact start?
A median of 595 ms, with the earliest first contact in the group at 197 ms. Among the named examples the range runs from 329 ms on revenuecat.com to 1,529 ms on websupport.sk.