Start Learning
Plugins & Tools

Lightweight WordPress Analytics Plugins: I Measured 10 on a Clean Install

Ellie Vanderstaat Ellie Vanderstaat 13 min read
Lightweight WordPress Analytics Plugins: I Measured 10 on a Clean Install

Five of the ten WordPress analytics plugins I tested call themselves lightweight.

Only two say how light.

So I put all ten on one clean test site, one at a time, and weighed what each adds to the page, the server, the database and wp-admin. They’re some of the most-installed free analytics plugins on WordPress.org.

Tested on WordPress 7.1.4 with the Twenty Twenty-Five theme, PHP 8.3 and MySQL 8.4, on November 4, 2026. Plugin versions are in the test notes near the end.

I expected to rank ten trackers by size. On the page there isn’t much to rank, because all of them are small.

Then I opened wp-admin.

The three heaviest Dashboards each carry over thirteen times what the heaviest tracker puts on a page.

A small script doesn’t make a light plugin. The weight sits in two places a byte count never shows. One is the visit your server has to record on every single page view. The other is the code a plugin loads into your own wp-admin.

You don’t need to read code for any of this.

Still choosing a plugin for its reports or its price? My guide to the best WordPress analytics plugin covers prices, reports and cookie banners.

On the page: what your visitors download

Start with the part your visitors feel. Each plugin puts some code of its own on every page you publish, as a script file, as a few lines written into the page itself, or both.

I weighed that code compressed, the way most hosts send it.

The chart has the six plugins that count visits inside your own WordPress. The four Google plugins come right after it, because their number means something else.

Slimstat’s tracker weighs about 33 times as much as Koko’s. Even so, all six stay under 31 KB.

Koko manages without a script file at all. Its tracker is a few lines written straight into the page. Independent Analytics works the same way.

Now the Google plugins.

On paper, one of them is the lightest plugin in the whole test. GA Google Analytics added about 170 bytes of its own. MonsterInsights and ExactMetrics added 5.5 KB each.

Don’t hold those numbers against the chart.

A Google plugin is there to place Google’s tag, a separate file called gtag.js that loads from Google’s servers and does the real work.

My test site had no internet access. I could count that request but couldn’t weigh the file, so add it on top before you compare.

Site Kit gave me nothing to weigh.

The plugin can’t place Google’s tag until you sign in with a Google account. I left it unconnected.

If a lightweight WordPress analytics plugin means a small download for your visitors, every plugin on that chart passes. The whole difference between its best and its worst is under 30 KB.

On your server: the tracking hit a page cache can’t hide

A tracker has to tell someone about every visit. Each time a page opens, it sends a small request with the details. I’ll call that request the tracking hit.

The Google plugins send it to Google. The other six send it to your own server.

A page cache doesn’t help here. The cache hands your visitor a saved copy of the page, so WordPress doesn’t have to build it again. The tracking hit still arrives, once for every page view, and something on your server has to answer it.

MonsterInsights turns this into a sales point. Its FAQ says native WordPress stats plugins “will always slow down your website because they rely on your WordPress hosting server”.

So I timed it.

For each plugin I measured how long my server took to answer one hit. As a yardstick, the chart also marks how long the same server needed to build the home page when no analytics plugin was installed at all.

I didn’t expect that spread.

Two plugins spend about as long recording a visit as WordPress spends building the whole page. WP Statistics spends a good deal longer.

Koko is done in a fraction of a millisecond. “Always” doesn’t hold.

The gap comes down to what has to wake up. Koko sends its hit to a tiny file of its own that never starts WordPress. A single line goes into a buffer, and a scheduled task moves the buffer into the database later.

WP Statistics, Independent Analytics, Matomo and Slimstat start WordPress for every single hit.

Burst sits in between.

Its hits go to a fast endpoint of its own, but there are two of them per page view, one when the page opens and one when the visitor leaves.

Your visitor doesn’t wait for any of this, because the hit travels in the background. The cost lands on your server. On a busy site that sits behind a page cache, that one hit can be the only real work the server does for each visitor.

Building the page is the cheaper half.

Seven plugins out of ten added between one and four database queries per page, and I couldn’t measure any change in build time. Independent Analytics was the exception, with 30 extra queries and about 4 ms more on every page.

Your server will give different times than mine. Use these to compare one plugin with another, and don’t read my milliseconds as a forecast for your host.

In your database: what 100 page views leave behind

