Trackum

Core Web Vitals: How Tracking and Cookie Banners Affect Them

LCP, INP and CLS depend on more than images and your theme. Tag Manager, pixels and cookie banners play a part too. Here is how to measure cleanly and improve in a targeted way.

Guide · · Updated · 6 min read · Written with AI, AI-assisted review on

Core Web Vitals: How Tracking and Cookie Banners Affect Them
📷 Chris Liverani · Unsplash

What do the Core Web Vitals measure?

Core Web Vitals are three metrics Google uses to judge how a page feels to visitors. Largest Contentful Paint (LCP) measures when the largest visible content has loaded. Interaction to Next Paint (INP) measures how quickly the page responds to clicks, taps and keyboard input. Cumulative Layout Shift (CLS) measures how much content jumps around unexpectedly. An LCP of up to 2.5 seconds, an INP of up to 200 milliseconds and a CLS of up to 0.1 count as good. The value assessed is the one that three quarters of page views reach or beat (the 75th percentile), separately for mobile and desktop.

In March 2024, INP replaced the older metric First Input Delay. The difference matters for anyone with a lot of tracking on the page: First Input Delay only measured the very first interaction, whereas INP looks at all interactions during the visit. Every click that triggers a tracking event therefore feeds into the assessment. If you attach many tags to clicks, you notice it here first.

Core Web Vitals at a glance
MetricWhat it measuresGood up toTypical influence from tracking
Largest Contentful Paint (LCP)Loading time of the largest visible content2.5 secondsScripts that start on load; a banner that appears late
Interaction to Next Paint (INP)Response to clicks, taps and keyboard input200 millisecondsMany tags on click triggers
Cumulative Layout Shift (CLS)Unexpected shifting of content0.1A banner bar that pushes content down

Google uses the Core Web Vitals as one of many signals in search. Good values alone will not lift a page if the content does not fit. Poor values, however, are a real problem for visitors: a page that jumps while you tap or hangs noticeably after a click loses enquiries and sales. For marketing managers, that is the more important reason to deal with them, because paid clicks from Google Ads and Meta land on exactly these pages.

Measuring Core Web Vitals: PageSpeed Insights and Search Console

For individual pages, PageSpeed Insights is the quickest route. At the top, the tool shows field data from the Chrome User Experience Report, meaning measurements from real visitors over the last 28 days. Below that comes lab data from Lighthouse, a single test measurement with a simulated device and a throttled connection. Field data is only available if a page gets enough visits from Chrome users. Small websites often lack it, and then only the lab measurement remains.

The lab measurement cannot measure INP directly, because nobody clicks there. Instead it shows Total Blocking Time, which is how long scripts block the browser’s main thread. This value is a good indication of whether tracking scripts are making the response time worse. For the whole website, you use the Core Web Vitals report in Google Search Console. It is also based on field data, groups similar pages together and rates them as “Good”, “Needs improvement” or “Poor”.

→ Cookie banner with Consent Mode v2: compliant, with no monthly licence

How tracking scripts burden LCP and INP

Every tag in Google Tag Manager loads code: the Meta Pixel, the LinkedIn Insight Tag, the TikTok pixel, heatmap tools, chat windows. Each of these scripts has to be downloaded, processed and executed. If that happens at the same time as the main image or the headline loads, LCP is delayed. The bigger effect, though, usually shows up in INP: if several tags have to finish their work after a click before the browser can show the response to that click, the page feels sluggish.

A typical pattern: over the years, an online shop has collected seven pixels, three of them for ad platforms that are no longer booked. Every click on “Add to basket” triggers events in all the pixels. The lab measurement shows a high Total Blocking Time, and in Search Console the product pages are rated “Needs improvement” for INP. After the old pixels are removed and the events are consolidated, the blocking time drops clearly, without a single relevant measurement going missing.

Cookie banners are a common cause of poor CLS values. This happens when the banner is inserted as a bar at the top of the normal page flow and pushes all the content down after it was already visible. For the visitor, the page jumps, and for Google, the layout shift value rises. A banner that sits over the page as an overlay, so with a fixed position, does not move existing content. According to web.dev, a newly inserted element only counts as a layout shift if it displaces other visible elements.

