Built into WordPress hosting on G7Cloud

G7Cloud Cache: full-page caching that knows what you edited

G7Cloud Cache keeps a full copy of every cacheable page in front of your WordPress site, so a cached page is served in milliseconds without starting PHP or touching your database. When you edit something, only the pages that actually display it are refreshed. Nothing goes stale, and the cache never rebuilds from cold.

Cached pages served in milliseconds, before PHP even starts
Edit a menu and only the pages showing that menu refresh
Carts, checkouts and logged-in visitors are never cached
No caching plugin to install, no settings to maintain
Precise refresh in action
Automatic
New post published"Spring collection"
Homepage
Lists the new post
Refreshed
Category: news
The post appears here
Refreshed
RSS feed
Includes the post
Refreshed
About
Does not display it
Still cached
Services
Does not display it
Still cached
+ 35 more pages
Still cached
3 of 40 pages refreshed · nothing served cold

Served before WordPress even starts

On a normal request, WordPress builds the page from scratch: PHP boots, the database is queried, the theme renders. G7Cloud Cache serves a full copy of the finished page from in front of your site instead, so most visits never reach WordPress at all.

That does two things. Visitors get the page in milliseconds. And your site's own resources stay free for the visits that genuinely need them: checkout, admin and search. Static files and images are cached in front of your site too. It is all part of managed WordPress hosting on G7Cloud.

A cached page costs your site nothing to serve: PHP never starts and the database is never queried.
Without full-page caching
RequestPHP bootsDB queriedPage built

Every visitor pays the full cost of building the page, even when it has not changed in weeks.

With G7Cloud Cache
RequestServed in millisecondsPHPDB

The finished copy is served from in front of your site. WordPress is not involved at all.

The precise-refresh mechanism

Only the pages that display your edit are refreshed

G7Cloud Cache keeps a map of what every cached page displays. That map is what makes precise refresh possible, and it is what a file-based caching plugin cannot do.

01

Every page is mapped

As a page is cached, G7Cloud Cache records what it displays: which posts, categories, menus, sidebars and widgets it rendered.

02

You edit something

Publish a post, rename a category, change a menu. You edit WordPress exactly as you always have; there is nothing extra to press.

03

The affected pages are found

G7Cloud Cache checks its map for every cached page that actually displays the thing you changed.

04

Only those pages refresh

Instantly and automatically. Every other page stays cached and warm, ready to serve in milliseconds.

What caching plugins get wrong

A typical caching plugin has two ways of handling an edit, and both cost you.

Wipe the whole cache on every edit

Fix a typo and every page on the site is purged. Every visitor hits an uncached page until the cache slowly rebuilds, which is exactly when your site is at its slowest.

Serve stale pages until a timer expires

The cache holds a page for a set time whether you edited it or not. Change a price and visitors can keep seeing the old one until the timer runs out.

G7Cloud Cache does neither

Because it knows what every page displays, it refreshes only the pages your edit actually changed. Nothing goes stale, and the cache never has to rebuild from cold. There is no timer to tune, no exclusion list to keep correct, and no purge button to press.

Safe for WooCommerce, by design

The fastest way to lose a shopper's trust is to show them someone else's basket. G7Cloud Cache is built so that cannot happen: logged-in visitors, carts, checkouts, wp-admin, previews and comment posts are never cached.

There are no exclusion rules for you to write and keep correct as your store changes. Dynamic paths are recognised and passed straight through to WordPress, every time. On WooCommerce hosting that means the product pages your shoppers browse are served in milliseconds while the checkout stays live and personal.

Browsing is served from the cache, so your store's PHP and database stay free for the orders coming in.
Never cached, ever
  • Carts and checkouts

    Always live, always the right basket for the right shopper.

  • Logged-in visitors

    Every response is built fresh for that person.

  • wp-admin and previews

    You always see the current state of your site.

  • Comment posts

    Submissions go straight to WordPress.

You cannot serve one customer another customer's basket. The cache holds public pages only.

Pairs with the object cache for the dynamic pages

G7Cloud Cache removes the cacheable pages from your site's workload entirely. The pages it deliberately leaves alone (carts, checkouts, logged-in sessions) still need WordPress to run, and that is the job of the managed Redis object cache add-on.

The two do different jobs, so they stack: G7Cloud Cache takes the repeatable traffic off WordPress, and the object cache speeds up the dynamic visits that remain. Both are covered on the WordPress performance page.

  • G7Cloud Cache: cacheable pages served without WordPress
  • Redis object cache add-on: faster carts, checkouts and admin

The speed half of ScaleShield

G7Cloud Cache is part of ScaleShield, the security and speed layer in front of your site. The same layer that serves your cached pages also filters what reaches WordPress:

  • Bot protection turns away scrapers and password-guessing scripts before they touch your site.
  • The managed firewall rejects requests matching known attack patterns before your code runs.
  • Free automatic TLS certificates on every site, wildcards included, renewed for you.

G7Cloud Cache FAQ

What the full-page cache in front of your WordPress site does, and what it deliberately leaves alone.

Do I still need a caching plugin?

No. G7Cloud Cache does the full-page caching in front of your site, so there is no plugin to choose, no settings page of timers and exclusion rules, and no purge button. If you move a site across with a caching plugin installed, you no longer need it.

What happens when I publish a post or edit a page?

Only the pages that display the change are refreshed, instantly and automatically. Publish a post and the homepage, its category page and the feeds that list it refresh; everything else stays cached and warm. Edit a menu and only the pages showing that menu are refreshed.

Is G7Cloud Cache safe for WooCommerce?

Yes. Carts, checkouts and logged-in sessions are never cached, so every shopper sees their own basket and their own account, always. Product and category pages are served from the cache; the checkout is passed straight to WordPress every time.

Will logged-in visitors ever see a cached page?

No. Logged-in visitors, wp-admin, previews and comment posts are never cached. When you are logged in you always see the live site, so you can check an edit the moment you make it.

How fast is a cached page?

A cached page is served in milliseconds from in front of your site. PHP never starts and the database is never queried, so serving it costs your site nothing and your resources stay free for checkout, admin and search.

Does G7Cloud Cache cost extra?

No. It is built into WordPress hosting on G7Cloud as part of ScaleShield, the security and speed layer in front of every site. There is no caching add-on to buy and nothing extra on the bill.

How does G7Cloud Cache work with the Redis object cache add-on?

They do different jobs. G7Cloud Cache removes the cacheable pages from your workload entirely, and the managed Redis object cache add-on speeds up the dynamic pages that cannot be cached, such as carts and logged-in sessions. Together they cover both halves of your traffic.

Retire the caching plugin

G7Cloud Cache is on from the moment your WordPress site goes live on G7Cloud. Nothing to install, nothing to tune, nothing to purge. And if you are coming from another host, we migrate your site for you.