SlimStat Free 6.1.2 builds on a more efficient SQL foundation: 50% fewer weekly-chart row reads, about 50% fewer sort rows, 68% fewer option updates per stored pageview and 99% fewer per refused bot in the recorded v6 development measurements. It combines that foundation with prioritized report loading and better reuse of cached results.
If your hosting assessment comes from SlimStat 5.5 or an older version, the current architecture gives you concrete reasons to evaluate it again. The product now avoids duplicate chart aggregation, reuses eligible results and controls when report requests start. These improvements are included in Free; Pro adds tools for turning the collected data into decisions.
What changed from the older SQL approach?
SQL is the language SlimStat uses to read and write its analytics database. The v6 changes make that work more efficient by sharing query results, reusing cached data and prioritizing the reports you are viewing.
In the v5.5 chart code, chart buckets and totals were fetched separately. The reviewed v6 chart implementation obtains both from one grouped result instead of two queries. It avoids asking the database to repeat the same aggregation just to display a total above the chart.
That is a specific architectural improvement over v5.5. Versions older than 5.5 varied, so the figures below should not be treated as a benchmark of every historical release.
| Work measured during v6 development | Before | After | Reduction |
|---|---|---|---|
| Weekly-chart row-read counter, 150,000-row corpus | 304,454 | 152,227 | 50% fewer reads |
| Weekly-chart sort-row counter, same corpus | 212,301 | 106,141 | About 50% fewer sort rows |
| Average option updates per stored pageview | 3.22 | 1.03 | About 68% fewer option updates |
| Average option updates per refused bot | 1.80 | 0.02 | 99% fewer option updates |
The chart figures are operation counters from the recorded v6 comparison, not a new 6.1.2 timing run. Option-write figures come from the separate corrected tracking comparison on a roughly 443,000-row installation (WordPress 7.0.2, PHP 8.2, MySQL 8.0.35). The refused-bot comparison used 70 requests before and 65 after. See the measurement provenance. Each figure describes the operation named in the table. Together they demonstrate specific reductions in database work; they are not page-load timings.
Percentage reductions use (before − after) ÷ before × 100, rounded to whole percentages. For hosting teams, that is a concrete reduction in the work the database performs for these operations.
What Free 6.1.2 adds to that foundation
Load the reports you are approaching
With Async mode enabled, the report loader prioritizes widgets near the viewport and defers offscreen widgets until you scroll toward them. It allows up to three active loading requests and can batch eligible reports. A page with many reports does not need to start all their work at once.
This gives visible reports priority and keeps the initial request burst controlled. More reports load as you approach them, matching the work to the way you use the page.
Reuse results instead of repeating them
Historical report results can be cached. Charts can reuse results for a range that includes today with bounded freshness, instead of recalculating the entire history on every refresh. Ecommerce’s cache identity also allows Copy Prompt to reuse the report result already produced by the page when its scope matches.
Cache entries preserve the report’s dates, filters, permissions and database context, so reuse stays tied to the question you asked.
Show a dashboard widget when it is ready
The release corrects synchronous Dashboard loading on upgraded sites and removes the extra fade delay after widget data arrives. Report pages also avoid loading the Settings code editor. These are distinct improvements: less initial waiting and unnecessary browser work, alongside the SQL changes.
Keep AI out of routine visit collection
Free Copy Prompt runs when you choose it. Pro AI Analysis calls a provider only after you request analysis. Opening a saved AI result does not call the provider again. Ordinary visits do not trigger an AI request.
A lighter SQL workload for WordPress hosting
SlimStat is built for high-performance, self-hosted WordPress analytics. The improvement is in how it handles the workload: combine repeated aggregations, reuse existing results, prioritize visible reports and reduce repeated option updates during tracking.
| What matters to a hosting team | How the current architecture helps |
|---|---|
| Database work per chart | One grouped result supplies both buckets and totals; measured weekly-chart reads fell by 50% |
| Repeated report requests | Eligible cached results answer the same reporting question without repeating its aggregation |
| Initial Dashboard demand | Async mode prioritizes nearby widgets and caps active report-loading requests at three |
| Tracking-related option writes | Recorded averages fell by 68% per stored pageview and 99% per refused bot |
| Optional AI processing | Analysis runs on request; ordinary visits and reopened saved results make no AI-provider call |
Evaluate this architecture when reviewing SlimStat for a hosting environment. An assessment of the old duplicate-query chart path does not describe how the current chart works.
The hosting guide explains how to combine asynchronous reporting, retention, caching and optional capture settings for your site. Use the same reporting period and filters when measuring the benefits on your hosting.
Review the recommended hosting setup · Evaluate SlimStat Free
A practical upgrade and performance check
- Back up your site and analytics database. If you use external storage, back that up too.
- Update Free first, then Pro, and review pending Migration steps. A database update can take time and is different from everyday report loading.
- Check Settings → Reports → Async mode. Existing settings and upgrade recovery can affect what is enabled.
- Use Client tracking behind a page cache, and keep tracking requests uncached. Server mode only records requests that reach WordPress.
- Compare the same report, dates and filters before and after. Measure first loads and repeat loads separately; a warm cache answers a different question from a cold request.
- Set retention and optional heatmap sampling to the history and interaction detail you need. These controls help keep collection and storage focused.
Keep the report, period and filters with your measurements. A repeatable comparison shows which improvements matter most for your own reporting workflow.
When does Pro make sense?
You do not need Pro to receive the Free plugin’s core performance improvements. Upgrade when you want more value from the data you collect:
- AI Analysis: interpret eligible reports inside WordPress and revisit private saved results. Requires WordPress 7+, a connected provider and a valid site license; provider charges may apply.
- City-Level Insights: expand a country’s leading city into the available city breakdown.
- Visual heatmaps and funnels: see interaction patterns and where recorded journeys stop before a conversion.
- Deeper store reports, exports and scheduled emails: compare campaigns and share findings with your team.
- Custom DB: let your hosting team separate analytics storage from the main WordPress database, with the legacy upgrade and outage behavior documented.
Compare every Free and Pro feature. All Pro plans include the same features; choose the number of sites you manage.
Common questions
Does SlimStat still use SQL?
Yes. SlimStat stores analytics in your configured database. The newer architecture makes that SQL work more efficient by removing duplicate aggregation and reusing eligible results.
Does half the row reading mean twice the speed?
The measurement establishes half the row reads for the tested weekly chart. It describes database work, so a timing comparison should be measured separately on the same site and workload.
Are all the gains new in 6.1.2?
No. The chart and option-write evidence comes from v6 development and shipped in Free 6.0. Free 6.1.2 adds report scheduling, caching and Dashboard refinements on top of it. The release history separates the changes.
Where can I verify the implementation?
Read the pinned chart implementation, report loader, Ecommerce report cache and upgrade guide. The numbers above describe historical development measurements, not a fresh benchmark run for this article.
