JavaScript is off. The country switcher and the demos need it; everything else on this page works.

Plugins · Performance & caching

Smush with AI, on every WordPress site you look after

Caching and optimisation plugins make a site fast until an update or a host change quietly turns a setting off, and nobody measures it again. WebCrew monitors the site 24/7, matches Smush's installed version against the vulnerability databases, and updates it with a restore point when you say go.

Start free Two ways to connect

Free for one site. Connect it in five minutes. No card.

Smush belongs to its publisher; WebCrew is not affiliated with it.

Smush1M+ active installs · version 4.3.2

Monitoring 24/7uptime from two regions, health scoreIncluded

Vulnerability checkSmush's version matched against the databasesIncluded

UpdatesOn your schedule; restore point first, code difference kept, rolled back when a check failsIncluded

Assistant actions in Smushchanges made for you, logged, one click to undoComing soon

Compress and optimize images, enable lazy load, serve WebP & AVIF, and speed up your site with a global…

What goes wrong

Three things that go wrong on sites running Smush, and what you see instead

Each card is one conversation: what happened, what WebCrew did, and the moment you stepped in.

The site got slow and the cache had been off for a month.

The version check reads Smush's settings: caching disabled since the host migration.
Listed as a finding, not a mystery.
You switch it back on. Page speed per page is coming soon.

Settings are read continuously; a plugin that stopped is a finding.

An optimisation update broke a page.

Smush update approved, restore point first.
Difference kept; the site is requested again after the update.
The home page renders blank. Restore: one click back.

One click back, every time.

PHP end of life is in two months and the host has not said anything.

6 sites flagged: PHP 8.1 reaches end of life in 60 days.
Each site shows the versions its host offers.
You schedule the upgrades. No surprise in two months.

End-of-life warnings months ahead, per site.

Included on every site

What WebCrew does for a site running Smush

Every change WebCrew makes takes a restore point first and can be undone in one click; you choose where it should ask you first. Monitoring reads; every change is logged and waits for a person.

Everything in site management

Uptime 24/7 from two regions

A site that stops answering, or answers with something else, reaches you within minutes with the response it gave.

Security scan and vulnerability match

Core-file integrity, unknown administrators, and Smush's installed version matched against the public vulnerability databases.

Updates with a restore point

On your schedule; restore point first, code difference kept, rolled back when a check fails.

Ask for changes in plain words

The assistant makes the change in Smush, shows you what it did, and keeps a restore point so one click undoes it Coming soon. Your own AI tools connect today over MCP.

Connecting

How to connect a site that runs Smush, and what we recommend

Where the host allows SSH keys, we recommend SSH: every file compared, not only what WordPress reports, and cleanup help when a site is compromised. Where it does not, the connector plugin covers monitoring, updates and Smush's version check in five minutes.

Connector plugin

Upload in wp-admin. No server access needed.

24/7 uptime, health score, versions, administrators
Vulnerability matching and updates with a restore point
One-click login, DNS and mail settings

Five minutes. Remove the plugin and the site is disconnected.

Recommended

SSH

One key, scoped to the site's user on the server.

Everything the connector does
File-level integrity checks and faster updates with a full restore point
Malware cleanup and staging copies, when a site needs them

Ten minutes. The key is revoked from your dashboard at any time.

How connecting works, step by step

Questions

Before you connect a Smush site

Does WebCrew add anything that slows the site?

No. Monitoring is requests from outside; the connector adds no front-end assets and does not touch Smush's cache.

Does it clear Smush's cache after an update?

Not today. It records the update and the difference; clearing the cache remains a step in Smush. The assistant is planned to draft that as an action.

Will it measure page speed?

Page speed per page is coming soon. Uptime and response time from two regions are included today.

Does it work with a CDN in front of the site?

Yes. Uptime checks reach the site the way visitors do; the connector works from inside.

Do I have to install anything besides Smush?

One of two things: the WebCrew connector plugin, uploaded in wp-admin like any plugin, or one SSH key for the site's own user. Nothing else changes on the site.

Can I use my own Claude or ChatGPT with a site that runs Smush?

Yes. Connect your tool to WebCrew over MCP and ask about the site from your own chat. Reading is instant; changes are made for you, logged, and undone in one click.

What does it cost for a site running Smush?

The first site is free, for as long as you like. Every site after that is billed per site per day, monthly, for the days it was on. Plugins are never counted.

Is my content or Smush's data used to train anything?

No. Your content is never sold and never used to train a model, by WebCrew or by a provider it uses.

What if Smush is a premium plugin with a licence?

It updates through its own licence. WebCrew shows the pending version, takes the restore point first and keeps the code difference, the same as for any other plugin.

Plugins that often run next to performance & caching

All plugins in the catalogue

Connect the Smush site now. The first check is done within the hour.

Start free How to connect

Free for one site. No card.