Sin impuesto Con impuesto
RKR Diagnostics: diagnostics and performance profiler for PrestaShop

RKR Diagnostics: diagnostics and performance profiler for PrestaShop

€108.78
First year:€108.78tax incl.
From the second year:€27.20/yeartax incl.
  • One year of technical support and lifetime updates; from the second year, support is extended for €27.20/year and includes taking on your general improvement ideas for the module.
  • Renews automatically; cancel whenever you want, with no minimum term.
One-time payment:€108.78tax incl.
  • One year of technical support and lifetime updates; after that, support ends (with the subscription it is extended for €27.20/year).
  • A single payment, with no automatic charges.
€89.90 + VAT = €108.78

A progress bar on each page displays the time, memory, SQL queries, hooks, and PHP errors of the request, along with a history of statistics and a mode that disables modules specifically for your browser. Find what's slowing down your store without impacting production.

Compatible with PrestaShop 1.7.8 to 9.2. Rekire module, tested in real stores.

Try the demo

Front officeBack office

Diagnosis and performance

Your store is slow and you don't know why. Stop guessing.

A module, a repetitive SQL query, a resource-intensive hook: any of these could be the culprit, and without measuring, you're left blindly disabling things in production. RKR Diagnostics displays a bar on each page showing the actual cost of that request and tells you what's slowing it down.

2 hours
The troubleshooting mode session lasts only in your browser: your visitors won't know.
8 indicators + 6 charts
Use statistics to see the health of the store at a glance
1.7.8 → 9.2
a single version of the module for all your PrestaShop stores

See the cost of each page on the page itself.

A bar in the back office, and in the store only for your admin session, showing request time , memory usage, SQL queries, and PHP errors. No need to open logs or install anything on the server to view the basics.

Slow and duplicate SQL queries
You can see which ones take longer than the threshold you set (50 ms by default) and which ones are repeated, and who launches them.
Time per hook and per module
You discover which module is consuming the page's time, instead of suspecting them all.
PHP errors in the request
The warnings and errors appear next to the page that causes them.
Active overrides
A list of your store's overrides and which modules include them, to understand what's affecting the codebase.

/ History and statistics so you don't depend on luck

Each request is saved in a history log, filtered by range, store, slowness, or errors. By default, it's kept for 7 days, but you decide how long. The statistics show the evolution of requests, the heaviest modules, and the times with the most errors, allowing you to verify whether a change has improved anything. The module is self-protecting: it stores a maximum of 800 queries per request.

Find the culprit module without breaking the store

Troubleshooting mode disables the modules you choose for your browser only, using a signed cookie that expires after 2 hours. Your customers continue to see the store as usual. You shut down, refresh, check if the problem disappears, and continue until you isolate the conflict. RKR Diagnostics itself never disables itself.

Designed for production. Query values are hidden in the history by default, URL tokens are also hidden, and the store bar is sent marked so that no page cache saves it and serves it to another visitor.

What worries us

Who can see it?
Only super administrators have access by default. You can open it to employees with permissions in the module's settings tab.
Optional overrides
To measure SQL and hooks, you install them with a button, not beforehand. They never affect overrides from other modules, and if you're already using PrestaShop's native profiler, the module detects it.
Weight
Capture is turned off with a master switch in Settings.
To try it risk-free
14-day demo data with one click, and a button to remove it. Inside you'll find a guide explaining each screen.
To your liking
24 visual themes, import and export settings or history, multi-store and translatable texts from International > Translations.

Install it, let it capture for a couple of days and first look at Hooks and modules : usually two or three will be most of the time.

Compatible with PrestaShop 1.7.8 to 9.2 PHP 7.1 to 8.4

Developed and maintained by REKIRE

  • Reference
    rkrdiagnoses

v1.1.0

Complete review of the received version (ZIP « 1.0.8 », code 1.0.9 ).

Arranged

  • The loose text "Script completed." was printed at the bottom of each page with the bar (back-office and store).
  • The store bar never worked: its data was being escaped by Smarty and remained at zero, and its AJAX actions did not respond (in the PrestaShop front it only calls displayAjax…() ).
  • With catching enabled, an uncaught exception would leave the page blank with HTTP 200 and no trace in the log: now PHP treats it as usual (500 and "Uncaught ...").
  • Hook overrides and database overrides are no longer deleted or overwritten when PrestaShop has merged them with another module's override: they appear as "merged with another module's override" and are not touched.
  • "Disable all overrides" (Advanced Parameters > Performance) removes class overrides in 1.7.8 and 8.x: now they are detected and warned about, instead of assuming the overrides are installed.
  • Nested hook times counted twice; the time "per module" was the hook split equally: now it is truly measured within each module (new table rkr_diag_module ).
  • Copying settings when duplicating a store (multistore) did nothing ( old_id_shop / new_id_shop ).
  • Import messages with « [1] » not replaced.
  • The version of config.xml ( 1.0.4 ) did not match the module version. Security
  • XSS: Custom CSS was printed unfiltered within a on all back-office pages; now any "<" is removed when saving, importing, and painting.
  • The history stored the literal SQL (emails, password hashes, API keys saved in the configuration) and the URLs with the back-office token: the values are hidden by default (new setting "Hide query values in history") and the tokens always.
  • The module page and its history are only visible to employees allowed in the settings (super administrators by default); with "every employee with permission on this tab", only the profiles that can see the tab, and the bar no longer appears to the rest of the back-office.
  • Signed cookies linked to your name, your data and the employee's password: changing the password, deactivating or deleting the employee cancels them; the one on the front panel no longer serves as a resolution mode cookie.
  • True browser troubleshooting mode: the module list travels in the signed cookie (previously it was global and one administrator could shut down another's session).
  • The store bar is sent with Cache-Control: private, no-store , so that a page cache does not serve it to visitors with the SQL and the link to the back-office.
  • The AJAX channel's "ping" requests a token. Performance
  • Capture only runs for allowed employees (previously, on all back-office requests, including login) and never on Symfony debug bar requests or those from the module itself.
  • Checked query limit before debug_backtrace() and SQL trimmed to 4 KB per query.
  • Queries are no longer saved twice per request; information_schema is replaced by SHOW TABLES once per request; batch purging is replaced with four DELETE operations per capture. Other
  • AFL-3.0 license; new logo; the menu trait is called RkrDiagMenuTrait (a dozen Rekire modules bring a different RkrBackOfficeMenuTrait and PHP keeps the first one it loads).
  • Translations: Spanish, French, Italian, German and Portuguese.

4 other products in the same category

Questions and answers

Nobody has asked anything about this product yet.

Cookie consent
Back to top