OpenCart 3.x

Your storefront answers before OpenCart wakes up.

Nitro serves cached pages straight from disk, ahead of the framework. On a hit your store runs no queries, loads no modules and renders no templates — because it never gets that far.

7-day trial No account 49€ once per store domain

Launch price 49€ once, for one store domain. Lifetime, no renewals.

A nitrous canister — the Nitro mark NOS
Trial length: 7 days TRIAL 7 days

The trial starts when you install it. No account, no card.

The boost run

Cache miss

OpenCart boots

Cache hit

0 queries

served before OpenCart boots

Hover or focus a phase above to see what it does.

Widths show work performed, not measured time. Your numbers depend on your host, your theme and your catalogue.

  • Fast File Cache
  • stale-while-revalidate
  • soft-bust epoch
  • ETag and Last-Modified
  • Dynamic Fragments
  • Entity purge and re-warm
  • Fast-resize prepass
  • WebP generation
  • Speculation Rules
  • Reverse-DNS verification
  • Cookie-less session guard
  • Canonical Domain Redirect
  • slow-query log

Queries on a cache hit

0

Served before the framework boots.

Trial

7 days

Starts when you install it. No account needed.

Licence

49€

Launch price. Once, per store domain. No renewals.

Ioncube

Not required

Plain PHP. Works on ordinary shared hosting.

Stores running Nitro

Live OpenCart storefronts with Nitro installed. Open one.

Why it matters

A slow store is a smaller store.

Every OpenCart page view boots the framework, resolves your modules, runs the queries behind them and renders the theme — then does the whole thing again for the next visitor. Most of that work produces exactly the same HTML it produced a second ago.

Nitro does that work once and then stops repeating it.

How it differs

The parts other caches leave out.

It serves before the framework boots
A hit is answered from catalog/index.php. Nothing downstream runs — that is where the saving comes from.
Edits purge only what changed
Editing a product clears that product's pages and queues them for the next warm run, rather than emptying the whole cache.
Every failure falls through to stock OpenCart
If any part of Nitro errors, the request continues as though it were not installed. A cache is not worth an outage.
Logged-in customers can read the cache too
Off by default, and it is a deliberate opt-in: it needs Fill Personal Areas on the Server turned on, Dynamic Fragments configured, and Skip Cache for Active Visitors turned off. With those set, signed-in visitors read the shared guest cache and their cart and account details are filled in server-side, before the response is sent — no client-side swap. A personalised render is never stored.

Compatibility

What it needs

  • OpenCart 3.x
  • Whatever PHP your store already runs — running the highest version your host offers is recommended
  • Ordinary shared hosting is fine — no Ioncube, no extensions to install
  • A cron entry, if you want the cache warmed automatically

Installing

Three steps

  1. 1 Upload the ocmod archive through Extension Installer.
  2. 2 Refresh Modifications.
  3. 3 Install Nitro from the module list — that's what starts your 7-day trial.

Try it on your own store.

7 days, no account, no card. If it does not help, uninstall it.

Download Nitro