Catalog speed & cache (TurboCache) for Shop-Script

A fast store sells - a slow one hands the order to a competitor

Shoppers decide in seconds - and they come on whatever connection they have: fast Wi-Fi, slow mobile data out of town, special network setups. A fast store keeps nobody waiting anywhere: not the catalog, not the product page, not the cart. Speed is money, directly: according to Shopify platform data for 2026, every extra 0.1 seconds of load time costs a store about 3.5% of its conversions, and stores that open in under 2 seconds convert almost twice as well as average. And fast stores are rare: according to HTTPArchive data for 2025, only 39% of e-commerce sites pass the Core Web Vitals speed thresholds - joining that minority means beating most competitors on speed alone.

The slowest pages of a store are usually the most important ones: the catalog with filters, categories with hundreds of products, product pages with photos and reviews. The plugin builds such a page once and serves the ready copy to every next visitor - the shopper sees your storefront immediately instead of staring at a blank screen.

Bots already visit stores more often than people - a fast site answers them, a slow one loses

The internet has changed: according to the Imperva Bad Bot Report 2025, automated traffic has overtaken humans for the first time - bots now generate 51% of all web requests. AI agents compare products on behalf of shoppers and crawl catalogs many times more often than a classic search crawler: a person opens five tabs, an agent hits thousands of pages in seconds.

For a store this means two things. First: fast pages make it into AI answers, slow ones almost never do. Good speed and Core Web Vitals raise the odds that your product is the one an assistant cites and the one that appears in AI search overviews. According to Adobe data for 2025, AI-driven traffic to online stores grew 393% in a year and converts about 42% better than regular traffic - losing it to slow pages is the most expensive loss of all. Second: the bot flood is real load that slows a regular store down for human shoppers. The cache solves both at once: bots get prebuilt pages instantly, and your server barely notices their visits.

Heavy catalog pages - served ready, straight from the cache

• Storefront home, categories, product pages, tags, and store pages - built once, then served ready-made.
• The cache clears itself - save a product or a category, update prices via import: outdated pages are rebuilt right away. Prices and stock never get stuck in the cache.
• Every storefront is separate. Multiple domains and storefronts never mix, each gets its own cache; mobile and desktop versions of a page are stored separately.
• Compression and browser caching - pages are served compressed, and a shopper's repeat visit opens even faster from the browser cache.
• Server setup assistant - the plugin detects your web server and drafts a ready-to-send letter for your hosting support if you want to squeeze out even more speed.

Install it, set it up - and forget it

The plugin does all the work by itself, quietly, in the background. You just keep running your store: adding products, changing prices, launching ads - pages are always served fast, and you never have to think about caching again.

• Works right after installation: pages are stored in the standard Webasyst cache storage; no theme or server tuning needed.
• Keeps pages fresh on its own: catalog events flush the cache instantly, and page lifetime is a single setting.
• A "Purge cache" button - for when you want to refresh everything manually, in one click.
• Built-in diagnostics: a response header shows whether a page came from the cache or was rebuilt - easy to verify yourself.
• A nice bonus: an unloaded server calmly survives bot floods, ad traffic spikes, and seasonal sales.

A fast store helps everyone at once: the shopper never waits on any connection, search engines and AI assistants get pages instantly, and you get more orders from the same traffic.

One domain in base - all storefronts and turbo mode in premium

Speed brings them in - markup and the map win them over

TurboCache makes sure pages are served instantly. And so that search engines and AI assistants also understand your store correctly, the KakTak.Net line has companion plugins - we recommend using them together: you get a complete circuit that prepares your store for search and AI.

Schema.org markupPrices and stock made clear to search and AI → llms.txtA store map for AI assistants →

Plus a free check-up. The Cache Audit plugin from the same line is completely free: install it and test your store across every caching and speed parameter - before buying and after installing. Cache Audit in the Webasyst store.

By Webasyst's rules: nothing is changed, nothing breaks

Webasyst and Shop-Script are thoughtfully designed: the platform itself is built for plugins to extend it neatly. TurboCache works exactly that way - it fits into the store's native mechanics, and pages simply stop being rebuilt on every visit.

• A ready page exists in the cache - the shopper gets it instantly, with no rebuild and no extra database queries.
• No ready page yet - the storefront is built by the store itself as usual: your theme, your plugins. The finished result is remembered for the next visitors.
• Nothing is replaced - the plugin does not rewrite the storefront or copy any store pages, and your theme needs no editing.
• Storage lives in the standard Webasyst cache backend (files, Memcached, or APCu - whatever your hosting provides). If no storage is configured yet, the settings assistant sets it up for you - in one click.
• Everything stays neat and standard - the store keeps working the way it always did, survives Webasyst and Shop-Script updates calmly, and the plugin leaves no traces if removed.

Numbers from a live store, not promises

Source of the numbers - measurements by the developer, KakTak.Net, July 2026, on a working Webasyst store (Shop-Script, PHP 8.5): native page rendering versus a ready page from the cache, on a warm engine. The method is reproducible - database queries counted via the DBMS query log, response time as the median of 25 runs.

• Every storefront is isolated - verified across six domains: each one has its own cache, another storefront's page is never served.
• Personal requests always bypass the cache - sessions, carts, sign-ins, and form submissions are handled by the store directly.
• Ad tags do not multiply copies - visits with ?utm get the same ready page, and unknown parameters are never cached at all.
• Verifiable in a minute - a service response header honestly shows whether the page came from the cache or was rebuilt. Open your storefront and see for yourself.

Final numbers depend on your hosting, theme, and plugin set - which is why the verification tool is built in, so you can measure the result on your own store.