Today I discovered a bug in a #WordPress plugin update that had a tremendous negative performance impact.
https://twitter.com/remkusdevries/status/1622545110176083968
Luckily the solution was an easy one to fix, but I've gotten some question about how I found out where the issue was, so I thought I take you along on some performance debugging steps I always take.
First off, I work with both local development sites as well as staging sites.
First off, I work with both local development sites as well as staging sites.
This means I work with two other version of the site besides the production site itself. This is how I discovered the issue before the update was deployed to the live site.
I'm using the same tools for all three environments.:
– Two WP CLI extensions:
I'm using the same tools for all three environments.:
– Two WP CLI extensions:
WP Profile & WP Doctor
Both have different ways to inspect whatever needs inspecting. Learn about them, play with them and add them to your deployment flow. They're indespensible in my dev environement just as much as my text editing tool.
Both have different ways to inspect whatever needs inspecting. Learn about them, play with them and add them to your deployment flow. They're indespensible in my dev environement just as much as my text editing tool.
– WP Debug
This goes without saying, right?
– Query Monitor
The WordPress plugin Query Monitor, together with Laps, are the two plugins I install on every single non-production site. They help to debug where issues lie, and where the fix most likely is to be found.
This goes without saying, right?
– Query Monitor
The WordPress plugin Query Monitor, together with Laps, are the two plugins I install on every single non-production site. They help to debug where issues lie, and where the fix most likely is to be found.
– Slow Queries
Turn on (or have your hoster do it for you) Slow Query log and see what's causing your WordPress site to slow down. And where. This is one you may want to have turned on production for short times as well.
Turn on (or have your hoster do it for you) Slow Query log and see what's causing your WordPress site to slow down. And where. This is one you may want to have turned on production for short times as well.
– Debug Plugins and Themes
Disable plugins one by one to identify the source of any performance issues.
There are ways to automate this with WP CLI. I'll cover this in my WP CLI course: remkus.devries.frl/courses
Disable plugins one by one to identify the source of any performance issues.
There are ways to automate this with WP CLI. I'll cover this in my WP CLI course: remkus.devries.frl/courses
And lastly:
– Chrome DevTools
Use the Network tab first, then look at Performance insights, Performance and Lighthouse.
That's it. That's what I use by default.
There is more to use, but this is my base performance debugging stack.
– Chrome DevTools
Use the Network tab first, then look at Performance insights, Performance and Lighthouse.
That's it. That's what I use by default.
There is more to use, but this is my base performance debugging stack.
Curious how I could help you or your clients? Hit that link in bio and let's start that conversation.
If you enjoyed this thread, please
① Retweet the tweet below to share this thread with your audience
② Follow me @remkusdevries for more of these
🙏🏻🤩
If you enjoyed this thread, please
① Retweet the tweet below to share this thread with your audience
② Follow me @remkusdevries for more of these
🙏🏻🤩
https://twitter.com/14264386/status/1622627966998966272
Wrote is out on my blog as well: remkus.devries.frl/wordpress-perf…
I run a #WordPress related newsletter that's not your average news roundup. Expect opinionated, and interesting content you're not reading anywhere else.
Curious? Have a look 👉🏻 remkus.devries.frl/subscribe
Curious? Have a look 👉🏻 remkus.devries.frl/subscribe
• • •
Missing some Tweet in this thread? You can try to
force a refresh
