Instant Reindexing for Search Engines & AI Assistants (Site) for Site app

A fast site brings leads - a slow one hands them to a competitor

Visitors 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 site keeps nobody waiting anywhere: not the home page, not a service page, not the inquiry form. According to Contentsquare (Digital Experience Benchmark 2025, 90 billion visits), 40% of visits come with visitor frustration, and slow loading is one of the main reasons people leave after the very first page. And fast sites are rare: according to HTTPArchive data for 2025, only 42% of websites pass the Core Web Vitals speed thresholds - joining that minority means beating most competitors on speed alone. A fast site gets read, gets trusted, and gets the inquiry.

Ads and mailings send people to the same handful of pages - and that is exactly when a site usually slows down. The plugin builds the page once and serves the ready copy to every next visitor: people see your content immediately instead of staring at a blank screen.

Bots already visit websites 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 read websites to answer their users and crawl pages many times more often than a classic search crawler: a person opens five tabs, an agent hits thousands of pages in seconds.

For a website 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 page is the one an assistant cites and the one that appears in AI search overviews. Second: the bot flood is real load that slows a regular site down for human visitors. The cache solves both at once: bots get prebuilt pages instantly, and your server barely notices their visits.

Website pages - served ready, straight from the cache

• The home page and inner pages of the Site app - built once, then served ready-made: about, services, contacts, landing pages.
• The cache clears itself - save a page, change the site structure, domains, or routes: outdated copies are rebuilt right away.
• Every domain is separate. Several websites on different domains 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 visitor's repeat visit opens even faster from the browser cache.
• APCu turbo mode - ready pages are read from ultra-fast server memory; enabled with a single switch if your hosting supports it. A direct same-server measurement (KakTak.Net, July 2026, median of 20,000 reads): a 64 KB page is read from APCu in 3 microseconds - 33 times faster than Redis (102 µs) and 13 times faster than Memcached (40 µs).
• 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 - and forget it

The plugin does all the work by itself, quietly, in the background. You just keep running your website: editing pages, launching ads, adding sections - 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: saving a page or changing the site structure flushes 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 mailing campaigns.

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

One domain free - all site domains 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 site correctly, the KakTak.Net line has companion plugins - we recommend using them together: you get a complete circuit that prepares your site for search and AI.

Schema.org markupPage content made clear to search and AI → llms.txtA site map for AI assistants →

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

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

• A ready page exists in the cache - the visitor gets it instantly, with no rebuild and no extra database queries.
• No ready page yet - the page is built by the site itself as usual: your theme, your blocks, your plugins. The finished result is remembered for the next visitors.
• Nothing is replaced - the plugin does not rewrite the site or copy its 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 site keeps working the way it always did, survives Webasyst updates calmly, and the plugin leaves no traces if removed.

Numbers from a live website, not promises

Source of the numbers - measurements by the developer, KakTak.Net, July 2026, on a working Webasyst site (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 domain is isolated - each website has its own cache, another site's page is never served.
• Personal requests always bypass the cache - sessions, sign-ins, and form submissions are handled by the site 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 site 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 site.