AMP Parameter

  • Resolved ecronik

    (@ecronik)


    2 years, 5 months ago

    Hi Marko,

    I hope you’re doing well! I have a question regarding the AMP configuration: When using query parameters (e.g. for my setup: https://domain.com/postname/?amp=1 ), I need to use “query string” in the W3TC extension, right? I am a little confused about the postfix: Standard is “amp”, do I need to change this to “?amp=1/” ? I’m asking since my mobile pagespeed score is worse with the extension enabled.

    Thanks a bunch and best regards,
    eC

    • This topic was modified 2 years, 5 months ago by ecronik.
Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @ecronik

    Thank you for reaching out and I am happy to assist you with this.
    The W3TC does not cache the query parameters by default. So if you are using Page Cache with Disk: Enhanced, the pages with query strings will not be cached.
    W3 Total Cache has the option Cache URIs with query string variables” and it is only available with Disk caching methods and memory-based caching like Redis or Memcached.
    This is most likely the reason your page speed decreased.
    As for the parameter, if you are using the query string for your AMP pages, in the W3TC AMP settings you should select AMP URL Type: query string and add ?amp to AMP URL Postfix: field.

    I hope this helps!

    Thread Starter ecronik

    (@ecronik)

    Hello Marko,

    Unfortunately, I can only do Disk and Disk: Enhanced. What would you recommend – to stay on Disk: Enhanced and get by without caching for the AMP pages, or to switch to Disk? Would the tradeoff between the two page caching methods be big or the advantage for the AMP pages? Pagespeed for them is looking really good already. Unfortunately, I can’t use the URL structure without query string for AMP, otherwise the layout of the pages will break.

    Thanks,
    eC

    Thread Starter ecronik

    (@ecronik)

    P.S.: And what I’m also wondering is if the Cache Preload mechanism works on just “Disk” as well?

    Also, if the caching of query string URL’s can/will cause any issues?

    Thanks for your advice,
    eC

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @ecronik

    Thank you for your feedback.
    If you check the source code on the AMP page when using the Disk: Enhanced you will see the following:
    Page Caching using disk: enhanced (Requested URI contains query)
    Try adding the amp string to Performance>Page Cache>Advanced>Accepted query strings:
    save all settings and purge the cache and let me know if this helps!

    Thanks!

    Thread Starter ecronik

    (@ecronik)

    Hello Marko,

    this seems to be working perfectly.

    Thank you for your excellent continued support,
    eC

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @ecronik

    You are most welcome!

    We would really appreciate it if you could take a minute and post a review here. This will help us to continue offering a top-notch product to users.
    Thanks!

    Thread Starter ecronik

    (@ecronik)

    Hi Marko,

    of course – just posted.

    Thanks again and best regards,
    eC

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘AMP Parameter’ is closed to new replies.