Questions

The answers, before you have to ask.

Installing, compatibility, the 7-day trial and the licence, how the cache actually behaves, and what to do when a page looks wrong. If yours isn't here, ask us — the reply usually ends up on this page.

Speed and diagnosis

Why are add to cart, login and checkout still slow?

Those pages are never cached, deliberately. Checkout, cart, account, login, register, logout, the API and payment routes are excluded outright — serving a shared copy of any of them would show one customer another's session. Beyond that, a guest who has put something in the basket, started a wishlist or comparison, or switched currency or language gets fully live pages from then on so the header is always right, and logged-in customers get live pages unless you deliberately enable caching for them. Those live pages are still faster than stock OpenCart, because the query cache, the optimized template engine and the asset work all still apply — they just do not skip the render.

How do I find out why a particular page is slow?

Turn on the Page Speed Panel and open the link it gives you. Every storefront page then carries a small badge saying whether it was a HIT, STALE or MISS, how long it took, how big it was, its cache key and which device bucket it landed in — with a button to purge that page and reload. A page that is always a MISS is being excluded or bypassed, and the dashboard's bypass counters say by which rule. If it is a HIT and still slow, the time is going somewhere in front of Nitro. Start Bypass shows you the same page with Nitro off entirely for comparison, and Track Slow Queries logs storefront queries over your threshold while you investigate. The panel link contains a secret — treat it like a password.

The dashboard shows a low cached-page hit ratio.

The dashboard breaks bypasses down by reason, which is where to look. Dynamic means visitors arriving with a cart, wishlist, comparison or login. Untrusted means requests on a hostname that is not in your OpenCart store table — the cacheable-host list is derived from that table and never hand-edited, so a storefront domain missing from System → Settings shows up here. Pattern means a URL matching an exclude rule. Cookie means one of your No-cache Cookies was present, and a high count there usually means a consent or A/B cookie was listed that every visitor actually has, which disables the cache for everyone.