A single page going from roughly 92 → 96 PageSpeed in a few minutes is a good day. In the latest Web Tech with Brett video, that lift came from cleaning image weight with Aura Optimise on an image-heavy Aura Builder page — about 842 KB saved in one pass, with WebP, resize-to-container, and library compare in the admin.
That win is real. It is also not the whole maintenance story for an agency book of work.
Watch: I Made My Site Faster in 5 Minutes (92 → 96 PageSpeed)
PageSpeed is site work. Fleets need ops work.
Optimising images on one URL is a site-level job. You open the media library, resize and compress, re-test Lighthouse, and move on. CMS Inspect is not that product. It is the fleet layer for WordPress and Joomla: updates, backups, reports, and visibility across many sites — so a speed fix on one client does not hide pending core updates, missed backups, or silent failures on twenty others.
Use Optimise (or any image tool) when the bottleneck is media weight. Use Inspect when the bottleneck is “which sites need attention this week, and can I prove what we did?”
Why agencies still need fleet visibility after a speed win
- Updates do not wait for Lighthouse — security releases land on their own calendar. A faster homepage still needs a tracked update path.
- Backups belong outside the site — before risky batches, copy database and files somewhere recoverable (Drive or Dropbox style workflows), not only “I hope the host snapshot is fine.”
- Clients ask for proof — branded reports beat Slack paraphrases when someone asks what changed last month.
- Mixed stacks are normal — many books still run WordPress and Joomla side by side. One ops habit beats two disconnected dashboards.
What CMS Inspect is for
CMS Inspect is built for that loop: fleet updates, backups, and reports for WordPress and Joomla in one place. Free core gets you started; advanced operations unlock at $1 per active site per month.
It does not replace image optimisation on a page. It sits beside that work so performance wins stay paired with maintenance you can see and document.
Soft next step
If you watched the PageSpeed run and thought “great for one site — what about the rest of the fleet?”, start at cmsinspect.com. Keep the image work on the site that needs it; bring updates, backups, and reporting into one ops dashboard when the client list outgrows browser tabs.
