Danilo Parra Jr.

Thank you Jamie!

Thank you @jamesosborne!

Hi @westonruter,

The site is just using transient in my local copy of the live site which I tested. So adding a debug code in the object caching won’t show anything in the log.

https://github.com/ampproject/amp-wp/blob/b5d3c6e457d06884e7f3847d0679be39657d401b/includes/sanitizers/class-amp-style-sanitizer.php#L1616

I tried to swap the stylesheets of Twenty Twenty-One theme to our theme’s stylesheet and check amp_parse_css which is zero and tried to put our stylesheet in the Twenty Twenty-One theme and check the amp_parse_css is not set to zero. Which concludes that some rules in our stylesheet is caching the issue.

This link shows the log of both the theme stylesheet being parsed multiple times in which some CSS rules are flagged as different.

Hi @westonruter,

Object caching is working in the dev site which is just a copy of the live site. I have checked wp-content/object-cache.php and it’s not empty or misconfigured.

In order to further investigate the issue, I disabled plugins, change themes, and found out that the main theme CSS is not being cache by AMP. This file https://www.superguide.com.au/wp-content/themes/genesis-superguide/style.css?ver=4.1.0 is being parsed multiple times on every page load.

In order to get the logs of all not cached files I added an error_log here
https://github.com/ampproject/amp-wp/blob/b5d3c6e457d06884e7f3847d0679be39657d401b/includes/sanitizers/class-amp-style-sanitizer.php#L970-L972

You can see the debug.log content here – https://gist.github.com/daniloparrajr/c5e59d24a5ff7a3e3881da137e61e9dc
This is all the logs generated when the homepage is loaded.

@westonruter @milindmore22

Ads are only showing for logged out users. I have checked amp_parse_css while logged in so ads that is adding inline styles won’t be present in the page. Also I have test a dev site where object caching is enable and it does show amp_parse_css is set to zero which means it is using the transient while in the staging and live site that have object caching disabled shows that amp_parse_css is not set to zero even on multiple page request.

Hi @milindmore22,

Thank you for your suggestion, but I already implemented WP Rocket through the Memberpress guide you mentioned. I also disable AMP on memberpress pages.

Hello @westonruter,

There is a dynamic content but it is not changing every time a page is loaded so it is pretty much the same e.g. theme color settings.

## Are you adding a current timestamp as the version for any of them, causing them to change with each page load?
I’m not using current timestamp to version any of them.

Hi @milindmore22,

I checked the live site and amp_parse_css is not set to zero which concludes that the site it not serving from transient. Please know that the live site does not have object caching enable because of memberpress recommendation. Is there any way around this if we can’t use object caching?

Hi @milindmore22,

I have submitted our site health information in the form, please check.

With regards to the stylesheet I manage to dequeue fontawesone and dashicons from the plugin calls, and optimize theme stylesheet by removing the unused styles we have in the site. Although that help in the site performance, AMP is still parsing the stylesheet slow. It is worth noting also that we don’t have Persistent object caching enable in our site because of Memberpress (our membership plugin) have issues with it.

The page tested is – https://www.superguide.com.au/comparing-super-funds/best-performing-pension-funds-high-growth

Please see the screenshot for the top 3 slowest process_link_element calls.
https://prnt.sc/ztr4nm

The list below are all the CSS files the page loads.

– https://www.superguide.com.au/wp-content/plugins/genesis-blocks/dist/assets/fontawesome/css/all.min.css?ver=1607299726
– https://www.superguide.com.au/wp-content/plugins/amp/assets/css/amp-default.css?ver=2.0.10
– https://www.superguide.com.au/wp-content/plugins/memberpress/css/ui/theme.css?ver=1.9.10
– https://www.superguide.com.au/wp-content/themes/genesis-superguide/style.css?ver=4.0.8
– https://www.superguide.com.au/wp-includes/css/dist/block-library/style.min.css?ver=5.6.1
– https://www.superguide.com.au/wp-content/plugins/wp-persistent-login-premium/blocks/manage-sessions/style.css?ver=1.0.1
– https://www.superguide.com.au/wp-content/plugins/genesis-blocks/dist/blocks.style.build.css?ver=1607299726
– https://www.superguide.com.au/wp-content/plugins/block-options/build/style.build.css?ver=1.29.3
– https://www.superguide.com.au/wp-content/plugins/superguide/public/css/superguide-public.css?ver=1.2.0
– https://www.superguide.com.au/wp-content/plugins/superguide/public/css/superguide-blocks.css?ver=1.2.0
– https://www.superguide.com.au/wp-includes/css/dashicons.min.css?ver=5.6.1
– https://www.superguide.com.au/wp-content/themes/genesis-superguide/lib/amp/amp.css?ver=4.0.8
– https://www.superguide.com.au/wp-content/themes/genesis-superguide/lib/gutenberg/front-end.css?ver=4.0.8
– https://www.superguide.com.au/wp-content/plugins/memberpress-courses/public/css/progress.css?ver=1.0.24
– https://www.superguide.com.au/wp-content/plugins/memberpress-courses/public/fonts/fontello/css/mp-courses.css?ver=1.0.24

SCREENSHOT
https://prnt.sc/ztqlhr

Thank you, Weston. I’m currently testing this in our staging site. If ever I have issues with the transients, I’ll let you know.

I just check within WPEngine and object caching is indeed disabled. Thank you! I’ll definitely enable this once we have reduced the autoloaded size on our site. Autoloaded data is still connected in the object caching though.

If the content that’s autoloaded surpasses the amount Object Caching can handle, then it rejects the request. WordPress, requiring the autoloaded data, sends the request again, and this causes a loop that eventually ends in a 502 error on the site.

The object cache size buffer is 1Mb.

https://wpengine.com/support/wp-engines-object-caching/#Object_Cache_and_502_Errors

• This reply was modified 4 years, 5 months ago by Danilo Parra Jr..

We have other autoloaded data on the site that all add up that affects the site performance. I’m currently trying to remove unnecessary data to keep our autoloaded data below 800,000 bytes. A recommendation by WPEngine – https://wpengine.com/support/database-optimization-best-practices/#Autoloaded_Data

I only have 6 amp related expired transients in the site. Is it safe to removed amp transients? or should I wait for the next update for the fix?

Autoloaded data – rows in wp_options that have the autoload column set to yes. Certain information in the database must load on each request, such as the site’s URL and active theme and plugins. We have 6 of this ‘_transient_amp_remote_request_*` in our site and wondering if we can only have one instead? Because it is adding up to our site’s autoloaded data in which turns our TTFB slow.

Screenshot
https://ibb.co/9hJmHqf

Thank you!