All six self-hosted plugins create their own database tables the moment you activate them. Koko made 5, Slimstat 6 and WP Statistics 7, while Burst made 24, Independent Analytics 27 and Matomo 44.

Forty-four tables sounds alarming. With my test data inside, all of them together came to about 1.5 MB.

A database grows by rows, the lines a plugin writes as visits come in. I sent each plugin the same 100 test page views and counted what it added.

Koko’s number isn’t a typo.

The plugin keeps one running total per page per day. My 100 views went to four pages, and three of them it had already counted that day. It added two rows for the new page and updated its totals for the rest.

Slimstat, Matomo, Independent Analytics and Burst write a row for every page view, and most of them add rows for visitors and sessions on top.

WP Statistics landed just under one row per view.

That choice decides how your database grows. With Koko it grows with the pages you publish and the days that pass. With the other five it grows with your traffic, so a good month for your blog is a big month for your database.

Take a blog with 500 page views a day. At one row per view, that’s about 15,000 new rows every month, before visitors and sessions are counted.

One more thing lands in the database.

Each plugin saves a few settings that WordPress loads on every request, needed or not. Koko added 3 of these and Matomo 17. No plugin went over 5 KB.

In wp-admin: where the heavy plugins are heavy

Your visitors never see this part. You do, every time you log in.

I opened the Dashboard with each plugin active and weighed the extra scripts and styles it pulled in. The measure is the same as in the first chart.

Each of the top three loads over five times more code into a single Dashboard visit than all ten trackers together put on a page.

GA Google Analytics and Site Kit aren’t on the chart, because they added nothing.

A fair warning about these numbers. Your browser keeps a copy of the files and won’t download them fresh on every visit. The browser still has to run them each time the Dashboard opens.

Here’s what MonsterInsights put on my Dashboard in exchange.

What MonsterInsights showed for 426 KB: a setup prompt
MonsterInsights widget on the WordPress Dashboard of the test site. It reads: Your website analytics dashboard is not currently configured. Please use our setup wizard to get started. Below is a Set Up Website Analytics button
MonsterInsights Lite 11.3.0, test site Dashboard · November 4, 2026

I’d typed in a measurement ID by hand. For tracking, that’s enough.

The reports stay locked until you connect the plugin through MonsterInsights’ own site. A notice said so on the Dashboard and again on the Posts list.

ExactMetrics did exactly the same. The two plugins share their developers and weighed the same on the page.

WP Statistics surprised me most, because it’s so modest on the front end. One Traffic Overview widget sits on the Dashboard, with 13 more waiting in Screen Options. Open your Posts list, where it adds a Hits column, and another 368 KB loads.

Slimstat goes the other way and shows everything. The Dashboard fills with 18 widgets, and 17 background requests fire once the page has loaded.

Matomo and Koko barely register. Matomo gets there by keeping its reports on a screen of their own.

I didn’t time how this feels in a real browser, because that depends on your computer and your connection. The heavy plugins still put far more code in front of you than in front of your visitors.

Which plugins phoned home

The test site was cut off from the internet on purpose. Every request a plugin sent to the outside world failed and landed in my log.

Seven of the ten tried.

Four wanted a location database, the file that lets a report show countries or cities. Those were Independent Analytics, Burst, Matomo and Slimstat.

Four wanted their own news feed, the one that brings a plugin’s notices into your admin screens. Slimstat is on this list too, next to WP Statistics, MonsterInsights and ExactMetrics.

Every one of those requests asked for a file that a normal host would simply have delivered.

Koko, GA Google Analytics and Site Kit asked for nothing. Site Kit may behave differently once it’s connected to Google.

The exact servers are in the test notes near the end, in case you run a firewall or keep a list of the services your site talks to.

Plugin by plugin

Short notes on each plugin, in case you came here for one name. Every claim comes from my test site or from the plugin’s own page.

Koko Analytics

Koko’s plugin page promises it “adds less than 1 KB to your HTML”. On my test site it added 0.9 KB. The claim holds.

One surprise for a plugin that sells itself on privacy. Out of the box it set a cookie that expires at midnight. The FAQ says cookies are optional. Switch them off in the settings if you’d rather go without.

Light doesn’t mean empty. Its report still counts visitors and pageviews page by page.

For the full tour, read my Koko Analytics review.

Independent Analytics

No cookies showed up, just as its plugin page promises.

