Theme Performance Pulse
Short-lived storefront performance monitoring for OpenCart.
A lightweight OpenCart extension that captures coarse browser performance signals, keeps only a short-lived rolling snapshot in cache, and renders a live admin dashboard for operators — without custom analytics tables, Redis, or Node services.
Features
Operational monitoring for OpenCart without analytics sprawl.
Live Snapshot Dashboard
View current storefront health in one admin screen with summary cards, degraded-signal counts, incident hints, and recent-event rollups.
Core Web Vitals Summaries
Capture coarse browser-side performance signals so you can spot slow templates, degraded routes, and operational regressions quickly.
OpenCart Native Placement
Built as a normal OpenCart module with a Bootstrap 5 and OpenCart-native admin interface rather than a separate analytics app.
Short-Lived Cache Only
All live data stays in OpenCart cache with a rolling window. No custom analytics tables or long-term history are added to the store.
Privacy-Conscious Tracking
No IP addresses, visitor identifiers, or personal data are stored. The extension is intentionally operational, not behavioral analytics.
Preview Mode
Review the dashboard state safely without altering the live snapshot, making it easier to test UI flows during development or demo sessions.
How it works
Five steps from storefront event injection to live operator insight.
- 01
Storefront tracker loads
The extension injects a lightweight tracker on supported storefront routes through OpenCart events.
- 02
Browser metrics are sampled
The tracker captures coarse performance signals such as page views, Web Vitals summaries, optional long tasks, and optional add-to-cart delay.
- 03
Snapshot is updated
The server validates the request and writes the rolling snapshot into OpenCart cache with expiry and lightweight rate-limiting guards.
- 04
Admin dashboard refreshes
The module dashboard polls the current snapshot and re-renders summary cards, breakdown rows, and recent event data in place.
- 05
Old data expires
As the rolling window advances, stale metrics fall out automatically. No long-term analytics database or cleanup worker is needed.
Privacy by design
Theme Performance Pulse is intentionally operational, not analytical. The goal is current-store health, not long-term visitor surveillance.
- No IP addresses are stored in settings, cache, or custom tables.
- No visitor identifiers or personal data are collected.
- Only coarse operational performance signals are retained.
- All snapshot data is short-lived and cache-backed.
- No Redis, queue worker, WebSocket service, or Node backend is required.
- The extension is designed for operators, not shopper-facing surveillance.
Requirements
| OpenCart | 4.x |
| Tested up to | 4.1.0.3 |
| PHP | 8.3 or higher |
| Storage | OpenCart settings + built-in cache |
| Database | No custom analytics tables |
| Extra services | None required |
Installation
- 01 Upload the .ocmod.zip package through the OpenCart installer.
- 02 Go to Extensions → Extensions → Modules.
- 03 Install Theme Performance Pulse.
- 04 Open the module settings page.
- 05 Enable Module Status and Storefront Monitoring.
- 06 Visit storefront pages to start generating live samples.
Frequently asked questions
Does this extension create its own analytics database tables?
No. Theme Performance Pulse uses OpenCart settings for configuration and the built-in cache for the live rolling snapshot. It does not introduce custom analytics tables.
Is this meant for long-term analytics reporting?
No. The extension is designed for short-lived operational visibility. It helps merchants understand current storefront health, not maintain long-term historical analytics.
Does it track personal data or store visitor identities?
No. The extension avoids storing IP addresses, visitor identifiers, or other personal data. Captured signals are coarse and anonymous.
Can I review the dashboard without affecting live data?
Yes. Preview mode exists so you can inspect dashboard behavior safely without altering the live snapshot that operators rely on.
Will this require Redis, a queue worker, or a separate backend service?
No. The extension is intentionally lightweight and runs inside a standard OpenCart environment using controllers, events, settings, and cache only.
Ready to monitor your storefront health?
Open source, lightweight, and built to feel native inside OpenCart.
MIT · Developed by Devlin Duldulao