Why Weekly Maintenance Matters
Nothing about a Bricks site breaks overnight. It degrades — and that’s the trap. Skip maintenance for three months and you have seventeen pending updates, a database full of transients and post revisions, a cache serving yesterday’s CSS to visitors, and a PageSpeed score that slid from 95 to the low 60s while you weren’t looking. Nothing exploded, so nothing felt urgent — and now the “quick check” is a weekend project.
The fix isn’t a bigger maintenance day. It’s a smaller one, on a schedule. Ten minutes, once a week, same day every week. That’s enough to catch every problem while it’s still a five-minute fix, because the things that actually hurt Bricks sites — stale caches, bloated databases, outdated plugins — grow slowly and predictably. Catch them weekly and they never get a chance to compound.
What You Need
This is a one-time setup. Spend an hour once, then the weekly pass is just the checklist below.
- A backup plugin — UpdraftPlus on the free tier is plenty. Configure it to store backups off-server (Google Drive, Dropbox or S3), never on the same disk as your site
- A staging environment — your host’s staging feature or a subdomain copy. You’ll use it for the monthly restore test
- PageSpeed Insights bookmarked, with the mobile URL of your home page saved
- WP-Optimize installed for database cleanup (by the UpdraftPlus team — free tier is fine)
- Query Monitor — read-only on the front end, and it shows your autoloaded data size in its Database panel
- A weekly reminder — calendar entry: “Bricks maintenance”, 10 minutes, every Monday
That’s the whole kit. No maintenance dashboard plugin, no automation stack. The tools you already have are enough; the missing piece is the habit.
Updates Check
The temptation is to update the moment a notification appears. Don’t. Bricks pushes releases every few weeks, and most are refinements you don’t need on day one.
- Open the Updates screen and list what’s pending — core, plugins, Bricks, theme
- Flag any security fix — those update immediately, no waiting period
- For everything else, wait 1-2 weeks, then read the changelog before updating
- Confirm this week’s backup exists before you update anything
- Update in order: WordPress core → plugins → Bricks → theme
- After updating, click through the home page and one inner page, and make sure the editor loads
Two minutes, done. If a changelog mentions a breaking change, skip the update that week and check the Bricks forum — someone will have posted the workaround by then.
Cache and Database
This is where the bloat actually lives. Caches and the database both accumulate silently, and both are a two-minute fix.
- Clear your page cache — WP Rocket, LiteSpeed or Perfmatters, whichever you picked in the setup checklist
- If you changed anything this week, rebuild Bricks’ own template CSS: Bricks → Tools → Rebuild
- Open WP-Optimize → Database → Clean: purge post revisions, auto-drafts, trashed posts and spam comments
- Run “Optimize database tables” to reclaim the space
- Check autoloaded data in Query Monitor’s Database panel — if it’s creeping past 1 MB, find the offending option and clean it up
A lean database also makes backups smaller and restores faster, so this step pays you twice.
PageSpeed Glance
One run of PageSpeed Insights, once a week, tells you more about the health of the site than any dashboard. Keep a log of the score — a one-line text file or a spreadsheet cell is fine.
- Run PageSpeed Insights on your home page, mobile preset — that’s the score Google actually ranks
- 90+ — you’re done. Close the tab and enjoy the rest of the week
- 80-90 — read the top issue; if it’s an image or font fix, schedule two minutes
- Below 80 — something changed this week. Check for new plugins, new images, or an update that re-enabled a setting
- Compare with last week’s score — the trend matters more than the single number
Media Housekeeping
Slowly, over months, the Media Library fills with images you used once in a draft and never again. Ten minutes a week keeps it honest.
- Scan the Media Library for obviously unused images — sort by date and eyeball the oldest ones
- Check Google Search Console → Pages → Not indexed → “Not found (404)” for the week’s 404s
- Fix dead links found in posts or menus — a redirect plugin or a quick anchor edit
- Delete stale drafts you started and never finished — each one is a future 404 or duplicate waiting to happen
- If the library is already huge, run a cleanup plugin like Media Cleaner on staging first — never straight on production
Backup Verification
A backup you’ve never restored is a hope, not a backup. Most people discover their backups are broken exactly when they need them — right after a bad update.
- Confirm this week’s backup completed and the file sizes look sane (a 2 KB “backup” is not a backup)
- Check that the latest backup contains both the database and the files
- Once a month, restore the latest backup to staging and confirm the site actually works
- Rotate old backups so you keep roughly 4-8 weekly copies, not 200
The 10-Minute Routine
Here’s the whole thing compressed. Bookmark this page, or print the list, and work through it in order:
- Minutes 1-2 — Updates. Open Updates, flag security fixes, read one changelog
- Minutes 3-4 — Cache and database. Clear the page cache, rebuild Bricks CSS, run the WP-Optimize cleanup
- Minutes 5-6 — PageSpeed glance. One mobile run, log the score
- Minutes 7-8 — Housekeeping. Media scan, 404 check, delete stale drafts
- Minutes 9-10 — Backups. Confirm this week’s backup, tick off the monthly restore test
That’s it. Ten minutes, once a week. Scores stay in the 90s, updates never pile up, and the database never becomes a problem you have to think about.
If this is your first week on a fresh site, the Bricks initial setup checklist covers the one-time configuration that makes this routine so short. And when the weekly pass surfaces something odd — an unexplained margin, a stylesheet that changed itself — the five Bricks pitfalls guide covers the classics and their fixes. See you next week.
