WordPress can handle large databases and high traffic quite well. I think one good example of this was seeing some WordPress sites holdup to high traffic when the recent iPhone announcement happened. This really comes down to how well you code your theme/plugins, how you manage caching and your server configuration. WordPress will not be … Read more
This is normal, minification of CSS/HTML and JS is not a magic button. If you have no plugins and 1 style-sheet and minimal javascript (aka not more than 1 function) it will work, but anything above that and your looking at conflict and load order problems. To properly minify takes work, you have to either … Read more
$starttime is undefined in your footer, so you’re subtracting nothing from endtime. declare global $starttime first and it’ll work. that said, it won’t be a very accurate indicator of rendering time, since most of the work WordPress does happens before you ever reach the template and start your timer. There’s already a built-in timer that … Read more
I would go with jQuery UI tabs where the feeds would be hidden because WordPress caches feeds for 12 hours using the Transients API. This would be less expensive than doing an Ajax call for each tab. Use fetch_feed to parse and and cache. The cache times can be filtered using wp_feed_cache_transient_lifetime.
I hate to answer this with a link, But with WordPress 3.3, how it searches for permalinks have been greatly improved so you can almost put anything into the permalinks and it will be fast. http://ottopress.com/2011/how-the-postname-permalinks-in-wordpress-3-3-work/
I suppose you could use wp dequeue script and then use yepnode, but honestly I don’t see the point with regards to speed since wp_enqueue_script already allows for conditional loading with dependencies. This is assuming your using well written theme/plugins that allow for the use of the built in function hooks. You can get an … Read more
The answer is no but just to put your question into perspective I tried the following code. 1.5 million ifs. $start = microtime(); $count = 0; while(true) { $count++; if($count > 1500000) { break; } } $stop = microtime(); $total = $stop-$start; print “Total time:$total”; 0.16 seconds
You can filter ‘posts_fields’, check if it is the main query and limit the queried fields to … whatever you need. See WP_Query::get_posts() in /wp-includes/query.php for details and side effects. For debugging the queries I recommend the plugin Debug Bar. If you add … define( ‘WP_DEBUG’, TRUE ); define( ‘SAVEQUERIES’, TRUE ); … to your … Read more
These queries are the same – the only difference being the syntax. There’ll be no noticeable performance difference. I prefer the first for readability when it is formatted correctly. (Also, the first query doesn’t use the paged argument, so it won’t ‘paginate’ – but I guess that was omitted by mistake).
The Codex page for the Object Cache class holds the answer to this: By default, the object cache is non-persistent. This means that data stored in the cache resides in memory only and only for the duration of the request. Cached data will not be stored persistently across page loads unless you install a persistent … Read more