The busy side is the database. Each tracking hit went through WordPress and ran 51 queries. Most of the 30 extra queries on a normal page are quick reads of the plugin’s own settings and cost little time.

In wp-admin you get a Views column in your Posts list. I liked having it there.

WP Statistics

For your visitors it’s modest, with one small script and no cookies.

For your server and for you it’s the opposite. WP Statistics had the slowest tracking hit in my test and one of the three heaviest Dashboards. If you like its reports, you can make that trade with open eyes.

MonsterInsights and ExactMetrics

Both want you signed in first. On my first wp-admin visit after activation, each plugin sent my browser straight to its own server to start a setup wizard.

For how MonsterInsights compares with Google’s own plugin, see MonsterInsights vs Site Kit.

Burst Statistics

Burst’s plugin page mentions “a tiny tracking script under 4 KB”. On my site the main script came to 5.4 KB. A 2 KB helper that measures time on page loads next to it.

Still small, to be fair.

Burst set a cookie that lasts 30 days. The FAQ says there’s a cookieless option. Turn it on before launch if you want no cookies. Your first wp-admin visit after activation opens a setup wizard.

Matomo for WordPress

Matomo is a full analytics platform living inside WordPress, and the numbers show it.

Tracking is switched off until you turn it on. Once it’s on, Matomo sets two cookies by default, one that lasts 13 months and one that lasts 30 minutes.

The Matomo for WordPress walkthrough covers the setup and the cookieless option.

Slimstat

The heaviest tracker in my test is a single 30 KB file. Before compression it’s 80 KB.

Slimstat set a cookie that lasts 30 minutes, and its FAQ says you can track without one. Turn off “Set tracking cookie” and turn on “Hash IP addresses” under Settings, then Tracker.

GA Google Analytics

One job, and nothing else. The plugin pastes Google’s tag into your pages and gives you a settings page. No tables, no Dashboard widget, no calls to a server of its own.

Site Kit by Google

Even unconnected, Site Kit read 9 of its settings from the database on every page. All nine together took well under a millisecond.

Once you connect it, it adds Google’s tag like the others. I didn’t connect it, so I can’t give you that number.

How I ran the test, and where it can mislead you

Each plugin got the same fresh WordPress with three test pages. Before every one I restored the same database and the same files, to make sure nothing carried over.

I left out Jetpack, where stats are one module inside a much bigger plugin, and simple view counters that have no reports of their own.

I kept the default settings and changed only what a plugin needs before it counts anything. For Matomo that meant switching tracking on. Three of the Google plugins got a made-up measurement ID.

Every page was loaded five times in a fresh Chrome window, logged out, with the browser cache off. For the server numbers I requested each page at least 25 times and took the middle value.

The database numbers come from 100 page views spread over 20 browser sessions.

Now the ways this can mislead you.

One test site, one theme and no other plugins. Yours will weigh more.

Defaults are a trap too. Koko, Burst, Matomo and Slimstat all set a cookie out of the box, and all four have a setting to run without one. Change it before you go live.

Versions move fast as well. Six of the ten plugins shipped an update in the two weeks after my test. Check the version numbers in the notes below against yours.

Test notes: versions, every number and the servers each plugin called

These are my notes from the test on November 4, 2026, with every plugin and every number in one place. Sizes are gzip-compressed, the way most hosts send files, and 1 KB means 1,000 bytes, the same unit Chrome’s developer tools use.

Plugins and versions tested

Plugin Version Active installs
Koko Analytics 2.5.3 70,000+
Independent Analytics 2.16.2 100,000+
WP Statistics 14.16.18 500,000+
Burst Statistics 3.7.4 200,000+
Matomo for WordPress 5.13.1 100,000+
Slimstat 6.0.0 70,000+
GA Google Analytics 20260810 400,000+
MonsterInsights Lite 11.3.0 2 million+
ExactMetrics Lite 10.3.0 200,000+
Site Kit by Google 1.191.0 5 million+

Install counts are the ones WordPress.org showed on November 4, 2026.

On the page

Code means the plugin’s own scripts and styles plus anything it writes into the page. Each number is the median across my three test pages.

Plugin Code per page Extra requests
Koko Analytics 0.9 KB +1
Independent Analytics 2.3 KB +1
WP Statistics 3.8 KB +2
Burst Statistics 7.5 KB +4
Matomo for WordPress 22.6 KB +2
Slimstat 30.4 KB +2
GA Google Analytics 0.2 KB + gtag.js +1
MonsterInsights Lite 5.5 KB + gtag.js +2
ExactMetrics Lite 5.5 KB + gtag.js +2
Site Kit by Google 57 bytes, not connected 0

