The shop I’m looking after also has a lot of large queries and for us, the solution was a WP optimised hosting provider with litespeed caching and sufficient resources (RAM) to handle the query. And for queries which are always the same, I also use transients. With transients, the query runs only once and is … Read more
get_posts() uses the WP_Query class to fetch posts. Usually, it returns an array of post objects. The $fields parameter for WP_Query accepts two valid arguments: ‘ids’ will make it return an array of post IDs and ‘id=>parent’ will make it return an associative array with the post objects properties as key => value pairs. Any … Read more
It depends on local factors and actual usage patterns. Bigger queries require more memory to store the data and potentially, depending on the plugins you use, to process it into the response, therefor you are more in a risk of running out of memory. With Bigger response (i.e. bigger page HTML) it takes more time … Read more
Query Monitor will show you what is loaded or you can print them directly. function print_wp_scripts_queue(){ $scripts = wp_scripts(); echo “<pre><h1>scripts</h1>”; print_r ( $scripts->queue ); echo “<h1>todo</h1>”; print_r ( $scripts->to_do ); echo “<h1>done</h1>”; print_r ( $scripts->done ); echo “<h1>registered</h1>”; print_r ( $scripts->registered ); echo “</pre>”; wp_die(); } add_action( ‘wp_head’, ‘print_wp_scripts_queue’, PHP_INT_MAX ); wp_deregister_script removes a … Read more
This is not an amount that is likely to cause performance issues. However if you are concerned about leftover transients it is worth looking into if any code you are using is consistently “leaking” them (creating transients that are never removed). See Are transients garbage collected? for relevant discussion and some code snippets.
Not the best way but removing the default WordPress actions that allow any scripts in the document’s head can help: function md_footer_enqueue_scripts() { remove_action(‘wp_head’, ‘wp_print_scripts’); remove_action(‘wp_head’, ‘wp_print_head_scripts’, 9); remove_action(‘wp_head’, ‘wp_enqueue_scripts’, 1); } add_action(‘wp_enqueue_scripts’, ‘md_footer_enqueue_scripts’);`
Continue execution after WP REST API response
My advice to you is not to worry about adding in the copious amount of .htaccess rules for forcing browser caching and setting correct expire time values for assets. If you download the W3 Total Cache plugin it handles adding all of the above into your .htaccess file for you. If you would prefer not … Read more
or should I create a plugin ? if it’s the case, why ? Yes you should: Separation of concerns. A theme is the view of the application. As the facebook functionality is part of your application, it belongs into a plugin. You have one large benefit from moving stuff into plugins: If you exchange your … Read more
Depends. One argument could be that if the requested page use all sizes then there will be a lot of image calls (slower response, bandwidth etc) but you can bypass that i.e. by loading images with JS. Also more sizes means more disk space usage. I don’t think there is any significant performance concern related … Read more