General speaking yes for read-only applications (until MySQL 5.7, it’s deprecated since version 8.0), it enables equal SELECTs to return data extremely fast if identical calls are already stored in cache. You should consider that: Only exact same clauses can benefit from the cache engine (no spaces, no comments, no actual differences in WHERE expressions); … Read more
In a general sense, any well maintained platform can be used to to create a website with good security. It has to be noted that you will never build a website which is completely secured against hacking and spamming, no matter which platform you use and no matter what genius or pro you are. Hackers … Read more
The wp_cache_*() functions are non-persistent caches which means that they only last during the current page request. This would be beneficial if you’re requesting the same information multiple times during page load. For example, if you’re showing recent posts in the header, content section, and sidebar ( calling the same code 3 times to retrieve … Read more
I had a similar issue on another site recently, memory usage was through the roof. When I checked the db, wp_options was about 80megabytes. Running this SQL reduced the entire db to 15mb: DELETE FROM `wp_options` WHERE `option_name` LIKE ‘%_transient_%’ Obviously, replace wp_ with your table prefix.
The use of SQL_CALC_FOUND_ROWS is not really a problem, although it incurs an overhead. What happens is, WordPress uses SQL_CALC_FOUND_ROWS in order to determine the total posts that would have been returned, if no LIMIT clause was provided. This is necessary in order to calculate and provide you with correct pagination links. Disabling it unconditionally … Read more
Combine JS and CSS for WordPress admin
Use a custom table. Create it as a network table, and store the site ID, so you can use just one table for the whole network. row_id | site_id | post_id | user_id There is no equivalent for such a table in the current core tables. Avoid serialized data, because that format is PHP specific, … Read more
HTTPS has an overhead on processing power on every request – security considerations or usage pattern left aside. That’s the major downturn (and that it ever was, a question of resources), so you should really ask yourself what do you want to offer to your users. It’s absolutely valid to SSL everything ™ for your … Read more
In response to the op’s comment: Update: I’ve deactivated all of the plugins and activated them one by one. The two that seemed to have the biggest effect was Advanced Custom Fields and Use Google Libraries. Here’s what i found. The use of google api’s should save you time and effort, not cost you time … Read more
You could just write your own query, too. That way, it’s one query per category: global $wpdb; $query = ‘ SELECT wpp1.* FROM ‘ . $wpdb->posts . ‘ AS wpp1 LEFT JOIN ‘ . $wpdb->term_relationships . ‘ AS wptr1 ON wptr1.object_id = wpp1.ID WHERE post_type = %s AND post_status = %s AND wptr1.term_taxonomy_id = %d … Read more