Why page weight matters
The analytics tool is supposed to measure how your site performs. It shouldn't be the reason your site performs worse. A heavy tracker quietly costs you across every metric you actually care about:
- Bounce rate. Visitors are impatient. Studies consistently show bounces rising sharply as load time climbs past 2 seconds. Every extra hundred milliseconds is a fraction of your traffic walking away before they read anything.
- Search ranking. Page speed is a Google ranking factor. A heavier script can quietly push your site down in results and cost you organic traffic before anyone even visits.
- Mobile. Most of your traffic is on mobile connections with limited data plans. A heavy script costs your visitors real data, real battery, and real seconds.
- Conversions. Slow pages lose signups, sales, and leads. Even a small improvement in load time has a measurable impact on revenue.
- Carbon. Lighter pages move less data and use less electricity. A heavy tracker on a million-pageview site adds up.
Why Google Analytics is so heavy
The Google Analytics 4 script is large because it has to be. It is the front end of a centralized platform built to support advertising, remarketing, audience building, cross-site tracking, and hundreds of standard reports. Most website owners never use the vast majority of those features. They pay the performance cost for all of them anyway, on every visit, on every page.
GA4 also makes multiple network requests per page load, not just one. Each one is a connection to an external Google server, adding latency on top of the script weight.
And the GA4 script is only part of the bill. Most sites running GA4 also load Google Tag Manager and a cookie consent banner from a tool like OneTrust or Cookiebot. Each of those is its own JavaScript bundle, each one running on every page, each one competing for the same render budget as your actual content.
Script size comparison
The numbers below are gzipped script weight from each vendor's own documentation. Cookie banners and tag managers are the realistic addition that most sites running GA4 also ship.
Why Clickport is lightweight
The size difference is not an accident. It comes from what we chose not to build.
Clickport tracks what most site owners actually care about: how many visitors came, where from, what they did, and how they engaged. We don't fingerprint, don't build cross-site profiles, and don't carry advertising or remarketing code. Less to collect means less script to do it. The full tracker, including scroll depth, visit duration, click tracking, file downloads, form submissions, and outbound link tracking, fits in roughly 2 KB minified.
There are also savings you only see when you compare the whole stack.
No cookie banner overhead
Because Clickport doesn't use cookies or collect personal data, you don't need a GDPR consent banner. Consent management platforms like OneTrust and Cookiebot are themselves JavaScript-heavy. Removing them removes another script, another render-blocker, and another vendor your visitors have to wait for. The savings compound.
Loads after your page renders
The Clickport tracker is loaded with defer and executes after the page has finished its first paint. It does not block the main thread during the initial render. Your Largest Contentful Paint and Interaction to Next Paint scores are not affected by the tracker.
One request per pageview, not five
Pageview events are sent as a single small POST request to the Clickport ingestion endpoint. There is no batched waterfall of script downloads, beacon pings, and remarketing pixels. One request, sent after the page is interactive, never on the critical render path.
EU-hosted, no transatlantic round trip
If your traffic is in Europe, GA4 sends every event across the Atlantic to a US server. Clickport is hosted in the EU on Hetzner infrastructure in Germany. For European visitors that is a meaningfully shorter network path on every request.
How to measure your site's actual weight
GTmetrix is a free tool that gives you a PageSpeed score, total load time, and total page size in one report. The Waterfall chart inside GTmetrix is the part that matters here: it shows every resource your site loads with its individual size and load timing. You can identify your analytics script in that list and see exactly what it adds to the page.
Run it once with your current analytics tool. Switch to Clickport. Run it again. The difference is usually visible in a screenshot.
Other ways to make your site faster
While you're auditing the analytics tracker, the rest of the page is worth a pass too. The actions that move the needle most:
- Question every new element. Most things you add to a page are not load-bearing. The cheapest performance win is the script or widget you don't ship.
- Audit third-party scripts. Chat widgets, social embeds, marketing tools, A/B test tools. Each one is a network connection and a render cost. Remove or replace the ones you don't actually need.
- Prefer system fonts. System fonts are already on your visitors' devices, so they add zero load time. Custom fonts are nice; they are also one of the biggest weight contributors on a typical page.
- Use fewer and smaller images. Images are usually the largest single category of bytes on a page. Resize and compress before upload. ImageOptim is a free tool for this.
- Use modern image formats. WebP and AVIF produce significantly smaller files than PNG or JPEG with no visible quality loss. All major browsers support them.
- Lazy-load below the fold. Images and videos below the initial viewport don't need to load until the visitor scrolls. Native lazy loading is one HTML attribute.