Query results for posts, terms, and metadata get placed in cache. If a function is called that accesses data from previously queried objects within the same request (or you’re using a persistent cache mechanism that maintains data across requests), it will not trigger another query and will instead fetch the data from cache.
A few things Use media_handle_sideload so that WordPress moves the files to the right location and validates them for you, creates the attachment post etc, none of this manual stuff Don’t run this once and expect it to do everything. You’re just going to run into the same problem but further into the import. If … Read more
You need to check the actual access logs, such as web, SSH, etc., and if you can access it, the MySQL log, too. That will show you what is possibly hitting the site at that time and let you differentiate between a huge unexplained web traffic spike from a bot and something that is happening … Read more
You need to look at this from a couple of perspectives and then you have to weigh the odds against each other In general, shortcodes will be slower (we are talking milliseconds here) as they need to be parsed and processed by the shortcode handler. USAGE: [my_shortcode] in post editor Shortcodes in general are quite … Read more
No. All posts are stored in the wp_posts table. The post type is defined by post_type column. Regardless to custom post types included in query, there is only one SQL query executed. Of course there may be some performance hit caused by a little bit more complex query (in vs. =), but it’s marginal.
Defining WP_HTTP_BLOCK_EXTERNAL constant (wp-config.php is good place to do this) would kill all outgoing network requests, other than those for hostnames, defined in WP_ACCESSIBLE_HOSTS. See source for details, doesn’t seem to be documented in Codex.
Your code shows an inline script, which adds a new script tag to the DOM, which probably slows down your website’s loading time. This is not an inline script tag then. Try adding this line s.defer = true; after s.async = true; to add the defer attribute to your script tag. It should then look … Read more
High CPU usage on 404 errors
Start with “view source” of rendered HTML and then work backward from that, building a new theme by pulling whatever css, php files and functions from the parent as needed. (footnote – thank you for the pointer to the ‘dust me’ utility, I will check that out).
You must use cache systems.without caching, your site will be slowly.use APC or memcache for increase speed of your home page. or use redis.