CookieYes
CookieYes is a consent management tool. A website installs it, and it draws the cookie banner you meet on the first page load, records what you choose, and is meant to hold back the scripts you have not agreed to. It was detected on 62 of the 5,294 sites in this index, 1.2 percent of them, which places it fifth of the nine consent platforms measured here by how many sites carry it.
What a CookieYes site looks like
The median site running CookieYes contacted 6 separate companies and made 31 third-party requests over the measured page load, with 1 of those companies classified as a tracker. Against the other consent platforms in this index that is sixth of nine on companies, sixth of nine on requests and eighth of nine on trackers. The sites carrying this banner sit on the lighter end of the consent-tool population rather than the heavy end. Reach and weight are separate things: a platform can be widely installed and still sit mostly on quiet pages.
Almost all of the contact happens in the first window
On 61 of the 62 sites, at least one company was contacted before the banner could have been answered. That is 98.4 percent, sixth of nine among the platforms measured here. Median first contact landed at 602 milliseconds, the third-highest figure of the nine, so contact on a CookieYes site tends to begin later than on most other platforms' sites. The quickest first contact recorded across the 62 was 55 milliseconds. The number that completes the picture is what arrives afterwards: at the median, zero companies are contacted after the window closes. On at least half of these sites, nothing new was reached once a visitor could plausibly have clicked anything.
One banner, and only one
CookieYes was the only consent tool recorded across this set: 62 sites, 62 sightings, nothing else seen alongside it. Figures like these are counts of sightings rather than slices of a total, because a single site can carry more than one consent layer and the numbers for a tool list can then exceed the number of sites they describe. Here they do not. Every site in the group ran one recognisable consent layer and it was this one, which makes the set unusually clean to read: no second banner to attribute anything to.
Who installs it
The 62 include a visible cluster of advertising and measurement companies running CookieYes on their own corporate sites: smadex.com, kargo.com, fyber.com, aniview.com and smilewanted.com all appear. So do tools their customers buy, including ahrefs.com, quantummetric.com and anydesk.com, alongside dribbble.com, psychologytoday.com, hugedomains.com and markmonitor.com. The spread behind the identical banner is wide. smadex.com registered 2 companies, both inside the window. quantummetric.com registered 25, of which 20 were inside, and it is one of the slower starters here at 897 milliseconds. ahrefs.com began earliest of these examples at 182 milliseconds with 6 companies, all inside; markmonitor.com began latest at 1,189 milliseconds with 4, of which 3 were inside. fyber.com carried 11, all inside the window.
What the banner does not tell you
A consent tool is a control surface, not a description of the page behind it. Two of these sites can show the same dialogue, with the same wording and the same buttons, and differ by an order of magnitude in how many companies your browser has already spoken to by the time you read it. The measurement here separates those two things deliberately: the tool is recorded, and so is the count of companies contacted before the window closed, and neither one predicts the other very well across 62 sites.
| Site | Companies | Before consent | First contact |
|---|---|---|---|
| markmonitor.com | 4 | 3 | 1189 ms |
| anydesk.com | 6 | 6 | 341 ms |
| psychologytoday.com | 3 | 3 | 764 ms |
| dribbble.com | 4 | 4 | 581 ms |
| smilewanted.com | 4 | 4 | 416 ms |
| hugedomains.com | 6 | 6 | 541 ms |
| smadex.com | 2 | 2 | 602 ms |
| kargo.com | 6 | 6 | 234 ms |
| fyber.com | 11 | 11 | 570 ms |
| ahrefs.com | 6 | 6 | 182 ms |
| aniview.com | 6 | 6 | 586 ms |
| quantummetric.com | 25 | 20 | 897 ms |
| Tool | Sites |
|---|---|
| CookieYes | 62 |
Questions
Does CookieYes decide what loads before I answer the banner?
The crawl records, for each site, how many companies were contacted before the banner could have been answered, and 61 of the 62 CookieYes sites had at least one. It does not record which requests those were, so it cannot separate the consent tool's own traffic from the rest of the page. What is established is narrower and still useful: on nearly every site in this group, third-party contact was already underway.
Is a median of 6 companies a lot for a site with a consent banner?
Among the nine consent platforms measured in this index, CookieYes sites rank sixth of nine on that figure, so the answer within this comparison is no. The set is also eighth of nine on median trackers, at 1, and sixth of nine on median requests, at 31.
What does the 602 millisecond figure mean?
It is the median time from the start of the page load to the first request that left the site's own domain, across the 62 sites. Half started sooner and half started later. The earliest recorded on any of them was 55 milliseconds.
Do all CookieYes sites behave the same way?
No, and the examples make the range plain: 2 companies on smadex.com against 25 on quantummetric.com, with first contact ranging from 182 milliseconds on ahrefs.com to 1,189 on markmonitor.com. The banner is a common component, not a common architecture.