AMP Errors After Installing W3

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    5 years, 1 month ago

    Hello @wcopus

    Thank you for your inquiry and I am happy to assist you with this.
    Can you please disable Lazy loading in Perfomrance>General settings, save all settings and purge the cache and try validating your AMP pages?
    Thanks!

    Thread Starter wcopus

    (@wcopus)

    5 years, 1 month ago

    Perfect. That seemed to do the trick. Is there any way to still utilize lazy loading for all pages except for AMP pages?

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    5 years, 1 month ago

    Hello @wcopus

    Thank you for the information.
    What you can do is to try to exclude the images on those pages from lazy load in Performance>User Experience>Exclude words.
    If that does not work, you should keep the Lazy load disabled.
    Thanks!

    Thread Starter wcopus

    (@wcopus)

    5 years, 1 month ago

    So could it be as simple as excluding the word “/amp” to make sure all of my AMP URLs aren’t lazy loading?

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    5 years, 1 month ago

    Hello @wcopus

    Thank you for your question.
    As I can see your images are being optimized with the SmushIt plugin so you should avoid using W3TC LazyLoading in this case.
    Thanks!

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

The topic ‘AMP Errors After Installing W3’ is closed to new replies.