Cookies set by default

Plugin Cookies
Koko Analytics 1: _koko_analytics_pages_viewed, until midnight
Independent Analytics None
WP Statistics None
Burst Statistics 1: burst_uid, 30 days
Matomo for WordPress 2: _pk_id for 13 months, _pk_ses for 30 minutes
Slimstat 1: slimstat_tracking_code, 30 minutes
GA Google Analytics, MonsterInsights Lite, ExactMetrics Lite Google’s, set by gtag.js
Site Kit by Google None until connected

On the server

Without any plugin, my three test pages needed 21 to 31 database queries and 50 to 62 ms to build. Two runs of the same plugin-free site differed by up to 3 ms, so I only report build-time differences above that.

Plugin Extra queries per page Each tracking hit
Koko Analytics +1 to 2 1 per page, 0.3 ms, skips WordPress
Independent Analytics +30, and +4 ms build time 1 per page, 52 ms, 51 queries
WP Statistics +1 1 per page, 90 ms, 15 queries
Burst Statistics +4 2 per page, 9 ms and 24 queries each
Matomo for WordPress +1 1 per page, 60 ms, 18 queries
Slimstat +2 1 per page, 22 ms, 15 queries
GA Google Analytics 0 Goes to Google, not your server
MonsterInsights Lite +3 Goes to Google, not your server
ExactMetrics Lite +3 Goes to Google, not your server
Site Kit by Google +9 None until connected

In the database

Plugin New tables and their size Rows added by 100 page views
Koko Analytics 5 tables, 147 KB 2
Independent Analytics 27 tables, 1.3 MB 119, of which 100 are page views
WP Statistics 7 tables, 492 KB 97, in three tables
Burst Statistics 24 tables, 1.4 MB 150, of which 100 are page views
Matomo for WordPress 44 tables, 1.5 MB 109, of which 100 are page views
Slimstat 6 tables, 705 KB 100

Autoloaded settings are the ones WordPress loads on every request.

Plugin Autoloaded settings added
Koko Analytics 3, or 0.9 KB
Independent Analytics 13, or 3.9 KB
WP Statistics 9, or 2.7 KB
Burst Statistics 9, or 1.7 KB
Matomo for WordPress 17, or 4.5 KB
Slimstat 15, or 4.2 KB
GA Google Analytics 1, or 0.5 KB
MonsterInsights Lite 10, or 4.4 KB
ExactMetrics Lite 10, or 4.3 KB
Site Kit by Google 2, or 0.2 KB

In wp-admin

Scripts and styles each plugin adds to two admin screens.

Plugin Dashboard Posts list
ExactMetrics Lite 438.3 KB 17.9 KB
MonsterInsights Lite 425.7 KB 18.0 KB
WP Statistics 407.7 KB 367.7 KB
Slimstat 298.8 KB 9.9 KB
Independent Analytics 96.1 KB 2.4 KB
Burst Statistics 54.0 KB 0
Matomo for WordPress 8.2 KB 8.2 KB
Koko Analytics 7.6 KB 0
GA Google Analytics 0 0
Site Kit by Google 0 0
Plugin Dashboard widgets Extra queries on the Dashboard
ExactMetrics Lite 1 +34
MonsterInsights Lite 1 +34
WP Statistics 1, and 13 more in Screen Options +13
Slimstat 18 +27
Independent Analytics 1 +42
Burst Statistics 1 +23
Matomo for WordPress 0 +2
Koko Analytics 1 +11
GA Google Analytics 0 +1
Site Kit by Google 0 +11

What else each plugin puts into wp-admin:

  • ExactMetrics Lite: ExactMetrics menu, notice asking you to sign in.
  • MonsterInsights Lite: Insights menu and toolbar button, notice asking you to sign in.
  • WP Statistics: Statistics menu, Hits column, Online counter in the toolbar.
  • Slimstat: SlimStat menu, Online and Heatmap in the toolbar, 17 background requests after the Dashboard loads.
  • Independent Analytics: Analytics menu, Views column, opt-in notice.
  • Burst Statistics: Statistics menu, Pageviews column, setup wizard.
  • Matomo for WordPress: Matomo Analytics menu.
  • Koko Analytics: Dashboard widget.
  • GA Google Analytics: a settings page, nothing else.
  • Site Kit by Google: Site Kit menu.