The banner can also play a role for LCP. If the banner itself is the largest visible content, for example on mobile, its loading time counts as LCP. Banners that first load several files and fonts appear late and push the value up. To check this, look in the diagnostics in PageSpeed Insights to see which element was identified as the Largest Contentful Paint.

→ Setting up Google Consent Mode v2 correctly: no warning in Tag Assistant

Improving Core Web Vitals: concrete measures for tracking

You do not have to give up tracking to reach good values. Usually it is enough to tidy up and control the order. The following measures bring the most in practice, without losing any measurement data.

  • Keep only the tags you need: remove pixels for platforms where you no longer advertise.
  • Load tags only after consent: without consent, only what may genuinely run without consent starts.
  • Load scripts asynchronously, so that they do not block the page from displaying.
  • Show the cookie banner as an overlay, not as a bar that shifts content.
  • Bundle click events, instead of building a separate click trigger for each platform.
  • Install the container code only once, not additionally through a plugin.

The point about consent has a double benefit. If marketing tags are only loaded after consent, you meet the requirements of § 25 TDDDG better and at the same time relieve the first page build, because no pixels load on the very first visit. This article is not legal advice. Technically, though, the rule is: what does not load cannot slow the page down.

Testing routine: how to find the bottleneck

Start with Search Console and see which page groups perform badly. Open a typical page from that group in PageSpeed Insights and note LCP, CLS and Total Blocking Time. Then open the developer tools in the Chrome browser, switch to the Performance tab and record a page view with a click. There you can see which scripts run for a long time and which domain they come from. You can recognise the domains of ad platforms and analytics tools by their names.

For a direct comparison, you can measure the page once with and once without consent in the banner. If the difference is large, the bottleneck is in the tracking. If it is small, it is more likely to be in images, fonts or the theme. That way you avoid removing pixels that are not the problem at all.

In Google Tag Manager itself, the preview helps. For each event in the timeline, from the loading of the container to every click, it shows which tags fired. If five or six tags hang on a simple click, that is a candidate for bundling. Also check which tags already start on the Initialization or Page View triggers. Everything that is not needed immediately can often load later, for example with the Window Loaded trigger.

Lean tracking without losing data: how Trackum helps

In the setup for €150 excl. VAT, Trackum builds Google Tag Manager, Google Analytics 4 and Consent Mode v2 so that tags only load after the appropriate consent and only the events you really need are measured. Everything is tested beforehand in preview, with and without consent. The Trackum cookie banner is a single 6.6 KB file and loads nothing further. If you want to know what is currently loading on your page, get in touch through the enquiry form.

Frequently asked questions

What are the Core Web Vitals?

Three metrics from Google for user experience: Largest Contentful Paint (loading time of the largest content), Interaction to Next Paint (response to input) and Cumulative Layout Shift (layout shifting). Good values are an LCP of up to 2.5 seconds, an INP of up to 200 milliseconds and a CLS of up to 0.1, each measured at the 75th percentile of page views.

What does CLS mean on websites?

CLS stands for Cumulative Layout Shift and measures how much visible content moves unexpectedly. A cookie banner that claims space at the top of the page after loading and pushes the content down is a typical trigger.

How can I measure Core Web Vitals?

The easiest way is PageSpeed Insights for individual pages and the Core Web Vitals report in Google Search Console for the whole website. Both use field data from real Chrome users from the Chrome User Experience Report, provided enough data is available.

Does Google Tag Manager make Core Web Vitals worse?

Google Tag Manager loads asynchronously, but its container code grows with every tag. Most tags also load code of their own. Many pixels, heavy scripts and tags that start immediately on page load mainly burden INP and, in part, LCP.

Sources

  1. web.dev: Web Vitals web.dev
  2. web.dev: Cumulative Layout Shift (CLS) web.dev
  3. Google Search Central: Core Web Vitals and Google Search results developers.google.com
  4. Search Console Help: Core Web Vitals report support.google.com
Help