Remkus de Vries

Bringing clarity to WordPress builders and companies at the intersection of performance, tooling, strategy & education.

👷🏻‍♂️@Scanfullyapp
👨🏼‍💻@Within_WP

[Remkus de Vries @remkusdevries]

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.
https://t.co/kd4tJJFwlf

[Scanfully @Scanfullyapp]

More alerts do not mean better monitoring.

They often mean more noise.

A useful alert should help you decide what needs attention.

Is the site down?

Did SSL fail?

Did performance change?

Did DNS move?

Did a vulnerable plugin appear?

Scanfully sends notifications around important changes, not random dashboard clutter.

That helps WordPress teams respond sooner without turning monitoring into another inbox problem.

Read more about Scanfully’s features here: https://t.co/Bb8znzEkoj

Start there if your current alerts create more work than clarity.

[Remkus de Vries @remkusdevries]

@markjaquith @mattpocockuk >>>>>>>>>

mostly those

[Remkus de Vries @remkusdevries]

@TadekSolarz Die in Gmünd is ook nice 😊. Oh, en de oude in Stuttgart was ook top. Maar kneuterig vergeleken met wat er nu is.

Auto’s zijn mijn favoriete vorm van kunst.

[Remkus de Vries @remkusdevries]

@markjaquith @mattpocockuk 50% hit and miss for me. Always has been.

[Scanfully @Scanfullyapp]

Content changes can break more than the words on a page.

An editor removes an image.

A link gets pasted incorrectly.

An embed stops loading.

A button points to an old campaign URL.

The page still loads.

But the user experience is worse.

Scanfully’s Content Health monitoring helps teams catch broken links and broken media after real content work happens.

Because content maintenance should not depend on someone manually revisiting every page.

Read more about Content Health here: https://t.co/jfww3FwnCj

Start there if content edits still create issues your team finds too late.

[Remkus de Vries @remkusdevries]

@GayaKessler Mooi mooi

[Remkus de Vries @remkusdevries]

@GayaKessler Alles waar ik controle over heb zeker! Met jou?

[Pablo Fredrikson @PeladoNerd]

https://t.co/zfFpPnJbdr

[Scanfully @Scanfullyapp]

A slow WordPress site does not always need another caching plugin.

Sometimes the issue starts earlier.

DNS lookup time.

TLS handshake.

TCP connection.

TTFB.

Backend execution.

Those signals matter because “make it faster” is too vague to act on.

Scanfully tracks performance over time and helps teams see where loading behavior changes.

That gives you a better starting point before you touch plugins, CDN rules, or hosting settings.

Read more about WordPress performance monitoring here: https://t.co/LB8XK5HX03

Use it to move from speed opinions to actual performance signals.

[Scanfully @Scanfullyapp]

A plugin update can look successful and still cause work later.

The update completes.

No fatal error appears.

The site stays online.

Then performance starts drifting.

That is the kind of issue teams miss when they only check whether the update broke the site immediately.

Scanfully tracks performance and WordPress activity, so you can connect slowdowns to recent changes more easily.

That makes post-update monitoring more useful.

Read more about WordPress performance monitoring here: https://t.co/LB8XK5HX03

Use it to check whether your update workflow watches what happens after the update.

[Remkus de Vries @remkusdevries]

@jamesckemp @gautamkhorana Look at the chesticles in that thumbnail 💪🏻

[Remkus de Vries @remkusdevries]

@austinginder @Gravnetic Silver standard. Maybe.

[Scanfully @Scanfullyapp]

Checkout problems do not always start in WooCommerce.

Sometimes the issue sits outside WordPress.

An SSL certificate fails.

A redirect behaves differently.

A browser warning appears.

A payment flow loses trust before the customer completes it.

Scanfully monitors SSL certificates so teams can catch certificate issues before they become visible in critical flows.

That matters because visitors do not diagnose SSL.

They just hesitate.

Read more about Certificate Monitoring here: https://t.co/iAfeSM4R9E

Start there if SSL checks still live outside your WordPress maintenance workflow.

[Scanfully @Scanfullyapp]

A CDN can make uptime look simpler than it is.

The cached page responds.

The visitor sees something.

The uptime check passes.

But the WordPress origin may still be struggling.

That distinction matters when you manage sites behind caching, proxy layers, and edge networks.

Scanfully supports CDN-aware uptime monitoring, cached-only detection, check modes, and warning statuses.

So your monitoring can better reflect how modern WordPress sites actually run.

Read more in the Scanfully 1.10 release notes: https://t.co/y0YcJMyw6i

Start there if your uptime checks only see the cached surface.

[Remkus de Vries @remkusdevries]

@MarcoAlmeidaPT @westguard @WCEurope

[Remkus de Vries @remkusdevries]

@scottbuscemi Brb, chaning my LinkedIn profile.

[Remkus de Vries @remkusdevries]

@gauravsapkotanp Cloudflare.