Milind More

Hello @koskar222

Thank you for reaching out to us, When we tested your website, and we didn’t locate any AMP issues or validation errors on the URL provided. Additionally, we checked your AMP page on the AMP test, which also didn’t report any issues.

Can you please share more details about the error, or share screenshots for better understanding.

Hello @madhu34

Making changes in WordPress core files is not recommended, instead can you please use the following code snippet in your child themes functions.php or in a custom plugin.

/**
 * Disable auto sizes for AMP.
 */
function amp_disable_img_auto_sizes() {
	if ( function_exists( 'amp_is_request' ) && amp_is_request() ) {
		return false;
	}
}

add_filter( 'wp_img_tag_add_auto_sizes', 'amp_disable_img_auto_sizes' );

Hello @farias615

Yes, it seems to be caused by a WordPress update 6.7.1 introduced the styling to fix auto image sizes #62413, my team is looking to fix the issue.

In meantime can you please add the following code in your child themes functions.php or in a custom plugin it should fix your issue on AMP pages.

/**
 * Disable auto sizes for AMP.
 */
function amp_disable_img_auto_sizes() {
	if ( function_exists( 'amp_is_request' ) && amp_is_request() ) {
		return false;
	}
}

add_filter( 'wp_img_tag_add_auto_sizes', 'amp_disable_img_auto_sizes' );

@madhu34 Can you please share your site health information using this form

@farias615

I apologize for the misunderstanding, but you have shared site health information where we found “Bunyad AMP” plugin active, so we thought it was custom AMP version.

Please make sure to keep the official AMP plugin active while we are checking your website.

We found following issues

1. The first issue you’re encountering with the AMP plugin settings appears to be caused by a conflict with the Litespeed plugin. It seems the Litespeed plugin is adding comments to the JSON response, which can interfere with the AMP plugin’s functionality.

To resolve this, please try adding the following code snippet to your active theme’s functions.php file or within a custom plugin:

add_filter( 'litespeed_comment', '__return_false' );

This code snippet should disable the Litespeed plugin’s comments in the JSON response.

2. The second issue invalids CSS being added in header, please check if your theme or any plugin is adding the invalid css, and please remove it or request that theme’s or plugin’s support to remove it.

<style>img:is([sizes="auto" i], [sizes^="auto," i]) { contain-intrinsic-size: 3000px 1500px }</style>

3. Your AMP pages are exceeding the CSS identify which plugin is exceeding CSS limit’s using AMP validator tool and find an alternative or suppress that plugin from AMP plugin settings.

Check your CSS budget, because the AMP framework only allows 75 KB CSS on each page, so the AMP plugin adds CSS optimizations, which are sometimes exceeded by third-party plugins or themes.

If you are not sure how to find exceeding CSS budget, follow the below steps:

a) Make sure you have enabled the AMP validation tool
Go-to: Users > Profile > check the checkbox for AMP Development tool > save

b) Visit AMP page exceeding CSS budget check Admin bar for AMP option locate submenu CSS budget and click on it (screenshot)

c) Locate the source of excessive CSS (screenshot)

d) If one of the plugins adds excessive CSS find an alternative plugin from the AMP ecosystem

You can learn more about the Reader mode video below:

We hope this helps!

@gaousti As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you require any further assistance.

Hello @farias615

Thank you for contacting us. You’re using a customized version of the AMP plugin. As we’re unfamiliar with the modifications that are made, we can’t provide specific support. We recommend contacting the Bunyad AMP plugins support for the assistance.

Hello @ali1010

Thank you for contacting us.

The first issue you’re encountering with the AMP plugin settings appears to be caused by a conflict with the Litespeed plugin. It seems the Litespeed plugin is adding comments to the JSON response, which can interfere with the AMP plugin’s functionality.

To resolve this, please try adding the following code snippet to your active theme’s functions.php file or within a custom plugin:

add_filter( 'litespeed_comment', '__return_false' );

This code snippet should disable the Litespeed plugin’s comments in the JSON response.

The second issue you mentioned, the error in Google Search Console, seems to be related to an invalid CSS rule being added to your website. This CSS rule includes a browser-specific path for the background image:

<div class="simple-translate-button isShow" style="background-image: url('moz-extension://3ebed59f-428c-4dd5-b8dd-d9053f54327b/icons/512.png'); height: 22px; width: 22px; top: 7456px; left: 722px;"></div>

The AMP validator of Google Search Console requires that background images have a valid URL with the https:// or https:// protocol. Since this CSS rule uses a moz-extension:// path, it’s considered invalid, leading to AMP errors.

To fix this issue, you’ll need to locate and remove this CSS rule from your website. This might involve inspecting your theme’s files, checking for any active plugins that might be adding this code, or using a browser developer tool to identify the source of this CSS rule.

We hope this information helps!

Hello @ali1010

Thank you for reaching out to us. When we checked your website’s AMP page, we found out that you are using AMP plugin in Reader Mode. Also, we didn’t encounter any issues with the AMP page. We also tested your AMP pages on AMP test, which didn’t report any errors.

If you were on different template mode before (Transitional or Standard) the error might be from the old settings and will clear over time.

We also noticed that you are using Elementor editor, which is not AMP compatible, so we will recommend adding the AMP enhancer plugin which fixes some compatibility issues with AMP.

We hope this helps!

Hello @madhu34

Can you please remove this custom CSS that has been added in header, it is breaking the AMP css styling.

<style>img:is([sizes="auto" i], [sizes^="auto," i]) { contain-intrinsic-size: 3000px 1500px }</style>

@viper_razor does recommendations from my last message helped?

Hello @madhu34

Thank you for reaching out to us, The Generate Press theme provides an AMP compatibility plugin to fix AMP issues, Please download and install it, the instructions are provided in their documentation

Additionally, can you please suppress plugin perfmatters from AMP settings as this optimization is already taken care of by the AMP plugin, you can read more about plugin suppression from our documentation

We hope this helps!

@educationnewshub As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you require any further assistance.

@viper_razor As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you require any further assistance.

Hello @tatilpanosu

Thank you for reaching out to us, When we checked page speed reports, it looks like there has been a render delay (Render delay is the time it takes for a web page or element to visually update) for text.

We can only think of the fonts that are being added though google fonts are not loaded in time and once loaded are they are swapped resulting in longer duration for render delay.

You can, however, update the font-display property to optional, it gives the font face a minimal block period and no swap period switching it to fallback font and there won’t be a render delay for the same.

https://fonts.googleapis.com/css2?family=Manrope&display=optional

You can learn more about web font optimizations from this guide

We hope this helps!