Rather than querying for a single item and then querying again for 6 more excluding the first, you can just do a single query for 7 items and selectively output markup by checking which post you’re currently outputting in the loop via $your_query_object->current_post. You can also combine that with $your_query_object->rewind_posts() to run through the same … Read more
No. Let’s compare. Normal load: Access URL. Load WP core. Retrieve stuff from database. Load template file. Ajaxy load: Accesss URL. Load WP core. Load template file. Load JavaScript. Make Ajax request. Load WP core (again). Retrieve stuff from database. Receive stuff from Ajax. Put into page. Repeat steps 5-9 for each Ajax request.
No, notices by themselves are not a performance issue and generating them typically doesn’t take considerable resources (there are exceptions if you are replacing error handler – I seen it get slow because of larger output volume and conflicts with antivirus). Of course what they do indicate is potential issues with code quality, which is … Read more
No the depth of your directory structure has almost no impact to load time. Maybe if your structure is very depth and the URLs for the images are very long you can hit the maximum length or your markup blows up. But a flat hierarchy should not be a problem as long as you keep … Read more
I had the same problem. You likely don’t need this any more, but just in case anyone else has this problem, here it is: The first hint of the issue with Chrome and prettyPhoto is that it occurs only when gallery images have a very large resolution and when thumbnails are being shown. What seems … Read more
Sagive, wp-blog-header.php loaded in the index.php on each page request. AJAX calls included (if that’s what you mean “time after time”. Then it loads template-loader.php. This has nothing to do with the SQLs you see, and not with the “spikes”. Install the Query Monitor plugin to see your SQLs better in the Debug Bar. Do … Read more
Yes, you should flush rewrite rules in this case, because you add rules for every author based on his nicename. To be more precise, you should flush them after any author changes his nicename also. And you do this using author_rewrite_rules hook, which is fired in wp_rewrite_rules() only when there are no rules in database. … Read more
It’s a valid theory and under some circumstances such micro-optimization might make a difference (making content fit into single packet rather than be split into two). However you misinterpret the size information. 8.5KB is gzip-compressed version of your page. Since repeats of same string are highly compressible, your optimization won’t reduce this by 5KB. How … Read more
For each extra functionality, you are going to pay for How much would depend on the function or action. It is like @TomJNowell said, even a simple echo statement costs time and memory although it is really minute and insignificant. The real issue here is db calls as they can get very expensive depending on … Read more
The problem with orderby rand is that on most setups the database will load all posts into memory, then randomly order them, and return what you asked for. It’s that loading into memory that makes the query super slow/expensive Also yes, terms are individual categories and tags, where category is a taxonomy, and the ‘development’ … Read more