If you’re serious about delivering fast WordPress sites , or just tired of fighting performance without a clear roadmap, this is the course you’ve been waiting for. Let’s make WordPress fast. withinwp.com/courses/make-wo…

Would you help support students and help to forge the next-adventurers with #wordpress? youtu.be/fKSgZHJkE8c?si=cBuL… #wceu #wordpressbusiness #wordpressuniversity

We just moved another one of our product sites back to WordPress after ~10 years of it being statically generated with Jekyll. That’s 4 sites in 4 months back on WordPress. Not saying we’re single-handedly reversing the trend, but we’re doing what we can. 😉 It’s a 1:1 conversion for now, but we’ll start milking the fact that it’s dynamic again over the next few weeks. Why the move back? - Easier content management. The team can update knowledge base content again without going through a developer or Git workflow. Smaller edits are frictionless. Spotted a typo or outdated sentence while browsing the live site? Click edit, fix it, done. - Dogfooding. We build WordPress products, so our own product sites should probably run on WordPress too. The results of @innerwebs’s poll last week surprised me in this regard. - If a site can be static, its #WordPress version can be cached just as aggressively at the edge, but with more granular purging when individual pages change. Obligatory Lighthouse score: 100/100/100/100.

Logging into one WordPress dashboard is easy. Logging into twenty is where Site Health stops being simple. You need to know what needs attention. Not eventually. Not when a client asks. Not after a support ticket appears. Scanfully brings WordPress Site Health signals into one place, so teams can review important checks without opening every admin area. That saves time. More importantly, it makes weak signals easier to notice. Read more about Scanfully’s WordPress monitoring features here: scanfully.com/features/ Use it to review where your current Site Health workflow creates blind spots.

The body can absorb as much Protein as you give it in a single sitting 50 grams, 100 grams, 200 grams…doesn’t matter Hopefully 2026 is the year this myth FINALLY gets laid to rest

Most WordPress email problems do not start with an obvious error. The form submits. The plugin logs success. The user sees confirmation. But the email never reaches the inbox. That is the blind spot. WordPress can confirm the send attempt without proving delivery. Scanfully’s Email Deliverability Monitoring checks the path beyond WordPress, including transport, authentication, blocklist signals, and inbox arrival. That gives teams a better way to catch silent email failures. Read more here: scanfully.com/scanfully-1-9-… Start there if your current check stops at “message sent.”

A WordPress site rarely becomes slow all at once. It drifts. A plugin update adds overhead. A third-party script gets heavier. A page builder layout grows. A few images slip through without proper compression. Then someone says, “The site feels slower lately.” Scanfully tracks performance over time, so you can spot changes before they become vague complaints. Because “it feels slow” is not a diagnosis. A graph is a better starting point. Read this piece on WordPress performance monitoring: scanfully.com/wordpress-perf… Use it to rethink how you track speed after changes, not just during audits.

We’re using Cloudflare Email for our Email Deliverability Monitoring at @Scanfullyapp as well. Such a no brainer.

I voted yes. But… I think dogfooding is important part of understanding your product, the environment, see what others do, etc. I will personally always run stuff on WordPress where it makes sense.

A small DNS change can create a very strange support day. The site still loads for some people. Email starts acting up. SSL validation becomes noisy. A CDN behaves differently. Nobody connects the symptoms at first. That is why DNS belongs in your WordPress monitoring workflow. Scanfully watches DNS records and helps teams see important changes before they turn into long debugging sessions. Because DNS problems rarely announce themselves clearly. Read what changed in Scanfully 1.10 here: scanfully.com/dns-monitoring… Use it to check how visible DNS changes are across your sites.

The worst WordPress question is not “what broke?” It is “what changed?” Because without that answer, everyone starts guessing. Was it a plugin update? A content edit? A theme change? A user role change? A late-night dashboard tweak? Scanfully’s WordPress Activity Log gives you a clearer timeline, so you can connect site issues to actual activity. That matters when a client asks what happened. And it matters even more when you need to fix it fast. Read why serious WordPress sites need an offsite activity log: scanfully.com/why-every-seri… Then compare it to how you currently answer “who changed what?”

Great article from @remkusdevries This would be a great value for the community and people that are a bit further in their professional journey! remkusdevries.com/the-wordpr… #WordPress #WordPressCommunity

This sentiment is a great case for a course I've got planned for the @within_wp Guild on "WordPress Multisite, the how, the why, and when"

The in-depth WordPress conference that doesn't exist yet, but should. @remkusdevries is making the case for a single-track event built for practitioners who are past the tutorials. To quote Remkus: "One where those building for the enterprise leveled clients feel just as at home as those aspiring to work at that level." Read it and tell him this needs to happen! remkusdevries.com/the-wordpr… Sharing this = ❤️

A missing image can make a page feel abandoned. Even when the site is online. Even when performance looks fine. Even when WordPress shows no obvious error. That is why content integrity needs its own checks. Broken media usually appears after edits, migrations, imports, cleanup work, or URL changes. And teams often miss it because they are checking availability, not the page experience. Scanfully’s Content Health monitoring helps catch broken links and broken media earlier. Read why content health matters here: scanfully.com/introducing-co… Start there if your monitoring still treats “page loads” as “page works.”

Yes, yes, yes! This! ⬇️

As much as I enjoy attending WordCamps, yes to this please.

Don't want to pay monthly for Canny? Build a feedback board on WordPress in an afternoon with GravityBoard. Voting, statuses, threaded comments, full ownership of the data, no per-seat pricing. gravitykit.com/canny-alterna…

A plugin update does not always break a site immediately. Sometimes it changes one small thing. A query gets slower. A form behaves differently. A page starts throwing warnings. A checkout step feels off. Then the team has to reconstruct the timeline. Scanfully’s WordPress Activity Log helps connect monitoring changes with actual WordPress activity. So when something shifts, you can ask a better question: What happened around the same time? Read why offsite activity logs matter here: scanfully.com/why-every-seri… Start there if debugging still begins with guesswork.

I have an idea about The WordPress Conference We Need Next: remkusdevries.com/the-wordpr…

Reminder: the 2026 #WordPress #Security #Survey is still open. If you work with WordPress, please spare a few minutes. Your input will help WordPress site owners better understand current security trends & best practices. Take the survey --> melapress.com/survey/