Full results on React

Only c15t, Cookie Control, Didomi, Enzuzo, iubenda, Ketch, OneTrust, Osano, Usercentrics and CookieYes ran on React. See every CMP on Next.js

GoodNeeds improvementPoor

Framework

Every CookieBench v3 metric for ten consent managers on React, Desktop profile. One row per metric, one column per consent manager.
Core Web VitalsLCP, CLS and TBT come from the page load. INP comes from the Accept click. Google rates LCP good up to 2.5 s and poor above 4 s. It rates INP good up to 200 ms and poor above 500 ms. It rates CLS good up to 0.1 and poor above 0.25. It does not rate TBT.
Metric	CookieYes	c15t	Cookie Control	iubenda	Enzuzo	Didomi	OneTrust	Osano	Usercentrics	Ketch
LCPLargest Contentful Paint	Good: 140 ms	Good: 180 ms+36 ms vs no CMP	Good: 136 ms	Good: 136 ms	Good: 132 ms−4 ms vs no CMP	Good: 140 ms	Good: 140 ms	Good: 140 ms	Good: 136 ms	Good: 136 ms−8 ms vs no CMP
INPInteraction to Next Paint, for the Accept click	Good: 16 ms	Good: 16 ms	Good: 24 ms	Good: 32 ms	Good: 16 ms	Good: 16 ms	Good: 16 ms	Good: 40 ms	Good: 16 ms	Good: 24 ms
CLSCumulative Layout Shift	Good: 0.00	Good: 0.00	Good: 0.00	Good: 0.00	Good: 0.00	Good: 0.00	Good: 0.00	Good: 0.00	Good: 0.00	Good: 0.00
TBTTotal Blocking Time during load	0 ms	0 ms	12 ms+12 ms vs no CMP	0 ms	43 ms+43 ms vs no CMP	51 ms+51 ms vs no CMP	2 ms+2 ms vs no CMP	9 ms+9 ms vs no CMP	51 ms+51 ms vs no CMP	174 ms+174 ms vs no CMP
Page loadGoogle rates TTFB good up to 0.8 s and FCP good up to 1.8 s. Content paint is the paint time of the article image. We time it even when the banner was the largest element.
TTFBTime to First Byte	Good: 4 ms	Good: 2 ms	Good: 2 ms	Good: 2 ms	Good: 2 ms+0 ms vs no CMP	Good: 2 ms	Good: 2 ms	Good: 2 ms	Good: 2 ms	Good: 2 ms+0 ms vs no CMP
FCPFirst Contentful Paint	Good: 92 ms	Good: 108 ms	Good: 76 ms	Good: 76 ms	Good: 76 ms−8 ms vs no CMP	Good: 76 ms	Good: 80 ms	Good: 76 ms	Good: 76 ms	Good: 72 ms−4 ms vs no CMP
Content paintThe article image painted	140 ms	180 ms+36 ms vs no CMP	136 ms	136 ms	132 ms−4 ms vs no CMP	140 ms	140 ms	140 ms	136 ms	136 ms−8 ms vs no CMP
LCP elementWhat the browser picked as the largest element
BannerMilliseconds from navigation. p75 is where the slowest quarter of visits starts.
CMP requestedFirst request for the CMP’s script or config
CMP loadedThe download of the CMP’s main script is complete
Consent knownThe CMP reports the visitor’s consent state		305 ms
Banner visibleThe banner is on screen	287 ms	332 ms	376 ms	419 ms	443 ms	458 ms	634 ms	647 ms	693 ms	1.62 s
Screen coveredShare of the viewport the banner covers
Click responseTime until the screen updates. We rate it like INP: good up to 200 ms, poor above 500 ms. The browser reports these times in 8 ms steps. It does not report clicks under 16 ms.
AcceptAccept all, from the banner	Good: 16 ms	Good: 16 ms	Good: 24 ms	Good: 32 ms	Good: 16 ms	Good: 16 ms	Good: 16 ms	Good: 40 ms	Good: 16 ms	Good: 24 ms
RejectReject all, from the banner	Good: 16 ms	Good: 16 ms	Good: 16 ms	Good: 16 ms	Good: 16 ms	Good: 16 ms	Good: 16 ms	Good: 32 ms	Good: 16 ms	Good: 24 ms
SaveSave, in the preferences dialog		Good: 24 ms		Good: 32 ms	Good: 32 ms	Good: 32 ms	Good: 24 ms	Good: 48 ms	Good: 16 ms	Good: 16 ms
Next clickA click on the page 500 ms after Accept	Good: 16 ms	Good: 16 ms	Good: 16 ms	Good: 24 ms	Good: 16 ms	Good: 16 ms	Good: 16 ms	Good: 16 ms	Good: 16 ms	Good: 16 ms
After AcceptMilliseconds from the click. Main thread is the long-task blocking time after it.
Banner goneBanner and any overlay removed
Consent appliedThe CMP’s consent state matches the choice
Scripts ranEvery script that the choice lets run is complete
Main threadLong-task blocking time after the click
After RejectReject lets no scripts run, so there is no script time to report.
Banner goneBanner and any overlay removed
Consent appliedThe CMP’s consent state matches the choice
Main threadLong-task blocking time after the click
After SaveFrom the Save click in the preferences dialog.
Banner goneBanner and any overlay removed
Consent appliedThe CMP’s consent state matches the choice
Scripts ranEvery script that the choice lets run is complete
Main threadLong-task blocking time after the click
Download sizeThe first load. Unpacked is the size after decompression. That is the code that the browser must parse.
TransferredBytes over the network during the first load	583 KB+31 KB vs no CMP	652 KB+100 KB vs no CMP	650 KB+98 KB vs no CMP	673 KB+121 KB vs no CMP	705 KB+153 KB vs no CMP	805 KB+253 KB vs no CMP	763 KB+211 KB vs no CMP	637 KB+85 KB vs no CMP	716 KB+164 KB vs no CMP	1.08 MB+532 KB vs no CMP
UnpackedThe same bytes after decompression	815 KB+97 KB vs no CMP	1.11 MB+394 KB vs no CMP	1.06 MB+346 KB vs no CMP	1.18 MB+458 KB vs no CMP	1.31 MB+592 KB vs no CMP	1.72 MB+1.00 MB vs no CMP	1.57 MB+855 KB vs no CMP	1.07 MB+348 KB vs no CMP	1.43 MB+711 KB vs no CMP	7.92 MB+7.20 MB vs no CMP
DeferredBytes transferred after the first load settled
RequestsRequests during the first load	16+9 vs no CMP	17+10 vs no CMP	9+2 vs no CMP	11+4 vs no CMP	9+2 vs no CMP	13+6 vs no CMP	19+12 vs no CMP	11+4 vs no CMP	24+17 vs no CMP	16+9 vs no CMP
Third-partyRequests to other hosts during the first load	9	1	2	4	2	6	12	4	17	9
Returning visitorsA visitor who accepted earlier loads the page again. We expect the banner to stay hidden.
Banner hiddenThe banner stayed hidden on the return visit
Consent knownTime from navigation until the CMP restores the stored choice
Consent checksNo tracker or cookie before the visitor chooses, and the choice holds afterwards. A check we could not run is not a failure.
ChecksLoad, Accept, Reject, Save, withdrawal and keyboard checks	3 of 4 passed1 could not run	4 of 4 passed	3 of 4 passed1 could not run	4 of 4 passed	4 of 4 passed	4 of 4 passed	4 of 4 passed	4 of 4 passed	4 of 4 passed	4 of 4 passed

A value without a “vs no CMP” line had no measurable change from the same page without a consent manager.