Denis Ryabov
Forum Replies Created
-
One of PageSpeed Ninja’s features is rescaling of large images for mobile devices with smaller screen resolutions. PSN is able to do it on the fly, but to improve performance we added a code that creates smaller images automatically for most common screen widths via built-in WordPress feature to create thumbnails. I’ll try to fix it in the next release (thumbnails will be created if rescaling of large images is enabled only). You can remove creation of that thumbnails using
remove_image_sizefunction, but most likely it’s simpler to remove$this->add_image_sizes();from wp-content/plugins/psn-pagespeed-ninja/includes/class-pagespeedninja.php and wait for next release.I see there are other optimizing plugins are used (at least Autoptimize), so maybe there is a conflict. I’d try to disable Autoptimize and test PageSpeed Ninja using different presets (starting from Safe) to found which one suits better. We are going to do some local tests with Autoptimize, but most likely it will be done after next major release (0.10.0) will be released, because of it differs significantly from current 0.9 branch.
Could you post URL of your website? I’d like to check how your mobile menu is implemented internally.
Hmm, could you post link to your website? I’ve found one possibility to reproduce this error, and that one was fixed in the latest release. Most likely you have another source of this error, and I’d like to look at your page sources to found what may be parsed incorrectly there.
Most likely it’s better to use a single optimizing plugin (Autoptimize or PageSpeed Ninja) to don’t duplicate optimization tasks. If you like to use both, I’d try both ways and choose one that works better (i.e. gives higher PageSpeed Insights scores and takes less time to generate page).
Most likely you have another active optimizing plugin that use JSMin library. Try to either disable that plugin, or disable JS minification (i.e. set “Minify Javascript Method” to “None” in the “Minify JavaScript” section of PageSpeed Ninja Advanced settings).
In addition to reply in a nearby topic: try to disable “Experimental Caching” if it is enabled.
What do you mean? Do you have large cache directory? (then maybe this post would be related: https://wordpress.org/support/topic/cache-folder-gets-too-large/)
Fixed in PageSpeed Ninja 0.9.33.
Try different values of “Google Fonts loading” setting in “Eliminate render-blocking JavaScript and CSS in above-the-fold content” section of Advanced tab in PageSpeed Ninja settings. Maybe our javascript-based optimizations conflict with other javascripts on your site.
Currently it looks like you have enabled “Optimize integrations” feature that postpones loading of external “widgets” to speed up rendering of main content. Try to disable it and check again.
I’ve fixed it in local repo, the fix will be included into next release. Thank you for bugreport.
PageSpeed Ninja didn’t support WooCommerce up to version 0.9.30. Since 0.9.31 WooCommerce is supported, but we are collecting feedback about possible issues and that’s why that warning message is not removed yet. Just don’t worry and try it. And if you found some issues, please inform us.
Currently there is no easy way to specify inlined script to don’t be merged, except of disabling of merging of all inlined javascripts.
But there are two tricky ways:
1) add ress-safe attribute to the script tag to skip this js (allowing prior and next javascripts to be merged into a single file), and
2) add data-cfasync=false attribute to disable optimization of this js and preventing merging of prior and next javascripts to avoid possible dependence-related issues.PageSpeed Ninja starts to process a page after it is generated by WordPress, so you can use any hook called by WordPress during page generation.