ArtakEVN

Hi. Thank you for reply, but this isn’t helpful. I’ve tested the issue in Chrome, no extensions, All WP plugins disabled besides Elementor. Theme – “Hello Elementor” or “Twenty Twenty-Four”. Same error in console.

Quick search shows that I am not the only one reporting this : one, two, three. I am sure everybody has it, but since this is not blocking any functionality and does not affect front end not all users aware of that.

Previously I was able to disable Global Style Guide to fix this issue. But now that option is missing/removed.

Hi.
Sure, you can download it here

Hi @ninjateamwp
Thanks for quick reply. Functional wise no issues. Just hundreds of similar php warnings.

hi. Structure is
1. home/public_html/mainDomain/Directory/Site1 (3rdfloortailors.com)
2. home/public_html/mainDomain/Directory/Site1/Site2 (3rdfloortailors.com/brosche)
3. home/public_html/mainDomain/AnotherDirectory/Site3 (arpinursery.ca)

For case #2 I am more or less understand. Thy are under same domain. One is just WP and the other one is Woocommerce as a path …
Main issue with #3

Hi. It is cPanel (version 100.0 (build 5)), latest WP and latest stable LSC

Thank you. I think the issue is fixed now

Sorry. wrong forum

Hi.
In fact this is old native width and height to the image element: <img width="150" height="50" src="... />. Sometimes its missing and I think Litespeed adds it in most of cases. (Add Missing Sizes)
When I run my website through Google Page Speed Insights I see an action point of “Image elements do not have explicit width and height“.
Here is the brief explanation of what do they expecting from images to avoid any Cumulative Layout Shift – https://gtmetrix.com/use-explicit-width-and-height-on-image-elements.html

Regards

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

Hi qtwrk
You are right. Looks like data-no-lazy=”1″ is coming from theme and not from Litespeed.
Is there a way to include this element (logo) into “explicit width/height” party manually?

Thank you

Thank you @qtwrk
I’ve deleted all cache and optimized data, remed all media exclusions. Did “reset” everything. Now lazy load is working (thats what you found ?? )

now I have lqip and lazy load (with some issue) and most of webp images. But still have issues with some images

In media library I see WebP generated and says WebP saved 27% but while the optimized jpg is available the WebP version is missing. This is happening on multiple files.

There is an issue with lazy load as well. But still trying to understand steps to duplicate the issue.

As I understood there is an issue with the cloud CCSS generator engine and there is not much we can this moment until they improve the CCSS engine.

What I’ve also done trying to fix the issue is “Reset Configuration Wizard” in Yoast Test Helper and went through wizard steps. Maybe that helped me to fix the issue. not sure

Thank you for quick response.
Looks like uninstall/fresh install fixed the issue.

Thank you

Installed and activated Yoast Test Helper plugin.
Did Tools → Yoast Test → Yoast SEO → Reset indexables tables & migrations options to reset it;

Then went to Start SEO data optimization
got an error
Oops, something has gone wrong and we couldn’t complete the optimization of your SEO data. Please click the button again to re-start the process.

Error.log returned
PHP Fatal error: Uncaught TypeError: Argument 1 passed to Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder::is_invalid_ancestor() must be an instance of Yoast\WP\SEO\Models\Indexable, bool given, called in /home/user/public_html/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php on line 176 and defined in /home/user/public_html/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php:340
Stack trace:
#0 /home/user/public_html/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php(176): Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->is_invalid_ancestor(false, 340, Array)
#1 /home/user/public_html/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php(112): Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->add_ancestors_for_post(340, 3090, Array)
#2 /home/user/public_html/wp-content/plugins/w in /home/user/public_html/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php on line 340

Thank you!