mklappen

Great, thanks so much! That worked with keeping same priority.

One follow up question, when adding an new option to the ‘args’ param

'args' => array( 'object_type' => array( 'post', 'page', ) )

I did that with an array_push adding my custom post type to the end. Just want to make sure that’s correct way or is there a “better” way to update params

array_push($field['args']['object_type'],'my_cpt');

Thanks again, appreciate it.

Thx, will keep eye on that discussion.

Hi,

Thanks for quick reply and explanation, definitely helps clarify. Makes sense and noticed the “preload” value in the rel tag.

Interesting that in the help docs loadcss is recommended (https://developers.google.com/web/tools/lighthouse/audits/unused-css#deferring) but yet GPSI doesnt appear to detect the preload when its being used…

Thanks again
Michael

Hi
I am having similar issues with inline & defer section of autoptimize. I have created the critical css entered into inline & defer box but each time I rerun google pagespeed insights it comes back with #1 recommendation being to “Defer unused CSS”. It lists the two autoptimized generated css files.

When I select the “Inline and Defer” option and paste in my critical css, does the plugin defer the .css files it has created? or do I need to select/do something else?

I have created critical css via both options provided in the FAQ but with no change in results from google pagespeed.

Has anyone had success with google page speed insights recognizing that the autoptimize css files have been deferred?

Thanks!
Michael

I have noticed same issue. I click on category to filter the list of pages I see and then sort based on post counter column and it’s not sorted correctly from high to low/low to high.

Thanks, yeah doesn’t break anything, just noticed the warning message when I had debugging enabled.

Disregard. I have traced the issue to another plugin and fixed.

Great, thanks. I will be sure to check out and give it a try.

ok, that’s what I thought. A new feature in future release if possible (and if not to much of drag on your time) would be great!

thanks

Thanks for this, very helpful.

One thing I notice was that clearing data from the plugin UI, doesn’t clear anything from post_meta. So you if you want to clear/remove any of the “views_*” I had to delete manually from wp_postmeta.

Thanks again!

Thanks… dumb mistake.

I did try that before but I was putting cf_subtitle rather than variable name of cf_wps_subtitle.

thanks again
mk

Thanks, whatever update you made worked on both the single.php and single-ctp.php pages.

Thanks again.

I do not use another plugin for meta tags/seo

I have a custom template and this issue is occuring for both the single.php and single-ctp.php pages.

After troubleshooting, the title and description tags set in the Homepage meta fields in Settings page of WP Meta SEO are coming through to the single.php and single-ctp.php pages rather than the ones set for each post.

So it appears WP Meta SEO sees my single pages as the home page? However when I echo out is_front_page() from the single.php pages it does not show as a front page…

apologies for the double post…will close this one but leave other open.
thx.

Thanks! not sure how I missed seeing the custom_args parameter in the documentation. I simply passed my custom WP_Query args into custom_args then set offset=5 and is working exactly as I wanted.

Thanks again