Alain Schlesser

You seem to have a plugin or theme installed that adds HTML markup in a bad way.

This results in the following tag being echoed to the browser outside of the normal page rendering:

<i id="revolver-icon" class="dashicons dashicons-menu sidebar-rev alignleft"></i>

You’ll need to find out where that icon is being added and change the way that happens.

@aaron13223 The query itself seems to run as fast as expected on its own (0.001 sec on your MariaDB screenshot), and the EXPLAIN does not show any immediate issues as far as I can see.

However, on your QueryMonitor screenshot, I can see that the query runs through an extra DBCache (probably via W3TotalCache?). Have you tried disabling that DBCache to see whether that fixes the issue?

@collins1980 Release v1.5.2 is currently planned for today 10am PDT, provided no unexpected surprises come up in the mean time.

@janvitos Thanks for all the additional information, that really helps get a better picture of the issue.

From the Site Health debug information, I can see the following:

amp_css_transient_caching_disabled: true
amp_css_transient_caching_threshold: 50 transients per day
amp_css_transient_caching_sampling_range: 14 days
amp_css_transient_caching_transient_count: 172

With the new plugin release, we added a mechanism to detect when the CSS stylesheet cache we have is too volatile, to avoid filling up users’ database with thousands of transients when they don’t serve any use. This can happen when the CSS contains randomized or generated data, so that each new request has slightly different CSS than the one before.

In the above debug log, amp_css_transient_caching_disabled is true, meaning that this detection was actually triggered on your site, and that hence the CSS stylesheet caching was disabled.

The added latency for your site with this version could come from the fact that this caching is disabled and all stylesheets have to be reparsed on every single page request.

However, as we don’t yet have much real-world data about what values to expect, it could well be that our threshold is too low right now.

I would be very grateful if you could try the following to get some confirmation.

Can you please set the threshold to a high value for now, by adding the following code to a plugin or your theme’s functions.php file:

add_filter( 'amp_css_transient_monitoring_threshold', 1000 );

And then reset the disabling of the CSS stylesheet cache by running the following code once:

AMP_Options_Manager::update_option( Option::DISABLE_CSS_TRANSIENT_CACHING, true );

You can do this for example with WP-CLI’s wp shell command, or by pasting it into a plugin or your theme’s functions.php file and removing it again.

After this, when you go back to the Tools -> Site Health screen, the Info page should display these changes at the bottom, with amp_css_transient_caching_disabled showing false and amp_css_transient_caching_threshold showing 1000 transients per day.

Please let me know if you don’t know where to do the above, and I’ll prepare a separate plugin to install instead.

Thank you very much!

@macken Version 1.5.1 should fix your issue. Please update the plugin to that version and confirm whether the issue is fixed for you or not.

(It would still be a good idea to nag your hosting provider about the libxml version, though)

Thank you!

@kishanunjia I suspect that this is caused by the use of the amp_post_template_metadata filter.

Can you please check whether and how you are using this filter?

Your libxml version is indeed too low, and it is lower than what it should be for the PHP version you’re running.

I’ll look into whether I can get around the requirement for the libxml version we need.

In the mean-time, I would recommend talking to your hosting provider to find out whether they can update the version of libxml that is being used by PHP. This would not only fix the error above, but also generally improve DOM handling for your PHP version and make it more secure.

@kishanunjia There seems to be an error with the new serverside rendering component of version 1.5.0.

To help us debug, I would be grateful if you could send me the current contents of the transients in your wp_options table that start with _transient_amp_remote_request_. There should be 2 of them.

As a quick work-around, you can disable serverside rendering by adding the following filter in a plugin or your theme:

add_filter( 'amp_enable_ssr', __return_false );