Full results on Nuxt

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

GoodNeeds improvementPoor

Framework

Every CookieBench v3 metric for ten consent managers on Nuxt, 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	c15t	CookieYes	Cookie Control	iubenda	Didomi	Enzuzo	OneTrust	Osano	Usercentrics	Ketch
LCPLargest Contentful Paint	Good: 172 ms+64 ms vs no CMP	Good: 120 ms	Good: 116 ms	Good: 108 ms	Good: 112 ms	Good: 116 ms+4 ms vs no CMP	Good: 108 ms	Good: 112 ms+2 ms vs no CMP	Good: 116 ms	Good: 112 ms
INPInteraction to Next Paint, for the Accept click	Good: 24 ms	Good: 16 ms	Good: 16 ms	Good: 24 ms	Good: 16 ms	Good: 16 ms	Good: 16 ms	Good: 48 ms	Good: 16 ms	Good: 16 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	28 ms+28 ms vs no CMP	0 ms	59 ms+59 ms vs no CMP	43 ms+43 ms vs no CMP	1 ms+1 ms vs no CMP	17 ms+17 ms vs no CMP	52 ms+52 ms vs no CMP	177 ms+177 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: 17 ms+12 ms vs no CMP	Good: 7 ms	Good: 5 ms	Good: 6 ms	Good: 6 ms	Good: 5 ms+0 ms vs no CMP	Good: 5 ms	Good: 5 ms+0 ms vs no CMP	Good: 6 ms	Good: 6 ms+1 ms vs no CMP
FCPFirst Contentful Paint	Good: 72 ms+24 ms vs no CMP	Good: 44 ms	Good: 44 ms	Good: 44 ms	Good: 56 ms	Good: 52 ms	Good: 44 ms	Good: 46 ms	Good: 52 ms	Good: 48 ms
Content paintThe article image painted	172 ms+64 ms vs no CMP	120 ms	116 ms	108 ms	112 ms	116 ms+4 ms vs no CMP	108 ms	112 ms+2 ms vs no CMP	116 ms	112 ms
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	104 ms
Banner visibleThe banner is on screen	45 ms	284 ms	397 ms	430 ms	472 ms	480 ms	640 ms	671 ms	692 ms	1.63 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: 24 ms	Good: 16 ms	Good: 16 ms	Good: 24 ms	Good: 16 ms	Good: 16 ms	Good: 16 ms	Good: 48 ms	Good: 16 ms	Good: 16 ms
RejectReject all, from the banner	Good: 16 ms	Good: 16 ms	Good: 16 ms	Good: 24 ms	Good: 16 ms	Good: 16 ms	Good: 16 ms	Good: 24 ms	Good: 16 ms	Good: 24 ms
SaveSave, in the preferences dialog	Good: 24 ms			Good: 24 ms	Good: 32 ms	Good: 24 ms	Good: 24 ms	Good: 40 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: 16 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	665 KB+113 KB vs no CMP	584 KB+31 KB vs no CMP	651 KB+99 KB vs no CMP	675 KB+122 KB vs no CMP	806 KB+253 KB vs no CMP	706 KB+153 KB vs no CMP	764 KB+211 KB vs no CMP	638 KB+85 KB vs no CMP	717 KB+164 KB vs no CMP	1.09 MB+532 KB vs no CMP
UnpackedThe same bytes after decompression
DeferredBytes transferred after the first load settled
RequestsRequests during the first load	36+27 vs no CMP	18+9 vs no CMP	11+2 vs no CMP	13+4 vs no CMP	15+6 vs no CMP	11+2 vs no CMP	21+12 vs no CMP	13+4 vs no CMP	26+17 vs no CMP	18+9 vs no CMP
Third-partyRequests to other hosts during the first load	0	9	2	4	6	2	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	4 of 4 passed	3 of 4 passed1 could not run	3 of 4 passed1 could not run	4 of 4 passed	4 of 4 passed	4 of 4 passed	4 of 4 passed	3 of 4 passed1 could not run	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.