AMPforWP conflict

  • Resolved tripledm

    (@tripledm)


    4 years, 4 months ago

    Almost all of our website pages was de-indexed and as result we lost 90% of the traffic. All our posts pages are on AMPforWP but thankfully we found the solution so this is to report the bug/conflict on AMP with the AMPforWP plugin with Recipes Card PRO.

    Error in Google Search Console:
    “The author stylesheet specified in tag ‘style amp-custom’ is too long – the limit is 75000 bytes.”
    Problem:
    With Recipes Card plugin enabled it injects a ton of css in to the amp-custom tag so it pushes it beyond the limit.
    Solution:
    Enable in AMPforWP under settings – performance “Optimise CSS (beta)”
    This applies tree-shaking so minising the CSS and removed the incorrectly injected css from amp-custom.

    I hope you can fix the conflict and I hope this helps someone else fix the search console error.

Viewing 2 replies - 1 through 2 (of 2 total)

  • Hello @tripledm

    First of all, we’re sorry about the loss of a big percent traffic on AMP pages. Thank you for your message about the conflict with AMPforWP plugin. We’ll try to fix the issue with size of inline CSS styles for AMP pages.

    Thread Starter tripledm

    (@tripledm)

    Thanks @vicolaspetru

    For some reason it injects the css in to style amp-custom so I don’t think it’s he inline css rather css on AMP for the recipes that is injected in to style amp-custom so really hope you fix it ??

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘AMPforWP conflict’ is closed to new replies.