View in #wordpress on Slack
@Timothy_Anderson: Got another performance question for you all. Autoptimize or WP Rocket?
@Myles_McNamara: Personally I like wp rocket better
@Timothy_Anderson: @Myles_McNamara Nice. Any thoughts on how well they work comparatively with Pantheon?
@Myles_McNamara: So I honestly don’t even use it on Pantheon, mainly on sites where doesn’t already use varnish and CDN I’ve had better results, I think I like it better though because the code base is cleaner
Feature wise someone else may be able to say though since I’ve only dealt with autoptimize on client site where they already using it
@Doug: Just a heads up that both these plugins have some known issues on Pantheon:
The platform automatically does it’s best to do much of what those plugins offer by providing full page caching and edge CDN delivery with no configuration. The problems that most folks will want to solve generally involve having too many stylesheets, or using sessions or cookies that prevent caching.
There are two ways to solve the stylesheet issue, the best is to move to a build workflow with something like Parcel or WebPack which can concatenate and minify all your js/css. These approaches are more technical and require you to keep an eye on what your plugins are doing, but are going to be the most performant.
If that’s not an option (maybe you have a client who wants to turn on/off plugins at will a lot) Autoptimize is a decent way to handle concatenation to reduce requests while not needing a ton of technical expertise.
If you’re not familiar with how our edge caching works, I recommend reading the basics here, and the advanced topics here.
Pantheon Docs: WordPress Plugins and Themes with Known Issues
@webidextrous: @Doug Over the years, I’ve requested from WP Rocket that they tune their plugin to be more compatible with Pantheon. It’s been slow progress but some of their more recent versions of the plugin have taken that feedback into account. The last piece is to have them stop rewriting wp-config.php to set WP_CACHE to “true” whenever the plugin sees that it is set to “false”. I don’t know why they think it’s a good idea for plugins to overwrite wp-config.php on the regular, but they do. For now the trick is to keep an eye on the commit log for this change to wp-config.php when making updates to the site, and generally leaving the site’s connection mode set to Git.
@Doug: I’ve had in person conversations with them at WordCamps in the past and they’ve been excited about making it work, but that’s always seemed to end after the camp
and 80% of the features are already included/better integrated within the platform
at least IMO
@webidextrous: Yes, same. I mainly use WP Rocket for the minification, lazy loading, and other stuff separate from what Pantheon provides. The clients whose sites I manage are not the type to be tolerant of the kinds of workflows you mentioned (which are not bad in themselves, just more complicated than they’ll want to deal with). So WP Rocket is the best compromise. Now if it could do something to reduce the overhead of page builders, it’d be perfect. haha
@Joel_Yoder: We’ve experimented with using both, but never saw a measurable improvement in performance on our Pantheon site. We already minify and bundle all of our CSS and JS, so with Pantheon’s edge caching and Redis enabled, performance bottlenecks mainly come down to plugins and how much JS we’re pushing.
We tried using Hummingbird for a while to defer and bundle plugin scripts, but the overhead of the plugin adds ended up negating all of the benefit we were getting from it, so we dropped it. We still use Smush for image compression and lazy-loading and that does make a difference for our performance since our site is image-heavy.