Written for Cookie Rocks 2.9.14, checked on 5 November 2026. The current version is 2.11.2: some details may have changed.
What this screen is for. The Weight screen shows what the cookie banner you already use adds to your home page, next to the weight of the Cookie Rocks banner.

What to do here
- If the screen says Not measured, analyse the site on the Cookies screen, then come back.
- Compare the size of your banner with the last row, For comparison: the Cookie Rocks banner.
The screen has no settings. Every visitor downloads these files, so a heavy banner slows down each first visit.
Tip. Analyse the site again after you change your banner or its settings. The size comes from the last analysis.
Cookie Rocks Audit itself adds nothing to your visitors’ pages: no script and no style. Only the cookie policy shows, on the page where you place its shortcode.
Every row on this screen
The screen is titled What your cookie banner adds to your pages. “What every visitor downloads for the cookie banner, measured by the last analysis. Compressed size, as it travels over the network.” The first row shows one of these:
- Your current cookie plugin and the size of its banner in kB: “On your home page.” The size is marked as a point to fix when your banner is heavier than the Cookie Rocks banner on a first visit.
- Your current cookie plugin, Not measured: “Run a scan on the “Cookies” page. A banner served from its publisher’s servers cannot be measured.”
- Your banner, None found: “Your site has no cookie banner.”
The last row, For comparison: the Cookie Rocks banner, followed by its version number, gives its size on a first visit. It adds: “Then … on every page for a visitor who has already chosen.” These figures come with the plugin, for its current version.
At the bottom of the screen, a box titled With the Cookie Rocks banner sums up its weight, with the same two sizes as the last row, and nothing loaded from another server. Click Hide: it does not come back for your user account.
How the size is measured
The size comes from the last analysis, run on the Cookies screen. While it opens your home page, the analysis adds up the compressed size of the files each plugin loads from your site. The Weight screen shows the total for the plugin of your banner.
Files loaded from another server are not counted. That is why a banner served by its publisher shows Not measured.
On our test sites, the Cookie Rocks banner adds 11.43 kB to a page on a first visit, then 1.00 kB to each next page. Each version is also measured with Lighthouse, with and without the banner. See how we measure.
With Cookie Rocks Pro
With Pro, the screen is titled What Cookie Rocks adds to your pages. It is measured on your site, with your settings. Sizes are compressed (gzip). A file already downloaded is kept by the browser: from the second page on, only the part written in the page travels again.
- Three figures: written in each page, for a visitor who has already chosen, at most, and on a first visit, banner shown.
- Total, by type of file: one bar for a visitor who has already chosen, one for a first visit, split into what is written in the page, JavaScript and CSS.
- Piece by piece: each piece, its size before and after compression, why it weighs that much and when it loads. Some pieces load only when needed: held videos, maps and forms, the cookies to erase after a withdrawn consent, the style of the elements in your content. A label marks the heaviest piece Heaviest, a piece under 1 kB Featherweight, and the others Middleweight.
- Engine options: “Each site gets an engine with only the options it uses.” The table gives the size of the Base engine, then what WP Consent API, Record of consents and Advanced settings add, in bytes, each marked Used here or Not loaded. Advanced settings cover rules by country, a site aimed at children, the Global Privacy Control signal, a site aimed at the United States and a custom place for the cookie button.