Bubble people! We need to unbubble! Come listen to me ramble and explain, and hopefully motivate! remkusdevries.com/wordcamp-ar...

WordCamp are great, but they're not enough!

WordCamps are wonderful. I know that from experience, having initiated and co-founded WordCamp Europe and WordCamp Netherlands, and having organized WordCamps for the past 17 years. But if you work seriously with WordPress, WordCamps should not be the only events you attend. In this video, I talk about why WordPress Builders and Developers need to […]

remkusdevries.com

Is 4614 words enough to describe what goes into modern WordPress Query Performance and what changed? Asking for a friend, ofc.

People who, instead of clicking on your message and hitting edit to fix your typo, follow up with the correct spelling of your typo... Who hurt you?

One thing I find myself doing after my holiday break is unfollowing, unsubscribing and deleting posts a lot. I guess I needed some kind of cleanse. How often do you consciously clean up your "inbox"?

Lifehack: for every 5 minutes of doom scrolling , promise yourself to do 15 minutes of working out. If that don’t fix your problems, I don’t know what would.

Let's make WooCommerce work better beyond just speed, m'kay? www.youtube.com/watch?v=COs...

7 Ways to Make WooCommerce More Performant 🚀

--- Links mentioned ---- Omnisend: https://remk.us/cosklc-oipi- H...

youtube.com

I think we’ve made WooCommerce (and WordPress) performance too small. We really have. We keep talking about speed, Core Web Vitals, and TTFB, and those are super important, but there's so much more that goes into a performant WooCommerce site.

If your site only feels fast when cached, you need to know that. Not because caching is bad, no, caching is essential. But uncached requests reveal the raw cost of the application. Your Admin, WooCommerce Checkout, or Logged-in flows.

Responsive images in WordPress are not an advanced optimization. I mean, they are often seen as such, but they are part of the foundation.

Frontend performance is not about making the browser faster, it is about making the browser do less work, less often.

Images inside your WordPress site are not just about file size. Many optimization tricks out there focus solely on "watch out for the size", but don't really explain why... Well, here's why; they affect: - Bytes transferred. - Decode cost. - Render timing. - Largest Contentful Paint.

If your first instinct (still) is “There’s a plugin for that,” this video is for you. youtu.be/E9-cE3OOU1s

Stop Putting Everything Inside WordPress!

** Omnisend → https://remk.us/cr54k** Scanfully → https://remk.us/...

youtube.com

WordPress doesn’t have a plugin problem. It has a “we installed this before we understood the problem” problem. I am less impressed by adding things. I am impressed by removing the wrong things, and wanting to find the actual cause. That’s what this video is about: youtu.be/hclFuxjODfY...

Let's talk about Fonts. Fonts feel like design, right? But in the browser, they behave like infrastructure. They affect text visibility, they affect layout, they affect line breaks. And the can cause invisible text and layout shift.

You'd be surprised how many times I see this: two optimization plugins doing the same job. It should be obvious they are not twice as effective.

A problem I see a lot: most over-optimized WordPress sites are not actually optimized. They are tangled. A mess of criss-cross behavior. One plugin delays JavaScript, another defers JavaScript, and then a a third preloads scripts.

Have you heard about "the Edge"? The non-U2 version? The edge is a layer that lives in front of your site. It's a place in your stack that allows for requests to never reach WordPress at all.

I got a lot of reactions, comments, and DMs to my "The WordPress Conference We Need Next" blog post so I decided to turn it into a video, addressing the entire angle of why this is needed. Watch it and let me know what you think! www.youtube.com/watch?v=qqL...

Implementing HTML caching for your WordPress site is powerful because it creates a fast path. The first request pays the full WordPress cost, and the next visitor gets the finished response.

A cached WordPress page can still create dynamic server load, did you know that? Yeah.. the HTML might come from the edge instantly, but then JavaScript fires background calls.

A CDN (at the Edge) for your WordPress site is not an optional extra anymore, it is part of the modern WordPress performance stack. For these simple four reasons: - It reduces distance. - It absorbs static asset delivery. - It can serve HTML at the edge.

Most slow WordPress sites are not slow because of one huge mistake. They are slow because of small architectural costs that compound. It's one of these things, right? It's a little too much autoload, a few global scripts, some unnecessary API calls.

A WordPress plugin that loads everywhere is a WorsePress plugin. It's asking WordPress to do blind work without any smartness.

The Hooks inside WordPress are not just extension points. You should, instead, see them as moments in time. The earlier a hook runs, the less context WordPress has. This means expensive logic on early hooks can run everywhere, whether the request needs it or not.

Slow queries are not just a WordPress database problems. They happen there, sure, but they are user experience problems if you really think about it. Because every slow query delays the response, every repeated query adds pressure, and every unindexed query makes MySQL work harder than needed.

Your WordPress database is not a storage box. It is, in fact, a part of the performance path. Every request asks it questions. For things like Posts, Metadata, Options, Users, Terms, Settings, and Plugin data, for instance.

Get Ready For the Powerful CSS border-shape Property! We recently got the shape() function and corner-shape property. What else could we possibly need as far as making shapes in CSS? Let me tell you: the... https://css-tricks.com/get-ready-for-the-powerful-css-border-shape-property/

Get Ready For the Powerful CSS border-shape Property!

We recently got the shape() function and corner-shape property. What else could we possibly need as far as making shapes in CSS? Let me tell you: the border-shape property!

css-tricks.com

Silent performance killer in WordPress? A big set of autoloaded options. Because... autoloaded options are huge global memory cost. They load on every request. Before WordPress knows what page is being served. Before templates run.

A cache hit means WordPress (or the caching layer) remembered. A cache miss means WordPress had to relearn and redo. That relearning often means PHP execution, database queries, and extra time before the response can be sent. So enabling Redis is not the goal.

I've been buried deep in writing the lessons for my Cloudflare for WordPress course for the past couple of weeks. The deeper I dive into Cloudflare, the greater the set of options to integrate becomes.