Vegsur

Ive did that and im 99% sure delayed javascript is doing that, thats why i was thinking if i could exclude the toc or something. Is it bad to use delayed js loading? Can it cause google indexing problems or something

I have Easy Table of Contents plugin and its causing alot of “Not Mobile Friendy” issues. I can see that when i load my page the Table of Contents loads open and then closes after the page is loaded. TOC should be closed until its opened manually.

Also do you know, can delayed javascript or some setting cause google indexing issuses?

Report number: NHYSYOKA

Solution for this would be great.

No solution for this? Had mobile friendly problems for weeks now and found out its this plugin causing it. Need some padding between the links

Mostly im getting “Content wider than screen” & “elements too close together.” I just clear cache and validate fix and they are gone. Errors are randomly coming to between all of my pages. And the site is optimized on mobile perfectly, there are no such problems. I was wondering is this jquery async causing this if google sees the site wrong

Thank you for your time and answer, very helpful! ?? I cant notice any errors in the site but feels like after putting that async, google is giving me alot of not mobile friendy errors and my new posts are not getting indexed because of this. Where i can see console errors?

I added this code and yeah the first contentful paint problem went away but now my mobile menu is not working ?? so the problem is something related to that? `add_filter( ‘script_loader_tag’, ‘add_async_to_script’, 10, 3 );

function add_async_to_script( $tag, $handle, $src ) {

//You can use this to make all async

$tag = str_replace( ‘ src’, ‘ async src’, $tag );

}
`

Removed that and added this <script src=”/wp-includes/js/jquery/jquery.min.js?ver=3.6.0″ async></script> and the problem is fixed but could this cause some problems in site?

• This reply was modified 2 years, 11 months ago by Vegsur.
• This reply was modified 2 years, 11 months ago by Vegsur.
• This reply was modified 2 years, 11 months ago by Vegsur.
• This reply was modified 2 years, 11 months ago by Vegsur.

I have been investigating the issue and saw that, when loading the page on mobile, the main menu or something acts weirdly. Ive had problems before with mobile menus, could this be the reason? Video in link https://drive.google.com/file/d/1ItMOqYNLuOIy40P-wc7VdreiWiP9_GZ-/view

Also i made and EMPTY test page and still First Contentful paint over 4000ms. There is picture from GTMterix waterfall report https://ibb.co/DtjJC8G

Nice thank you very much for your time and help!!! ??

Do you guys have any guide, how to do that or should i dive in the google search?

Ive destroyed and optimized then 5 times in 2 days. I think i had “remove the original backup” on. Is there anything i could do now?

Deleted image and added back then optimized. Says in media library its optimized but nope https://gyazo.com/b511a006c7b19c7c548b7e4dd4a3e8b2

Just weird that im 99% sure they had webp versions and i cant do anything to get them back. Its hurting my SEO

• This reply was modified 3 years, 2 months ago by Vegsur.
• This reply was modified 3 years, 2 months ago by Vegsur.

Im pretty sure they had webp versions until i started messing up with the image optimization settings.

After messing up with the settings Google started giving me this “warning” https://gyazo.com/6b328ddfa5a79a47b2ab426fb010693a

So theres nothing do, like force them to be served as webp. Or do i have to just ignore the and let them be?

Yeah in home page, those images in “blog entries” or what they are called. https://gyazo.com/2127b462ab4c7b1ecb8be6acd1a7498e All the images in blog posts are webp. but those blog entries and related post images which are the same than blog entries on homepage

Added that top of the .htaccess and it didnt do anything or under the hood means google will still give warnings? Weird thing is that webp. images worked perfectly before. There is nothing more to do?

And why all the other images are server with webp but not the blog entries