Performance Nag: Inactive

Hi @lukehm,

I’m not sure what Performance Nag: Inactive means

It means that the plugin hasn’t displayed a notice to you regarding performance yet. The plugin displays such notice when it detects that your site might be a high-traffic one to let you know that you may need to make some changes in order for your site to keep running at good performance levels.

WPP is not collecting data

WordPress Popular Posts can’t reliably track visits on your site due to a conflict with one of your plugins, see Is WordPress Popular Posts compatible with plugins that minify/bundle JavaScript code?

If you need help identifying which plugin might be the one causing this then please go to WP Dashboard > Settings > WordPress Popular Posts, click on the Debug link at the top center of your screen and share the info displayed there here so I can have a look.

I got a PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /var/web/site/public_html/wp-includes/class-wpdb.php on line 2320 when I tried to delete a post. The only way to stop it was disabling WPP. I deleted WPP and reinstalled with new tables. I dont know if any of this akes any sense to you?

Honestly this could be anything. The error message itself doesn’t really provide any useful hints. It might be a good idea to reach out to the people who maintain your website / your developer and have them look into this for you.

Thanks Hector I found the plugin – Hummingbird.

Nice! I suspected that that was the case. I saw some references to Hummingbird in the HTML source code of your site and was waiting for your feedback but you figured it out first, good job!

Page caching at the server-side using FastCGI turn on. The cache clears every hour. If I’m happy that the WPP lists are only updated every hour am I right in thinking that Data Caching: Never Cache and Load popular posts list via AJAX: Disabled are the right settings?

Yep, that should be fine. I can’t think of any downsides, if anything your site should perform at least slightly better in terms of speed, loading times, etc. as it’ll run less database queries per hour with that setup.

There might be a way but I’m not 100% sure that it’s compatible with page caching so I’m not going to share any details yet. I’ll get back to you as soon as I know more.