← Back to modules

nexya cache

Each page kept as a file and handed to the next visitor before WordPress loads — then thrown away as soon as something changes it.

  • Always up to date A page edited, a comment published, a menu changed: the copy concerned goes at once. Nobody sees yesterday’s page.
  • Never for what is personal Signed-in visitors, searches, feeds, baskets and password-protected pages are never kept.
  • Proved before it is kept The rules set on the server are proved by a real request, and taken back out on the spot if the server does not answer with them.
0:55

Pro

Page cache, the server answering without PHP when it can, browser cache time for styles, scripts and fonts, emptied in one click from the admin bar.

Get started

nexya cache in three steps

  1. Switch on nexya cache In the nexya hub, with the Pro licence (seven-day free trial).
  2. Turn on the page cache Each page is kept as a file and served before WordPress loads.
  3. Let it empty itself A page edited, a comment published: the copy concerned goes at once. One click in the admin bar empties everything.

nexya cache is in the Pro version, with a seven-day free trial.

Start 7-day free trial

FAQ

Everything about nexya cache

A page cache is the clearest gain: the page is served from a file, without starting WordPress or the database. nexya cache adds browser caching of styles, scripts and fonts.

nexya cache does the core of the job — page cache, answering without PHP when the server allows, browser cache — in the same panel as the rest of the suite. If another page cache is active, it steps aside to avoid a double cache.

No: every change empties the copy concerned at once. Signed-in visitors, searches, baskets and protected pages are never cached.

Yes: baskets, orders and anything personal are never kept.

The files and the rules set on the server are removed: the module leaves nothing behind.

The suite

Other modules

nexya translate

The site in several languages: every content with its versions, an address per language, and the site’s texts translated in one place.

nexya popup

Popups composed section by section, opening at the right moment — and able to close the shop and the forms while they are live.

nexya custom fields

Fields of your own, kept in their own tables — and read in a single query per page.

nexya aris

Audience figures, measured by the site itself — no Google, no Matomo, no IP address kept.

nexya mailya

Newsletters written on the WordPress site, with your posts in them — sent in the background, at the pace your server can hold.

nexya media

Folders to sort the media library, and thumbnail regeneration in the background, in batches, carrying on when you close the tab — and telling you when it is finished

nexya hub

The panel that gathers every nexya plugin. A module you switch on, a module you switch off — and nothing running on the WordPress site while it is off

nexya dashboard

The WordPress admin as the client sees it: menus cut down to what is useful, a tidy admin bar, and the dashboard in your own colours right through to the login page

nexya shortcuts

Duplicate, reorder, add — three gestures placed on the WordPress content lists, so you stop doing them by hand

nexya roles

WordPress capabilities filed under the plugin that creates them, readable at last. And the menu cut down to what the person in front of it actually has to do

nexya activities

Who changed what on the WordPress site, and when. Down to the ACF fields, with the value before and the value after — and the button to put it back

nexya cookie

Cookie consent, and the blocking that goes with it. Nothing runs before the visitor agrees — not the scripts, not the embedded videos, not the remote fonts

nexya seo

What the WordPress site says about itself to search engines — and what it shows when someone pastes its address somewhere. Written once, applied everywhere, checked before publishing

nexya mail

The WordPress site’s emails actually go out — and you know which ones did not, with the exact reason given by the SMTP server

nexya redirects

The 404 errors picked up as visits happen, and the 301 redirect suggested before anyone goes looking for it. With the number of hits, so you know which ones count

nexya security

The HTTP security headers set without breaking the site, the watch on vulnerabilities in the WordPress plugins installed, and the eye on what moves in the files

nexya maintenance

The operations you carry out on the WordPress site rather than in it: closing it for an intervention, slimming its database down, taking a copy