SlimStat vs Matomo

The privacy argument does not decide this one

Most comparisons on this site turn on where the data goes. This one does not. Matomo for WordPress stores everything in your own database — its plugin page states plainly that “All data is stored in your WordPress and not sent to any third party” — which is the same answer SlimStat gives. Anyone choosing between these two on privacy grounds has already got what they wanted from either.

What separates them is scale, in both directions: how much analytics you want, and how much server you have to spend on it.

Matomo is an application; SlimStat is a plugin

Matomo for WordPress runs the actual Matomo analytics platform inside your WordPress install. That is the source of its depth and the source of its cost, and Matomo is unusually straight about the second part. Three statements from its own plugin FAQ:

• “The minimum PHP memory limit is 128Mb, but we recommend to use a higher limit (memory_limit = 256M).”
• “Running Matomo Analytics on your server can use significant resources. Whenever someone visits your WordPress website, your server will need to serve your WordPress pages to the user, as well as tracking the user journey in Matomo, resulting in an additional request for each page view.”
• “If you have high traffic website, or manage a lot of websites with WordPress MultiSite, we recommend installing Matomo On-Premise or signup to Matomo Cloud and install the Connect Matomo plugin instead.”

That last one is the important one, and it is worth reading twice: past a certain traffic level, Matomo’s own advice is to stop running it as a WordPress plugin. That is not a criticism — it is a platform being honest about the shape of its own product.

SlimStat’s requirement, by comparison, is 32 MB of peak PHP memory for the tracker. It is a smaller thing doing a smaller job.

What you get for that weight

A great deal. Segments let you slice every report by arbitrary visitor conditions. Attribution models tell you which channel earned a conversion rather than which one was last. Ecommerce reporting tracks products, carts and revenue. The Visits Log, Transitions and Users Flow reports answer questions about paths through a site that SlimStat’s access log can only hint at.

If you need any of that, the comparison is over and Matomo wins it. SlimStat does not have segments, does not model attribution, and has no ecommerce reporting at all.

What SlimStat is for instead

The reader SlimStat suits wants the visit record and not an analytics practice. Every pageview lands as a row with its referrer, country, browser, screen size and the outbound links that visitor followed, and the reports are SQL queries over that table. You open the access log and read what happened. There is no archiving step, no report pre-computation, and nothing that needs a memory limit raised.

That narrower scope is also what makes the operational surface small enough to document completely: the tracking mode, the exclusion filters, geolocation and retention are most of the configuration there is. The free feature list is the rest.

Pro adds five goals, three funnels, heatmaps, scheduled email reports, a registered-user report and CSV export for $39 a year on one site — still less than Matomo asks for nothing, but also far less than Matomo gives.

Which one to choose

Choose Matomo if you want an analytics platform and have the hosting to run one: if segments, attribution or ecommerce reporting are on your list, if you want to import your Google Analytics history, if you report across many sites, or if a zero-cost open-source product is a requirement rather than a preference.

Choose SlimStat if you want a light, readable record of who visited and what they did, on ordinary shared hosting, without raising a memory limit or reading a platform manual. It is the smaller tool, deliberately, and on a site taking a few hundred thousand pageviews a month that is the difference between analytics you run and analytics that runs you.

If neither framing fits because the real question is still whether to leave Google Analytics, start at the alternatives page.