Your site stayed up and served customers all month. One thing needs you: the SSL certificate stopped renewing itself and expires in 24 days.
Everything else is in hand. We applied five updates, caught one that broke the homepage and put it back within a minute, and closed two of the three issues raised this month. Performance slipped slightly — the cause is identified and the fix is a setting on your host, not a rebuild.
Uptime
99.94%
▲ up from 99.71%
Response time
412ms
▼ 38ms slower
Performance
68/100
▼ down 6 points
Open issues
1
▼ 2 closed
Response time, daily average
Baseline 374ms
1 Sep↑ 14 Sep — feed rebuild30 Sep
What we caught
Things that would otherwise have reached your customers
An update broke your homepage. We put it back in 47 seconds.
Larkspur Product Filters 2.4.1 was applied on 11 September at 02:14. The homepage returned HTTP 500 immediately afterwards, so the update was rolled back automatically from the pre-update snapshot and the previous version restored. Total time unreachable: 47 seconds, overnight.
Five updates applied, four of them clean.
Each was checked against outcomes across the rest of the network before being applied here, and your homepage was loaded afterwards to confirm nothing broke.
A six-minute outage that was not your site's fault.
On 8 September the site returned HTTP 502 for six minutes and recovered without intervention. A clean start and a clean end, with no slow ramp, points to the PHP process pool being recycled at the hosting layer rather than to anything installed here — so there is nothing to fix on the site.
What is safe to update
How each update behaved across every site we monitor
Plugin
Version
Across the network
Verdict
WooCommerce
9.3.3 → 9.4.1
Applied on 340 sites · 97% clean · 0 rollbacks in 30 days · no measurable load impact
Safe
Yoast SEO
23.4 → 23.6
Applied on 512 sites · 99% clean · 0 rollbacks · no measurable load impact
Safe
Smush
3.16.1 → 3.16.4
Applied on 287 sites · 98% clean · 1 rollback, unrelated to this environment
Safe
Tidecart Checkout
1.9.2 → 2.0.0
Applied on 96 sites · 94% clean · pages load around 120ms slower afterwards on average
Check first
Larkspur Product Filters
2.4.0 → 2.5.0
Attempted on 180 sites · 12% rolled back · 88% of failures on PHP 8.2, which this site runs · median 1 day to rollback
Hold
Known conflict on this site. Larkspur Product Filters and Tidecart Checkout have produced 23 recorded conflicts across the network when both are active on PHP 8.2, most commonly a fatal error at checkout. Nothing has gone wrong here yet. If you update either, update it alone so the cause stays identifiable.
Plugins
23 installed · 21 active · 4 updates available
Plugin
Installed
Latest
State
Network reliability
WooCommerce
9.3.3
9.4.1
Update
97%
Elementor
3.23.4
3.24.0
Update
96%
Larkspur Product Filters
2.4.0
2.5.0
Hold
88%
Tidecart Checkout
1.9.2
2.0.0
Update
94%
Yoast SEO
23.4
23.4
Current
99%
WP Rocket
3.17.2
3.17.2
Current
98%
Wordfence Security
7.11.6
7.11.6
Current
98%
UpdraftPlus
1.24.7
1.24.7
Current
97%
Smush
3.16.1
3.16.1
Current
98%
Contact Form 7
5.9.8
5.9.8
Current
99%
Really Simple SSL
8.1.1
8.1.1
Current
97%
Redirection
5.5.2
5.5.2
Current
99%
WPForms Lite
1.9.1
1.9.1
Current
98%
Classic Editor
1.6.4
1.6.4
Inactive
—
Duplicate Post
4.5
4.5
Inactive
—
Showing 15 of 23. Network reliability is the share of update attempts across all monitored sites that completed without a rollback.
No other availability events this period. Previous outage: 22 July.
Performance
Google Lighthouse, mobile, measured every 6 hours
Performance
68
▼ from 74
Accessibility
94
no change
Best practices
92
▲ from 88
SEO
100
no change
Core Web Vitals
Largest paint (LCP)3.10s
Interaction (INP)12ms
Layout shift (CLS)0.04
Google threshold, LCP2.50s
Verdict1 of 3 failing
Server & database
Page generation2.40s
Database query time180ms
Queries per page94
PHP memory limit256M
Peak memory used118M
Caching
Page cachingOn (WP Rocket)
Object cachingOff
Redis availableYes
Browser cacheOn
CDNCloudflare
Biggest single win available
Object caching is off while Redis is already available on this host. Enabling it should remove most of the 180ms database time from every uncached request, and is the main reason the Saturday feed rebuild was able to slow the whole site down. Estimated recovery: 1.5–1.8s on the largest paint, and most of the six performance points lost this month.
Security
Full posture, checked daily
Certificate
StatusExpires in 24 days
Expires24 Oct 2026
IssuerLet's Encrypt
ChainValid
ProtocolTLS 1.3
Auto-renewalNot working
Response headers
Strict-Transport-SecurityPresent
X-Frame-OptionsPresent
X-Content-Type-OptionsPresent
Referrer-PolicyPresent
Content-Security-PolicyMissing
Permissions-PolicyMissing
DNS & email
SPF recordPresent
DMARC recordMissing
MX recordsPresent
Nameservers2
FirewallCloudflare
DNSSECNot enabled
WordPress hardening
File editing disabledYes
Debug loggingOff
PHP version exposedNo
Default "admin" userAbsent
Database prefixNon-default
XML-RPCEnabled
Scheduled tasks
Total jobs31
Overdue0
WP-CronEnabled
Real cron replacementYes
Last run12 min ago
Integrity scan
Core files modifiedNone
Suspicious admin accountsNone
Unexpected content changesNone
Homepage fingerprintUnchanged
Last scan30 Sep, 03:00
Issues
1 open · 2 closed this period
OpenDetected 26 Sep 09:02 · security · warning
The SSL certificate has stopped renewing itself
Your certificate expires on 24 October. From that date visitors will see a full-page browser warning, and most will leave rather than click through it.
Analysis and fix
Let's Encrypt certificates renew automatically with 30 days remaining. This one did not, which almost always means the renewal challenge is blocked before it reaches the site — usually a caching or redirect rule in front of it.
Confirm /.well-known/acme-challenge/ returns 404, not a redirect or cached page.
Add a cache bypass rule for that path in Cloudflare.
Trigger a manual renewal. We will confirm within the hour.
Pages took 3.2 seconds instead of the usual 0.4 between 09:10 and 09:50 — the busiest hour of the week.
Analysis and fix
The product feed rebuilds every Saturday at 09:00 and regenerates every variation in a single pass. Object caching is off, so each rebuild reads the full product table from the database rather than from memory. Traffic was normal for the hour — the slowdown was self-inflicted.
Fix: enable object caching (Redis is available on this host at no cost), then move the rebuild to 03:00 so it cannot collide with a traffic peak. Together these should remove roughly 1.8s from the page.
Two consecutive checks failed with a 502 from nginx, then recovered without intervention.
Analysis and fix
A clean start and a clean end with no slow ramp is the signature of a PHP process pool restart at the hosting layer, not of a fault in anything installed here. No action needed on the site. If it recurs more than once a month, ask the host whether the pool is being recycled under memory pressure.
Changes
Every change made through TalkToWP this period
Date
Change
Requested by
Verified after
Outcome
22 Sep 02:10
Theme updated — Blocksy 2.0.43 → 2.0.44
Schedule
HTTP 200
Applied
18 Sep 02:10
Yoast SEO 23.3 → 23.4
Schedule
HTTP 200
Applied
11 Sep 02:14
Larkspur Product Filters 2.4.0 → 2.4.1
Homepage returned HTTP 500 · snapshot restored after 47s
Schedule
HTTP 500
Reverted
3 Sep 02:12
Cache cleared
Automatic
HTTP 200
Applied
3 Sep 02:10
4 plugins updated in one batch
Contact Form 7, Smush, Redirection, WPForms Lite
Schedule
HTTP 200
Applied
Activity log
Everything recorded against this site
30 Sep 03:00
Integrity scan completed — no changes to core files
scan
28 Sep 03:00
Weekly health scan — 23 plugins checked
scan
26 Sep 09:02
Certificate check flagged 24 days remaining
security
22 Sep 02:10
Theme updated to Blocksy 2.0.44
change
18 Sep 02:10
Yoast SEO updated to 23.4
change
14 Sep 09:50
Performance issue auto-resolved — response time back to baseline
incident
14 Sep 09:10
Slow response time detected — 3.2s
incident
11 Sep 02:15
Update reverted — Larkspur Product Filters restored to 2.4.0
change
8 Sep 04:18
Site recovered — HTTP 200 after 6 minutes
incident
8 Sep 04:12
Site offline — HTTP 502
incident
3 Sep 02:12
4 plugins updated and cache cleared
change
1 Sep 00:00
Reporting period opened
system
Vulnerabilities
Every plugin and version checked daily against the public advisory database
Current status
No open vulnerabilities across all 23 plugins, the theme, or WordPress core
Last checked 30 September, 03:00. One advisory affecting this site was closed during the period, below.
Advisories affecting this site
Advisory
Component
Severity
Affected
Status
TTW-2026-0914
Larkspur Product Filters
< 2.4.0
Medium · 6.1
Stored cross-site scripting via the filter label field, exploitable by a contributor-level account
Patched 3 Sep
Closed by the batch update applied on 3 September, 23 days before the advisory was published. Your site was never running an affected version in the window where it was known.
Recent advisories in plugins we track — none present on this site
Published
Advisory
Component
Severity
On this site
28 Sep
TTW-2026-0928
Mapwright Store Locator < 4.2.1
Critical · 9.8
Not installed
21 Sep
TTW-2026-0921
Bellhop Booking Forms < 1.8.3
High · 8.1
Not installed
17 Sep
TTW-2026-0917
Tidecart Checkout < 1.9.0
Medium · 5.4
Running 1.9.2
9 Sep
TTW-2026-0909
Quillbase Analytics < 3.0.7
Medium · 6.5
Not installed
Shown because these plugins are common on sites like yours. If you install any of them later, we will check the version against this list on the next scan.
TalkToWP
Report generated 1 October 2026 · period 1–30 September 2026
Your site is checked every three minutes, around the clock. Network comparisons are drawn from anonymised update outcomes across every site we monitor — no site names, domains or customer data form any part of that.
TalkToWP