I answered a similar question on Stack Overflow recently. Don’t forget that the profiler itself adds a big overhead. If your page loads are still really slow with XDebug disabled then I don’t think your problems are limited to translation files and you should look at caching entire pages. You can eliminate MO file loading … Read more
There’s a post here that’s very good about load optimization and performance: Steps to Optimize WordPress in Regard to Server Load? It might be a good idea to also utilize a CDN for a majority of your page requests. If you want performance you’ll have to minimize requests to your database and setup aggressive caching. … Read more
All of these hooks are called in a similar fashion and get passes similar data. Under normal circumstances there should be no meaningful performance difference between them. One scenario I can think of is that if you aren’t properly targeting your code to specific queries and it runs in every query then posts_search might fire … Read more
I think that you can improve performance saving view information in one single option instead in post meta applying the filter date on saving instead of on retrieving create the markup and save in a transient instead of saving the query (fragment caching) Rough implementation in a class class PopularPosts { const OPT = ‘myplugin_popular_posts’; … Read more
Template tags rely on global $post (unless you explicitly provide something else to those that support it. So either: they get something from that variable (no reason to go for it in database) or they don’t (then they fail because they have no clue what you want) Under most normal circumstances there is no reason … Read more
The Transient API saves data inside the database, which isn’t as effective as APC, but a similar workflow as used for transients can be used for APC. It is important to check if APC is available and active, so its functions are usable. Because this isn’t always the case, it is to consider to add … Read more
I don’t see a way to make the query faster, but we can cache the result. Unfortunately, there is no hook to circumvent next_post_link() and previous_post_link(), so we have to replace those functions with custom functions. The following sample code uses a post meta field to store the result. There might be side effects – … Read more
Having 2 revisions or 100,000 will not change front end performance in a default plugin-less WordPress setup However plugin and theme authors who do not query the database correctly, could end up accidentally searching/querying revisions, which could have some performance issues Here’s a snippet on it revisions take up space in your WordPress database. Some … Read more
Well, get_posts() actually instantiates a new WP_Query object, so if you’re comfortable using WP_Query directly, don’t even bother with get_posts(); get_posts will only return the results from the database, whereas WP_Query gives you the whole functionality of the class.
First: don’t enqueue custom versions of WordPress core-bundled scripts, including (and especially) jQuery. Second, to answer your question: those Plugin scripts and stylesheets are enqueued, using add_action(), via a callback hooked into one of the following action hooks: wp_head wp_enqueue_scripts wp_print_scripts wp_print_styles (There are others, but those are the most likely.) Inside the callback, the … Read more