Servers each plugin tried to reach

  • Independent Analytics: assets.independentwp.com, for a geolocation database, on activation.
  • Burst Statistics: burst.ams3.cdn.digitaloceanspaces.com, for a country database, on the first wp-admin visit.
  • Matomo for WordPress: download.db-ip.com, for a city database, on activation.
  • Slimstat: cdn.jsdelivr.net for a city database, and connect.wp-slimstat.com for its notifications feed.
  • WP Statistics: connect.wp-statistics.com, for its notifications and marketing campaigns feed.
  • MonsterInsights Lite: plugin-cdn.monsterinsights.com, for its notifications feed.
  • ExactMetrics Lite: plugin-cdn.exactmetrics.com, for its notifications feed.
  • Koko Analytics, GA Google Analytics, Site Kit by Google: nothing. Site Kit wasn’t connected, so that may change once it is.

MonsterInsights and ExactMetrics also sent my browser to connect.monsterinsights.com and connect.exactmetrics.com on the first wp-admin visit after activation.

How the test ran

  • A fresh WordPress 7.1.4 install with the Twenty Twenty-Five theme and three test pages: the home page, a blog post and a regular page.
  • One plugin at a time. Before each plugin, I restored the same database and the same files.
  • Default settings. I only changed what a plugin needs before it counts anything.
  • Matomo ships with tracking switched off, so I switched it on.
  • MonsterInsights, ExactMetrics and GA Google Analytics got a made-up GA4 measurement ID. Site Kit only accepts one through a Google sign-in, so it stayed unconnected.
  • Each page loaded five times in a fresh Chrome window, as a logged-out visitor, with the browser cache off.
  • For the server side, I requested each page at least 25 times and took the median time and number of database queries.
  • Then 100 test page views from 20 browser sessions, to see what lands in the database.
  • The test site had no internet access. I logged every request a plugin tried to send to an outside server.

How to check a plugin on your own site

You don’t have to trust my numbers.

Ten minutes in your own browser will give you better ones, because they’ll include your theme and your other plugins.

Page weight. Open one of your posts in a private browser window and press F12. Go to the Network tab, tick “Disable cache” and reload the page.

Now type the plugin’s folder name into the filter box, for example wp-statistics or burst. Every file it loads is listed with its size.

The tracking hit. Clear the filter and watch for a request that shows up after the page has finished loading. You’ve found the hit. The Time column tells you how long the answer took to arrive.

Cookies. Same panel, Application tab, then Cookies, then your domain. Anything new after a fresh page view came from a plugin.

Database queries. Install the free Query Monitor plugin. It groups every query by the plugin responsible, so you can see what your analytics plugin adds to each page.

Database size. Go to Tools, then Site Health, then Info, and open Directories and Sizes. Write down the database size today and look again in a month.

Lightweight WordPress analytics plugins: FAQ

Do analytics plugins slow down WordPress?

Not much on the page itself.

Every plugin I tested added under 31 KB of its own code, and the lightest added under 1 KB. The bigger costs are the tracking hit that your server has to answer on every page view and the scripts some plugins load into wp-admin.

What is the lightest WordPress analytics plugin?

Among plugins that count visits themselves, Koko Analytics. Koko added 0.9 KB to each page, and its tracking hit never starts WordPress. GA Google Analytics adds even less of its own, about 170 bytes, but it hands the real work to Google’s tag.

Does a caching plugin make analytics free?

No. A page cache serves the saved page without running WordPress, but the tracker still sends its hit to your server after the page has loaded.

Four of the six self-hosted plugins I tested start WordPress for every one of those hits.

How much database space does an analytics plugin need?

That depends on how the plugin stores visits. Four of the plugins I tested write a row for every page view, while Koko keeps daily totals per page.

After 100 test page views, their tables ranged from 147 KB for Koko to about 1.5 MB for Matomo.

Is a Google Analytics plugin lighter than a self-hosted one?

Its own code often is. Every Google plugin also loads Google’s tag from Google’s servers. That file isn’t in my numbers. Count it in before you compare.

Ellie

Written by Ellie

Former Head of Analytics at a European digital agency. 8+ years making WordPress analytics make sense. I write the guides I wish existed when I started.

More about me →