Skip to main content

Full results

GoodNeeds improvementPoor
Framework
Every CookieBench v3 metric for ten consent managers on Next.js, Mobile profile. One row per metric, one column per consent manager.
Metricc15tOsanoCookieYesCookie ControliubendaEnzuzoOneTrustUsercentricsDidomiKetch
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.
LCPLargest Contentful PaintNeeds improvement: 3.86 s+408 ms vs no CMPNeeds improvement: 3.87 s+424 ms vs no CMPNeeds improvement: 3.64 s+176 ms vs no CMPNeeds improvement: 3.94 s+492 ms vs no CMPPoor: 4.06 s+612 ms vs no CMPPoor: 4.22 s+768 ms vs no CMPNeeds improvement: 3.93 s+476 ms vs no CMPPoor: 4.30 s+844 ms vs no CMPPoor: 4.72 s+1.28 s vs no CMPPoor: 5.19 s+1.74 s vs no CMP
INPInteraction to Next Paint, for the Accept clickGood: 32 msGood: 128 msGood: 24 msGood: 24 msGood: 32 msGood: 56 msGood: 16 msGood: 16 msGood: 16 msGood: 40 ms
CLSCumulative Layout ShiftGood: 0.00Good: 0.00Good: 0.00Good: 0.00Good: 0.00Good: 0.00Good: 0.00Good: 0.00Good: 0.00Good: 0.00
TBTTotal Blocking Time during load66 ms−1 ms vs no CMP223 ms+156 ms vs no CMP83 ms+5 ms vs no CMP255 ms+188 ms vs no CMP115 ms+48 ms vs no CMP264 ms+197 ms vs no CMP183 ms+116 ms vs no CMP154 ms+87 ms vs no CMP357 ms+290 ms vs no CMP1.05 s+982 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 ByteGood: 21 ms+15 ms vs no CMPGood: 5 msGood: 8 msGood: 7 msGood: 6 msGood: 6 ms+1 ms vs no CMPGood: 6 msGood: 7 msGood: 5 msGood: 6 ms+1 ms vs no CMP
FCPFirst Contentful PaintGood: 268 ms+28 ms vs no CMPGood: 248 msGood: 264 msGood: 248 msGood: 252 msGood: 248 ms+8 ms vs no CMPGood: 248 msGood: 252 msGood: 248 msGood: 252 ms+12 ms vs no CMP
Content paintThe article image painted3.86 s+408 ms vs no CMP3.87 s+424 ms vs no CMP3.64 s+176 ms vs no CMP3.94 s+492 ms vs no CMP4.06 s+612 ms vs no CMP4.22 s+768 ms vs no CMP4.54 s+1.09 s vs no CMP4.30 s+844 ms vs no CMP4.72 s+1.28 s vs no CMP5.19 s+1.74 s vs no CMP
LCP elementWhat the browser picked as the largest element
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 state1.98 s
Banner visibleThe banner is on screen240 ms2.15 s2.42 s2.47 s2.66 s2.75 s3.92 s4.16 s4.41 s7.95 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 bannerGood: 32 msGood: 128 msGood: 24 msGood: 24 msGood: 32 msGood: 56 msGood: 16 msGood: 16 msGood: 16 msGood: 40 ms
RejectReject all, from the bannerGood: 40 msGood: 88 msGood: 24 msGood: 24 msGood: 24 msGood: 56 msGood: 16 msGood: 16 msGood: 24 msGood: 32 ms
SaveSave, in the preferences dialogGood: 40 msGood: 80 msGood: 40 msGood: 48 msGood: 40 msGood: 16 msGood: 104 msGood: 32 ms
Next clickA click on the page 500 ms after AcceptGood: 16 msGood: 16 msGood: 16 msGood: 16 msGood: 16 msGood: 24 msGood: 16 msGood: 16 msGood: 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 load725 KB+112 KB vs no CMP698 KB+85 KB vs no CMP644 KB+31 KB vs no CMP712 KB+99 KB vs no CMP735 KB+122 KB vs no CMP766 KB+153 KB vs no CMP824 KB+211 KB vs no CMP777 KB+164 KB vs no CMP866 KB+253 KB vs no CMP1.15 MB+532 KB vs no CMP
UnpackedThe same bytes after decompression1.45 MB+472 KB vs no CMP1.33 MB+348 KB vs no CMP1.07 MB+98 KB vs no CMP1.32 MB+346 KB vs no CMP1.44 MB+458 KB vs no CMP1.57 MB+592 KB vs no CMP1.83 MB+855 KB vs no CMP1.69 MB+711 KB vs no CMP1.98 MB+1.00 MB vs no CMP8.18 MB+7.20 MB vs no CMP
DeferredBytes transferred after the first load settled
RequestsRequests during the first load16+6 vs no CMP14+4 vs no CMP19+9 vs no CMP12+2 vs no CMP14+4 vs no CMP12+2 vs no CMP22+12 vs no CMP27+17 vs no CMP16+6 vs no CMP19+9 vs no CMP
Third-partyRequests to other hosts during the first load049242121769
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 checks4 of 4 passed2 of 4 passed2 failed3 of 4 passed1 could not run3 of 4 passed1 could not run4 of 4 passed4 of 4 passed4 of 4 passed4 of 4 passed4 of 4 passed4 of 4 passed

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