you can limit calls and ignore args like this to reduce performance: // Limit backtrace to last 3 calls as we don’t use the rest // Limit argument was introduced in PHP 5.4.0 $backtrace = debug_backtrace(DEBUG_BACKTRACE_IGNORE_ARGS, 3);
There’s zero meaningful difference in performance between plugins and functions.php. All plugins are is PHP files that WordPress will run as it loads, and functions.php is just a file in the theme that WordPress run as as it loads. Performance is not a consideration when choosing between a plugin and functions. The right choice depends … Read more
From searching around, the consensus seems to be that the only real impact of inactive plugins is in the Dashboard, because that’s where get_plugins() (which scans the wp-content/plugins directory) is called. So probably zero impact on public-facing pages.
Reduce the amount of plugins. Check your theme for memory intense stuff or lots of queries. Add this line to your footer or hook it to the shutdown hook to see some basic information: <!– Time needed to print this page: <?php timer_stop( 0, 3 ); ?> Number of queries needed to process this request: … Read more
I hadn’t used this specific solution, but any self-hosted analytics in general should be considered potentially huge resource hog: every async action in WordPress is effectively another WP core load, so if tracking code makes even one additional async request to back-end it effectively doubles the load; stat logging by nature cannot be cached; stat … Read more
I usually use the timer_stop() function via the WordPress ‘shutdown’ hook, like this: // Grab the page load time upon WordPress shutdown. function page_load_time() { echo ‘<p>Page load time: ‘.timer_stop(0, 5).’ seconds.</p>’; } add_action( ‘shutdown’, ‘page_load_time’ );
It looks like your site is doing a lot of processing when displaying a page. have you tried adding a caching mechanism? you can give plugin a try: http://wordpress.org/extend/plugins/w3-total-cache/
I get what you want, it will require some coding skills though. What I did was create myself a plugin that registers a new menu page, and then I use wp_insert_post() function to create a post with given parameters. You can check out my plugin here: http://www.mediafire.com/?499tk848njaz7hq It’s for fast image posting, but I believe … Read more
There are a few pitfalls, mainly with wpautop being applied after the shortcode filter, and multiple do_shortcode calls because of plugins that already added this filter to widget_text. See the discussion in the following ticket: http://core.trac.wordpress.org/ticket/10457
Based on the information provided its nearly impossible to tell whether or not WordPress is the cause of your problem. However its almost certain that its not. That amount of bandwidth is highly excessive for it to be contained to a “problem* caused by the WordPress core itself. You could attempt to inspect the amount … Read more