CriticalCSS & ao_noptirocket=1 Issue

  • Resolved stephen87

    (@stephen87)


    5 years ago

    Hello!

    I have Autoptimize set up to send urls to criticalcss via the api.

    For some reason its adding ?ao_noptirocket=1 to the end of each url which i guess is the uncached version?

    How do I resolve this?

    p.s I also have wp-rocket but thats only handling preloading

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    in AO2.5 it does so on purpose when lazyload is active to avoid criticalcss not “seeing” the images. I will probably change this for a future version.

    but why do you consider this a problem?

    Thread Starter stephen87

    (@stephen87)

    Thanks for clearing this up, I totally misunderstood.

    I assumed there was an issue with AO not passing on the cached version.

    I tried to check google but the results for “?ao_noptirocket=1” are just peoples open queue logs haha

    Thanks for replying and for creating such a great plugin.

    Have a fantastic week

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    you’re welcome, feel free to leave a review of the plugin and support here! ??

    frank

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘CriticalCSS & ao_noptirocket=1 Issue’ is closed to new replies.