Pagespeed after 5 minutes

You can check at Google’s PageSpeed Insight website and see what is the reason for lower scores. I guess, it is because of long response time (either because of cache was reconstructed, or WordPress’es daily check for updates was triggered, or something like that).

Hello Denis,

Thank you for your reply… ??

– Now I have another problem with your plugin that otherwise looks awesome, and that I have high hopes for..! ?? The problem is this: When testing my site with pagespeed Pagespeed Insights Then I get a 500 error…? This was not here before… ??

I was wondering… If I gave you access to my WP-admin? Could you then take a quick look at it maybe? ??

Ps. I wish there was a central “easy-to-find” clear all cache-button in you plugin? ?? Right now there is a button like this… But it is hidden away…

Sincerely,
bobo

In the case of 500 server error, it’s necessary to look at error_log file, because of usually it is related to error on PHP side. Additionally, you could try to enable logging in Advanced tab of PageSpeed Ninja settings page, it will log all errors, warning, and even notices, that may help in search for bugs (note that for security reason there is no web access to generated log file, and it should be loaded using (S)FTP).

Dear Denis,

I just downloaded the “/wp-content/plugins/psn-pagespeed-ninja/includes/error_log.php (863 bytes)” But the weird thing is this… In the plugin it says 863 bytes.. But FileZilla says the file is like 58MB? ??

As said above, I can give you access to WP-Admin, if you wish to take a quick glance at it? ??

I’m more interested in those 58Mb error_log.php file. You can send access credentials to hello-at-pagespeed-dot-ninja.

PS. But let me note that email is not a secured protocol, it may be dumped by a man in the middle (even if it is very unlikely), and so be sure that sent credentials will be expired in few days after you sent them.

We have adjusted default caching lifetime settings in PageSpeed Ninja 0.9.29 and 0.9.30 (previously it set to was 15 minutes only). Starting from 0.9.30 time-to-live for internal fragment cache is detached from global “Caching time-to-live” parameter and is set to be at least 24 hours; it improves performance significantly even for 15 minutes TTL in the Safe preset.