While working on a couple of WordPress sites, attempting to optimize load times and help some clients to get their sites running faster, I’ve read a lot of articles on speeding up your WP. A lot of them focus on the obvious (but good) points; build a static site by removing as much php as you can, run a cache, configure your server/database server… there’s one major factor that slows down a lot of these sites though that’s a lot harder to address than the rest: Plugins.
Everybody has a different coding style, some good, some bad, and most of the time there’s more than way to skin the kitteh, which provides a lot of options for how much or how little functionality you add to your site.
I’ve been playing around with WP_Styles and WP_Scripts writing some of my own shorthand functions to help me try and remove this mess when possible, but due to those different coding practices that are employed by the plugin authors, it can be frustrating at best trying to incorporate something into your site that can and will remove all these unnecessary calls on pages that don’t require them, and doing it in such a way as to not have the site break next time the plugin is upgraded and some of the codebase changes.
I’d like to know if there’s any interest out there for some kind of system to help deal with this. Something that would permit you to access a be-all-end-all list of what’s in the queue for your page, and somewhere you could hook into post queue pre fire to strip out unwanted baggage with conditional structures.
Yay, nay? (should I post this to hackers, or would it be off-base?)
- The topic ‘Built in plugin management and removing idle scripts’ is closed to new replies.